Get your projects
off localhost.
Point us at a GitHub repo, bring your own Dockerfile, or just ask Claude to deploy it. Your project gets a live URL with HTTPS, in minutes.
Three ways in.
One URL out.
Pick whichever fits the project. What comes back is the same.
Give us a repo
Connect GitHub and pick a repository. We work out what the project is written in and build it for you. No Dockerfile, no config file, nothing to write.
Bring your Dockerfile
Already containerised? We build your Dockerfile exactly as it is and run the image that comes out. You keep control of how it is put together.
Just ask
ZopCloud speaks MCP, so Claude can create the service, deploy it, check whether it came up and redeploy. You never leave the chat.
Whichever way you start, the same four things happen next.
Code to image
Your project is built into a container image and stored for you.
Image to service
The image runs as a service with its own address.
Service to URL
A certificate is issued and traffic is routed to it over HTTPS.
Push to update
Turn on auto deploy and every push to your branch ships itself.
If it runs in a container, it runs here.
Node, Python, Go, PHP, Ruby, Rust and static sites build without a Dockerfile. Anything else, bring your own.
Portfolios and personal sites
Your own site, a project showcase, a CV page. Built with Next, Astro, Hugo, plain HTML or whatever you reached for. It gets a real address you can put in a bio or on an application.
Student projects
Coursework, a hackathon build, a final year project. Hand in a link your marker can open on their own machine, months after the deadline.
Docs and static sites
Documentation, guides, a landing page, or the output of any static site generator. Point it at the repo and the built site goes up.
Open source apps
Give the project you maintain a live demo, so people can try it before they clone it. Self host someone else's the same way.
APIs and backends
A REST API, a bot, a scheduled job, or the backend for something you are building. Attach a database when it needs to remember things between requests.
Every service gets all of this, from the very first deploy.
A URL with HTTPS
Its own address, with a certificate issued and renewed for you.
Databases
Create one, attach it to a service, and your app has somewhere to keep things.
Organisations
Group your projects and bring in the people you work with.
Environment variables
Configuration and secrets set per service, kept out of the image.
Auto deploy
Point a service at a branch. Every push ships itself.
Logs and deploy history
See what happened on every deploy, and put an earlier one back when you need to.
Services sleep after 30 minutes with no traffic and wake again on the next request. That is how the free tier stays free.
You already built it.
Now give it an address.
Free to start. Bring a repo, a Dockerfile, or just a sentence.