Skip to main content
For open-source maintainers

Make it live in one click.

Your users click it and get their own copy of your project running on zopcloud, with a live HTTPS URL. Free to start, no card.

deploy
build  detected Node, no Dockerfile neededdone
push   image to registrydone
run    container starteddone
serve  certificate issueddone

One line in your README.

You add it once. Everyone who reads your README can use it.

01 They click the button in your README.
02 Everything is already filled in.
03 Their own copy, live on its own URL.

What your users get.

Every deploy from your button comes with all of this.

01

Your app, built

ZopCloud reads your code and builds it for you. Have a Dockerfile? It uses that.

02

A URL with HTTPS

Every service gets an address on our domain with HTTPS. Users can point their own domain at it too.

03

A database

Create one, attach it to the service, and the app has somewhere to keep things between requests.

04

Environment variables

Add the settings your service needs, like an API URL or a feature flag, right on the service.

05

Observability

Logs, metrics and deploy history for every service, so your users can see what it is doing.

06

Rollback

Every deploy is kept in the history, and they can roll back to an earlier one.

What your users can run.

The kinds of project zopcloud is built for.

01

Web apps

A full app, frontend and backend, in Node, Python, Go, PHP, Ruby or Rust.

02

Docs and static sites

Documentation, guides, a landing page, or the output of any static site generator.

03

APIs and backends

A REST API, a bot, a scheduled job. Attach a database when it needs to remember things.

04

Personal projects

A side project or a weekend build, with a link that still opens months later.

Questions maintainers ask.

Before they put anything in their README.

Does it cost my users anything?

zopcloud is free to start, and there is no card to enter before they deploy.

Do I need to change my repo?

No. The button is one line in your README. There is no config file to add, and no Dockerfile needed for Node, Python, Go, PHP, Ruby, Rust or static sites.

What if my project needs a database?

After the first deploy, your users create a database and attach it to the service. You can also pre-fill environment variables in the link with &env=NAME=value. Use it for defaults only, never secrets, because the link is public.

Can I remove it later?

Yes. Delete the line from your README and the button is gone. Copies your users already deployed are theirs and keep running.

Your README deserves a live link.

Paste your repo, copy the button, and send people somewhere they can click.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·