Plans and limits
Billing is per project. Each project you deploy carries a plan; the workspace has one Stripe subscription that holds all of them. Prices are in euros and exclude VAT.
Plans
| Plan | Price | CPU | Memory | Good for |
|---|---|---|---|---|
| Tiny | €5 / month | 0.1 CPU, bursting to 0.2 | 256 MB, up to 512 MB | Prototypes, internal tools, low-traffic backends |
| App | €9 / month | 0.25 CPU, bursting to 0.5 | 512 MB, up to 1 GB | Production Next.js sites and APIs |
| Pro App | €15 / month | 0.5 CPU, bursting to 1 | 1 GB, up to 2 GB | Heavier server rendering or memory-hungry services |
The first figure is guaranteed; the second is the ceiling. A container that exceeds its memory ceiling is terminated and restarted on the next deployment.
Every plan runs one instance of the app. There is no autoscaling and no persistent disk. During a deployment the new instance starts alongside the old one, which is why the memory ceiling is briefly doubled.
Plans can be changed on the project's Billing tab. Changes are prorated by Stripe.
Database add-ons
A project can add one managed PostgreSQL database on top of its plan. It is billed on the same subscription.
| Tier | Price | Instance | Storage | Connections |
|---|---|---|---|---|
| Postgres Lite | €5 / month | Shared pool | 1 GB | 5 |
| Postgres Starter | €12 / month | Dedicated, 1 GB RAM | 10 GB | 50 |
| Postgres Standard | €45 / month | Dedicated, 2 GB RAM | 25 GB | 50 |
| Postgres Plus | €89 / month | Dedicated, 4 GB RAM | 50 GB | 100 |
Backups, upgrade behaviour, the Lite tier's caveats and what happens when billing lapses are on the Databases page.
Credits
New workspaces receive €9.00 in credits. Credits are applied automatically to your invoices before your card is charged, and Vinssi may grant more for pilots or promotions. Your balance is shown on the dashboard.
What happens without an active plan
A project with no plan, or with a plan whose payment is past due:
- cannot be deployed, from the dashboard, the CLI, or a push;
- keeps serving whatever is already live;
- can still be configured: variables, build settings, domains and repository connections all work.
Update the payment method under Billing to resume deployments. Vinssi Pages is not part of the deploy gate and keeps working regardless.
Platform limits
| Limit | Value |
|---|---|
| Build time | 25 minutes |
| Build resources | 2 CPU, 4 GB memory |
| Request body through the platform address | 50 MB |
| Time for a new version to start listening | about 150 seconds |
| Deploys and rollbacks | 20 per 5 minutes per workspace |
| API token creation | 10 per hour |
| Checkout sessions | 20 per hour |
Vinssi Pages has its own limits, listed on its page.
Network
Your app can reach the public internet and cannot reach other customers' apps or Vinssi's internal services. Inbound traffic arrives only through the platform address and verified custom domains, on port 3000.