Stateless API service
A Node / Python / Go API that scales horizontally. Connect to an external database.
Runs
Express, FastAPI, Gin, Spring
Container Hosting
Push a Docker image, get a URL. Internal service discovery, custom domains, scale to zero on idle. You write the Dockerfile; we run the cluster.
acme-api · cluster
5/5 healthyapi-gateway
replicas 2/2 · 8% cpu · 124 MB
orders-service
replicas 3/3 · 12% cpu · 287 MB
queue-worker
replicas 4/4 · 6% cpu · 198 MB
admin-dashboard
replicas 1/1 · 3% cpu · 67 MB
cron-runner
replicas 0/1 · 0% cpu · 0 MB
~10s
Cold start
Zero
Idle cost on Pod
Auto
GitHub deploys
Streamed
Live logs + metrics
Pricing
All three come with GitHub integration, custom domains, auto SSL, internal service discovery, and live logs + metrics. Bigger tiers run more containers with more resources.
Pod
1 container · 512 MB · 0.5 vCPU
Side projects, small APIs.
Cluster
Up to 5 containers · 4 GB · 2 vCPU
Staging + small production.
Fleet
Unlimited containers · 16 GB · 8 vCPU
Production microservices.
NZD inc. GST. Waitlist members get 2 months free on any tier at launch. Final pricing fixed at GA.
What you can run
Six common ways teams use Container Hosting. Stateless workloads where state lives elsewhere (managed DB, object storage, queues).
A Node / Python / Go API that scales horizontally. Connect to an external database.
Runs
Express, FastAPI, Gin, Spring
Job queues, message consumers, scheduled tasks. Scale workers independently from your API.
Runs
Sidekiq, Celery, BullMQ, RabbitMQ consumers
Multiple containers talking via service discovery. Deploy services independently, share nothing.
Runs
Anything packaged as an OCI image
A container per pull request. Spin up, share the URL with reviewers, tear down on merge.
Runs
Works with any GitHub-deployed service
A small container that takes webhooks and forwards them. Scale to zero, pay for traffic only.
Runs
Stripe webhooks, GitHub Actions, third-party integrations
A container that wakes up, runs your batch, exits. Per-second billing means you pay for compute used.
Runs
ETL jobs, image processing, data pipelines
Not sure containers are right?
GitHub deploys
Connect GitHub. Push triggers a build. Health-checks gate the rolling update. Failed deploys roll back without you doing anything.
How a deploy goes
git push origin main
GitHub webhook fires
kapsule build container
Dockerfile detected, layers cached
push image to internal registry
Signed, sealed, tagged with commit SHA
rolling update across replicas
Health-check gates promotion
old replicas drain, traffic flips
~10s end-to-end, zero downtime
Scale to zero
Pod scales to zero replicas when idle. First request after idle takes ~3s extra (cold start). Bigger tiers stay warm for production-grade response times.
Scale to zero
Idle ≠ payingNo requests, no charge
First request boots a container
Auto-scaled to 4 replicas
Trickle traffic, one warm replica
Per-second billing on Pod. Bigger tiers always-on.
FAQ
Containers are how you ship stateless workloads in 2026. Push a Docker image, get a URL. Scale a service independently from your database. No SSH-and-configure step, no OS patching, no "where do I put this file." If your app fits in a Dockerfile, Container Hosting is faster to ship and cheaper to run than the equivalent VPS.
Container Hosting is for stateless services. Run your database on a Cloud VPS or Cloud Server, file storage on our object storage, queues on a managed Redis. Containers connect to those over the network. This is the modern microservices architecture, and it scales properly.
Q3 2026 for general availability. The build orchestrator and image registry are in private testing now. Waitlist members get early access starting Q2 2026 and 2 months free at GA on any tier.
Yes. We support docker-compose for multi-container deploys on Cluster and Fleet. Services declared in compose get internal hostnames and discovery automatically.
Containers launch in our European region for the initial rollout. NZ visitors hit our Auckland + Sydney edge for static + cached responses; container origins are served from the EU at ~280ms round-trip. A Pacific region is planned post-GA.
Talk to us. We have custom container clusters available with dedicated hardware, larger resource pools, and SLA contracts. Email [email protected] or use the Sales link in any plan card.
Q3 2026 launch
Waitlist members get early access starting Q2 2026 and 2 months free on any tier at launch.