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.
| Service | Status | Deploys |
|---|---|---|
| my-portfolio | live | 14 |
| final-year-project | live | 8 |
| docs-site | asleep | 31 |
| api · database attached | live | 62 |
| hackathon-demo | building | 3 |
Pick whichever fits the project. What comes back is the same.
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.
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.
ZopCloud speaks MCP, so Claude can create the service, deploy it, check whether it came up and redeploy. You never leave the chat.
Your project becomes a container image, stored for you.
The image runs as a service with its own address.
A certificate is issued and traffic routed over HTTPS.
Turn on auto deploy and every push ships itself.
Node, Python, Go, PHP, Ruby, Rust and static sites build without a Dockerfile. Anything else, bring your own.
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.
Coursework, a hackathon build, a final year project. Hand in a link your marker can open on their own machine, months after the deadline.
Documentation, guides, a landing page, or the output of any static site generator. Point it at the repo and the built site goes up.
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.
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.
Its own address, with a certificate issued and renewed for you.
Create one, attach it to a service, and your app has somewhere to keep things.
Group your projects and bring in the people you work with.
Configuration and secrets set per service, kept out of the image.
Point a service at a branch. Every push ships itself.
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.
Free to start. Bring a repo, a Dockerfile, or just a sentence.