Vinssi documentation

Vinssi takes a GitHub repository, builds it, and runs it on a European cloud in Helsinki. You get a URL, TLS, and a deploy on every push. This guide covers the platform as it works today.

What you can deploy

• Next.js applications, built with next build and served by next start.
• Vite front-ends, built to static files and served from a container.
• Node backends built on Express, Fastify, Hono or NestJS.

Detection is automatic. See Supported apps for the exact rules, the commands Vinssi runs, and the two things every app must respect: listen on port 3000 and run on Node 22.

What you need

1. A GitHub account and a repository you can install a GitHub App on.
2. A Vinssi account. Sign in at vinssi.ai/dashboard; a workspace is created for you with a small credit balance.
3. A plan for each project you want to deploy. Plans are per project and start at a few euros a month. See Plans and limits.

Where to go next

• Quickstart walks through the first deployment end to end.
• Environment variables explains how secrets reach your build and your running app.
• Databases adds a managed Postgres to a project, from €5 a month.
• Deployments describes what a push triggers, the stages a deploy goes through, and how rollback works.
• CLI covers the vinssi command for scripting deploys from a terminal or CI.
• Vinssi Pages is the fastest way to share a static HTML file or folder with a link.

Things Vinssi does not do yet

Being upfront saves you a support ticket:

• No preview deployments. Only pushes to the connected repository's default branch deploy.
• No runtime logs in the dashboard. Build logs are available; application output is not yet.
• No persistent disk. Anything your app writes to its filesystem is gone on the next deploy.
• One replica per project. There is no autoscaling.

If any of these blocks you, tell us. They shape what we build next.