One click. Any cloud.
Your users click it and run your project on zopcloud, or on their own AWS, GCP or Azure.
One line in your README.
You add it once. Your users pick where it runs.
What lands in their cloud.
All of it runs in your user’s own AWS, GCP or Azure account.
Your app, built
zopday builds it from the repo with no Dockerfile required. Or it runs your image.
A Helm release
Deployed as a standard Helm release on their GKE, EKS or AKS cluster, with one-click rollback.
A URL with TLS
Routed through the cluster’s ingress, with DNS written for them and certificates from cert-manager.
A database
MySQL, Postgres or Redis in their cloud, with HA, backups and deletion protection.
Environment variables
Sensitive values are masked and stored in their cloud-native secret manager, never ours.
An audit trail
Every change is logged with who, what and when, so they can see what happened to a release.
What your users can run.
The kinds of project zopday is built for.
Web apps
A full app, frontend and backend, built from the repo with no Dockerfile.
Static sites
A landing page, a portfolio, or the output of any static site generator.
APIs and backends
A REST API, a bot, a scheduled job. Attach MySQL, Postgres or Redis when it needs to remember things.
Starter templates
Ready-made applications and datastores from our Helm charts, installed in one click.
Questions maintainers ask.
Before they put anything in their README.
Does it cost my users anything?
On their own cloud, their cloud provider bills them for what runs there, and zopday's Free plan costs nothing. On zopcloud, it is free to start, with no card to enter.
Do I need to change my repo?
No. The buttons are one line each in your README. There is no config file to add, and zopday builds from your repo with no Dockerfile required.
What if my project needs a database?
Your users create MySQL, Postgres or Redis in their own cloud from zopday and connect 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. What your users already deployed keeps running in their cloud: it is a standard Helm release on their cluster.
Give your project a one-click way in.
Paste your repo, copy the buttons, and let your users choose where it runs.