ProductsServices
Managed compute
Run the process. Bind the database.
A service is your process — a Nuxt server, a Go API, a worker — running in a microVM of its own with a TLS address in front of it. Add a database from the catalogue and its address arrives as an environment variable.
- Isolation
- a microVM each
- Catalogue
- 7 engines
- Shell
- none, by design
How it works
The CLI looks at your build and deploys what it is.
Link the build
A static folder becomes a site; a Nitro node-server build or a Linux binary becomes a service.
$ subnomic sites link api --dir .outputDeploy
The platform builds a read-only disk from your build, boots a microVM and waits for your process to answer on its port.
$ subnomic sites deploy --prod https://api.subnomic.app
Bind a database
The connection string is generated for you and handed to your process, so it never lives in your repository.
DATABASE_URL=postgres://postgres:••••@… REDIS_URL=redis://default:••••@…
The catalogue
Seven engines, our images, pinned.
Pick one and bind it to a service. You cannot point a managed datastore at an image of your own: it would be arbitrary code running with our credentials on our hardware, which is a different product with a different threat model.
The catalogue lists only the engines the machines in your region can run.
| Engine | Image | Your process gets |
|---|---|---|
| PostgreSQL | postgres:18 | DATABASE_URL |
| MariaDB | mariadb:10.11 | DATABASE_URL |
| Redis | redis:7.0 | REDIS_URL |
| Valkey | valkey:7.2 | REDIS_URL |
| Memcached | memcached:1.6 | MEMCACHED_URL |
| NATS | nats:2.15 | NATS_URL |
| Meilisearch | meilisearch:1.54 | MEILISEARCH_URL |
What comes with a service
A size, an address, and nothing to log in to.
A size is named for its memory
256m, 1g and so on. Each one fixes CPU, memory, disk, network and disk I/O together — they are not tuned separately.
Resize without losing data
The service stops, is re-sized and starts again on the same machine. Disk only ever grows.
No shell
Your build arrives as a read-only disk built before the machine boots. There is no SSH into a service, by design.
Egress is yours to close
A service may reach the internet or only the workspace’s own services. It applies at the host firewall, not in your code.
Services reach each other
Services in the same workspace can talk to each other. Nobody else’s can.
What the host measures
CPU, memory, disk and network read from the machine itself, and live logs from your process.
Limits
What each plan includes.
| Plan | Free | Pro | Team | Enterprise |
|---|---|---|---|---|
| Services | 1 | 3 | 10 | 10 |
| Largest service | 256 MB | 1 GB | 2 GB | 8 GB |
| All services together | 256 MB | 3 GB | 20 GB | 80 GB |
A stopped service still holds its slot on a host and still counts against your plan — delete it to free the room. Going past a limit refuses the action rather than charging for it.
Not yet
What it does not do today.
No automatic backups
A managed datastore holds your data on one machine and nothing snapshots it for you. Take your own dumps if the data matters.
Logs are not archived
Logs live with the machine, so a service that is destroyed takes its history with it. Download anything you need to keep.
Your first service is on the free plan.
One service of 256 MB comes with every workspace, with no card. Link a build and deploy it.