ZoophostDocs

Deploy your first app

A complete first deployment: buy a cloud hosting plan, push a repository, pick a build pack, attach a domain and watch the build finish.

Getting started3 min read

This is the shortest path from nothing to a running site on Zoophost Cloud hosting. It assumes you have an account and a Git repository you can push to.

1. Buy a cloud hosting plan

  1. Open zoophost.com/cloud and pick a plan. Hobby is enough for a first app; Pro and Business add more websites and dedicated vCPU.
  2. Choose monthly or annual billing. The annual variant is the same monthly rate billed once for twelve months.
  3. Check out with the wallet, a card or UPI.

A plan includes a fixed number of website slots. Each app uses one slot. You can add another plan later from Websites & Apps with Buy a plan or Add slots.

2. Start a deployment

  1. Open Zoop Console and select the right organization.
  2. Go to Websites & Apps and choose New deployment.
  3. Work through the four steps: Source → Destination → Plan slot → Review.

Source

Pick Git repo for a public repository:

  • Git repository URL — the HTTPS clone URL.
  • Branch — usually main.
  • Build pack — Nixpacks (Auto-detect) works for most Node, Python, Go, Ruby, PHP, Rust and Java projects. Choose Static Site for a pre-built static output, Dockerfile if the repository contains a Dockerfile, Docker Compose for a compose file, or Railpack if you prefer it.

For a private repository, connect GitHub first — see Deploy a private repository.

Destination

Give the app a name (optional; a name is generated if you skip it) and enter a domain if you already have one pointed at Zoophost. You can add the domain later.

Plan slot

Pick a plan with a free slot. The card shows the plan name and how many websites it includes. If every slot is taken, buy another plan or add slots.

Review

Check the source, name, branch and build pack. The footer tells you which plan the slot comes from. Choose Deploy — uses 1 slot.

3. Watch the build

The app page opens on Deployments. A new deployment moves through queued, building, deploying and finally success (or failed). Open Logs to follow the build in real time. Most builds finish in under a minute; large Docker builds take longer.

If the build fails, the log names the failing command. See Failed deployments for the common causes.

4. Open the app

Every app gets a Zoophost hostname ending in .falcon.zoophost.com. Open the Overview tab to see it, or use Domains. HTTPS works on that hostname without any extra setup.

5. Attach your own domain

  1. In Settings → Networking, add the domain (one per line, include the protocol, for example https://app.example.com).
  2. Add the DNS record the console asks for. If the zone is hosted on Zoophost nameservers, the record can be written for you with Host this domain here.
  3. Save. The Domains card shows the DNS state: Points here, Does not point here, No A record yet, or DNS hosted here. SSL is issued once the name resolves to Zoophost.

Details: Custom domains and SSL.

6. Keep it running

  • Auto deploy on push is under Settings → Source. With it on, every push to the selected branch builds and deploys.
  • Restart, Stop and Start are in the app header.
  • Environment Variables is its own tab; saving a value triggers a deploy.

What a deployment costs

Nothing at deploy time. The slot was paid for when you bought the plan, and redeploying does not consume another slot.

Next

  • quickstart
  • first deploy
  • git
  • cloud hosting
  • build
  • ssl

Ready to use this

Every product line and its entry price on one page.

  • Cloud hosting from the cheapest tier up
  • INR pricing, GST included
See the plans
Still stuck? Open a ticket from Support tickets in the console, or email [email protected]. Include the service name, the exact error and what you already tried.