How cloud hosting works
Zoophost Cloud hosting runs each app in its own container: how slots, builds, releases, previews and scaling fit together.
Cloud hosting is Zoophost's platform-as-a-service product. You give it code or an image; it builds, runs and routes the result. You never see a server.
The pieces
| Piece | What it means |
|---|---|
| App | One deployable service: a repository, image or Dockerfile, plus its settings |
| Slot | One app's place in a plan. Plans include 5, 15 or 30 website slots |
| Build | The step that turns your source into an image, using the selected build pack |
| Deployment | One build-and-release attempt, with logs and a final status |
| Release | The running version produced by a successful deployment |
| Domain | A hostname routed to the app, with SSL issued after DNS points here |
What happens on a deploy
- The source is fetched: repository at a branch, a registry image, or an inline Dockerfile.
- The build pack runs. Nixpacks detects the language and installs dependencies; a Dockerfile build uses your own instructions.
- The new image is started as a container and health-checked if a health check is configured.
- Traffic moves to the new container. The previous image is kept according to Images to keep.
- The deployment is recorded with its commit, branch, author, duration and logs.
Builds run on Zoophost infrastructure. You do not pay for build minutes separately, and a redeploy does not consume another slot.
Plans and slots
Cloud plans are sold as pools of website slots:
- Hobby — 5 websites, 0.5 vCPU burst, 1 GB RAM, 10 GB NVMe.
- Pro — 15 websites, 2 dedicated vCPU, 4 GB RAM, 40 GB NVMe.
- Business — 30 websites, 4 dedicated vCPU, 8 GB RAM, 100 GB NVMe.
Plans add up. Buying a second Hobby plan gives you five more slots, not a replacement. Every app takes exactly one slot while it exists; deleting the app frees it.
Each website slot also brings capacity for the other two services:
- One hosted DNS zone per slot on our own nameservers, with a full record editor and one-click mail records. A plan for 5 websites can host 5 zones.
- One mailbox per slot on your domains, with webmail, IMAP and SMTP plus a daily sending allowance. The same plan includes 5 mailboxes.
That capacity is a balance rather than a fixed allocation: it stacks across plans and across purchases. A DNS pack adds ten zones, a Business Email pack adds 5, 10 or 20 mailboxes. A zone created for a domain bought here, or one a mail plan sets up, does not use a slot. Zones and mailboxes you already have keep working if a plan lapses; only creating new ones is blocked until the balance covers them.
Resources are reserved per app within the plan's pool, so a noisy neighbour on the same physical host cannot steal your CPU.
Preview deployments
With Preview deployments for pull requests enabled under Settings → Source, a pull request gets its own build and URL. Use it to review a change before it reaches production. Preview deployments can consume resources; switch the option off if you do not use them.
Domains and SSL
Each app can answer on several hostnames. Zoophost issues a free Let's Encrypt certificate for every domain once DNS points at the platform. Force HTTPS redirects plain HTTP.
A Zoophost-provided hostname works immediately. A custom domain needs either its DNS zone hosted on Zoophost nameservers or a record you add at your current DNS provider.
Logs and releases
- Deployment logs show build output, streaming while the build runs.
- Runtime logs show what the process prints after it starts, refreshed every 10 seconds.
- Images to keep controls how many old build images stay available for rollback.
There is no rollback button in the console. To go back to an earlier version, redeploy the earlier commit (or revert and push). Old images are retained for provider-level recovery; keep that in mind when planning a rollback.
When cloud hosting is the wrong fit
Choose a different product if you need:
- Root access or a custom kernel — use Cloud VPS.
- A whole physical machine — use Dedicated servers.
- A GPU — use GPU & LLM hosting.
- Long-running stateful software you must administer yourself — a VPS is simpler than fighting a container platform.
You can migrate upward without changing accounts, billing or support.
Next
- cloud hosting
- containers
- slots
- builds
- releases
- plans
Ready to use this
Git-push containers, previews and custom domains, billed monthly in INR.
- 5 websites on the smallest plan
- Free SSL and custom domains

