Always-on backends, background workers, and reproducible build pipelines on infrastructure we own — predictable performance, private networking, and autoscale, with no noisy neighbours.
Live — battle-tested in production · Preview — fully usable today, still maturing · Coming soon — on the roadmap
Always-on services with health checks and zero-downtime deploys.
Long-running services are health-checked and self-healing, with zero-downtime rolling releases so a deploy never drops in-flight requests. Logs, metrics, and a shell are built in, so debugging a running service doesn't mean bolting on a separate observability stack.
Scale on real load signals and down to zero when idle.
Scaling follows real signals — concurrency and CPU — and can fall all the way to zero when a service is idle so you stop paying for nothing. You set the floor and ceiling, so a traffic spike scales out within bounds you chose rather than a surprise bill. (Coming soon.)
Service-to-service traffic over an encrypted private mesh.
Services talk to each other over an encrypted private mesh with private DNS, so internal traffic never touches the public internet. There are no bastion hosts or VPN appliances to run — the network is part of the platform, not a box you operate on the side.
Queues, cron, and long jobs decoupled from the request path.
Queues, scheduled cron jobs, and long-running tasks live off the request path, with durable delivery, retries, and backoff so work isn't lost when something fails mid-flight. A job can outlive the request that scheduled it, which is what you want for anything slower than a page load. (Coming soon.)
Reproducible builds with layer caching and artifact storage.
Builds are deterministic and layer-cached, so an unchanged dependency isn't rebuilt and an unchanged step isn't re-run. Artifacts are shared across services, and the same pipeline runs locally and in the cloud — the build that passes on your machine is the build that ships.
Full Postgres with pgvector for complex queries and AI workloads.
Managed Postgres with pgvector handles complex queries and AI workloads out of the box. Dedicated vector search scales semantic lookups beyond relational, and object storage covers binary assets with zero cross-box egress fees.
Where do my backends actually run?
On bare metal we own and operate — predictable performance with no noisy neighbours and no rented capacity underneath you.
Can services scale to zero when idle?
Autoscale (coming soon) scales on real concurrency and CPU signals and down to zero when idle, with floors and ceilings you control.
How do my services talk to each other privately?
Over an encrypted private mesh with private DNS between services — no bastion hosts or VPN appliances to run, and nothing exposed publicly.
What databases can I use?
Managed Postgres with pgvector for complex queries and AI workloads, plus dedicated vector search when you need scale beyond that.
Are builds reproducible?
Yes — deterministic, layer-cached builds with shared artifacts across services, and the same pipeline runs locally and in the cloud.
Everything here runs on infrastructure we own and operate. Start free.