Container Hosting

Containers,
without the Kubernetes.

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.

Early access: Container hosting launches Q3 2026. Waitlist members get 2 months free at launch on any tier.
Push Docker image Scale to zero on idle Custom domains + auto SSL NZ-time support
kpanel.kapsulecloud.com/containers

acme-api · cluster

5/5 healthy

api-gateway

replicas 2/2 · 8% cpu · 124 MB

live

orders-service

replicas 3/3 · 12% cpu · 287 MB

live

queue-worker

replicas 4/4 · 6% cpu · 198 MB

live

admin-dashboard

replicas 1/1 · 3% cpu · 67 MB

live

cron-runner

replicas 0/1 · 0% cpu · 0 MB

idle
Cluster · 4 GB pooled · 2 vCPU pooledDeploy from GitHub →

~10s

Cold start

Zero

Idle cost on Pod

Auto

GitHub deploys

Streamed

Live logs + metrics

SupportsDocker·OCI images·Dockerfile·docker-compose·k3s-compatible·GitHub Actions deploys

Pricing

Three tiers. Same orchestration.

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

$29/ mo

1 container · 512 MB · 0.5 vCPU

Side projects, small APIs.

  • 1 container
  • 512 MB RAM, 0.5 vCPU
  • Scale to zero on idle
  • *.kaps.run subdomain
  • Auto SSL
  • GitHub deploy integration
Join Waitlist
Most picked

Cluster

$89/ mo

Up to 5 containers · 4 GB · 2 vCPU

Staging + small production.

  • Up to 5 containers
  • 4 GB RAM, 2 vCPU pooled
  • Internal service discovery
  • Custom domains
  • Persistent volumes (paid)
  • Priority support
Join Waitlist

Fleet

$249/ mo

Unlimited containers · 16 GB · 8 vCPU

Production microservices.

  • Unlimited containers
  • 16 GB RAM, 8 vCPU pooled
  • Multi-region routing
  • Premium support
  • SLA available
  • Engineering hours add-on
Join Waitlist

NZD inc. GST. Waitlist members get 2 months free on any tier at launch. Final pricing fixed at GA.

What you can run

If it packages as a container, it runs here.

Six common ways teams use Container Hosting. Stateless workloads where state lives elsewhere (managed DB, object storage, queues).

Stateless API service

A Node / Python / Go API that scales horizontally. Connect to an external database.

Runs

Express, FastAPI, Gin, Spring

Background workers

Job queues, message consumers, scheduled tasks. Scale workers independently from your API.

Runs

Sidekiq, Celery, BullMQ, RabbitMQ consumers

Microservices

Multiple containers talking via service discovery. Deploy services independently, share nothing.

Runs

Anything packaged as an OCI image

PR preview environments

A container per pull request. Spin up, share the URL with reviewers, tear down on merge.

Runs

Works with any GitHub-deployed service

Webhook receivers

A small container that takes webhooks and forwards them. Scale to zero, pay for traffic only.

Runs

Stripe webhooks, GitHub Actions, third-party integrations

Batch processing

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

Push to deploy. Zero downtime, every time.

Connect GitHub. Push triggers a build. Health-checks gate the rolling update. Failed deploys roll back without you doing anything.

  • Dockerfile or docker-compose, auto-detected
  • Image build cached across deploys
  • Rolling update across replicas with health gates
  • Automatic rollback on failed health checks

How a deploy goes

1

git push origin main

GitHub webhook fires

2

kapsule build container

Dockerfile detected, layers cached

3

push image to internal registry

Signed, sealed, tagged with commit SHA

4

rolling update across replicas

Health-check gates promotion

5

old replicas drain, traffic flips

~10s end-to-end, zero downtime

Scale to zero

Idle workloads cost nothing.

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.

  • Pod: scale to zero, pay only when serving
  • Cluster + Fleet: always warm, predictable latency
  • Per-second billing on Pod for true usage pricing
  • Per-month billing on Cluster + Fleet for stable budgeting

Scale to zero

Idle ≠ paying
00:00 to 06:000 replicas

No requests, no charge

06:00 to 09:001 replicas

First request boots a container

09:00 to 18:004 replicas

Auto-scaled to 4 replicas

18:00 to 24:001 replicas

Trickle traffic, one warm replica

Per-second billing on Pod. Bigger tiers always-on.

FAQ

Frequently asked questions

Why containers and not just a VPS?+

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.

What about state, databases, file storage?+

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.

When does Container Hosting actually launch?+

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.

Can I use my existing Docker Compose file?+

Yes. We support docker-compose for multi-container deploys on Cluster and Fleet. Services declared in compose get internal hostnames and discovery automatically.

Will my Container Hosting workloads stay in NZ?+

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.

What if I outgrow Fleet?+

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

Be first at GA. 2 months free, any tier.

Waitlist members get early access starting Q2 2026 and 2 months free on any tier at launch.