A SaaS on one private network.
App servers behind a load balancer, managed PostgreSQL with a standby, and Valkey for sessions and queues. Each part is one lc command or one Terraform resource.
What it needs
The parts a SaaS runs on.
An app tier that widens under load, a database run for you, and a private network between them. All of it fits in one set of Terraform files.
An app server in 38 seconds
Another app server answers SSH 38 seconds after
lc server create. The load balancer adds it by label once it passes a health check.PostgreSQL with a standby
Managed PostgreSQL 16, 17 or 18 restores to any second of the last seven days. A standby on another host takes over when the primary fails.
Sessions and queues in Valkey
Managed Valkey 9 holds sessions, caches and job queues, so any app server can take the next request.
One private network
App servers reach PostgreSQL and Valkey on private addresses, over TLS. The network and the traffic inside it are not billed.
Staging from the same files
Build staging from the production Terraform files on smaller plans.
terraform destroyremoves it at the end of each working day.A copy in a second region
Stream a copy of the database to a second region over the private network. Tallinn to Riga is 5 ms, and Vienna to Milan 9 ms.
A month of it
A SaaS with a few thousand customers.
Three app servers behind a load balancer, PostgreSQL with a standby and Valkey for sessions. Uploads sit in a bucket, and a staging server runs on weekdays.
The month assumes outbound traffic stays inside the 20 TB each server includes, pooled across the project. Private networks and firewalls are not billed, and VAT is extra.
| What | Plan | Cost |
|---|---|---|
| App servers | 3 × s-4 | €37.47 |
| PostgreSQL, primary and standby | 2 × db-4 | €139.80 |
| Valkey, sessions and queues | kv-1 | €7.90 |
| Load balancer | lb-1 | €5.49 |
| Object storage, customer uploads | 2 × objects | €10.98 |
| Staging, weekdays only | s-2 | €2.20 |
| The month | €203.84 | |
Start with one server and one command.
Choose a region and a plan, and add an SSH key. The server answers SSH 38 seconds after the command, at the price on its spec sheet.