Git-push deploys
Connect a GitHub or Gitea repository. Every push builds and deploys, and any running build can be cancelled.
Chapong turns every git push into a deploy — previews for each pull request, instant rollback, automatic HTTPS — running on a dedicated server that’s yours alone.
$ avoca link
# linked to site “my-app”
$ git push origin feature/checkout
# → preview deploy built, commit status posted to the PR
$ avoca deploy --prod
# → health check passed, traffic switched atomically
$ avoca rollback dpl_8f2c
# → previous build is live again, instantly
Features
The workflow teams love — git-driven deploys, previews, rollbacks — without sharing a machine with anyone else.
Connect a GitHub or Gitea repository. Every push builds and deploys, and any running build can be cancelled.
Node 22 and Python. Static sites and SPAs, plus server apps like Next.js, Nuxt and Express with health-checked swaps.
Deploys are immutable. Rolling back is an atomic pointer switch to a previous build — no rebuild, no wait.
A unique URL for every deploy and every pull request, with a commit status posted back to your repo.
Point a CNAME and certificates are issued automatically. www ↔ apex redirects are handled for you.
Production, preview and shared scopes. Secrets are masked in the dashboard and logs.
One click connects a site to a Da8a backend and keeps SUPABASE_URL, ANON_KEY and auth redirect URLs in sync.
Response cache that purges itself on every deploy, plus Web Vitals and analytics for each site.
Password-protect any deploy. Deploy hooks let your CMS trigger a rebuild with a single POST.
How it works
Pick a GitHub or Gitea repository. Chapong detects the framework and sets up build and start commands.
Every push builds. Pull requests get their own preview URL and a commit status, so reviewers can click and check.
Promote to production — server apps pass a health check before traffic switches. Something off? Roll back instantly.
CLI
The avoca CLI does everything the dashboard does for deploys: ship a preview or production build, list and create sites, inspect deployments and roll back.
$ avoca sites create --name my-app
$ avoca sites list
$ avoca deploy # preview
$ avoca deploy --prod # production
$ avoca deployments
$ avoca rollback <id>
Compare
Chapong sits between a multi-tenant hosting platform and a server you manage by hand.
| Chapong | Typical multi-tenant PaaS | Self-managed VPS | |
|---|---|---|---|
| Runs on a dedicated server | Yes — yours alone | Shared infrastructure | Yes |
| Your data stays on your server | Yes | Provider’s infrastructure | Yes |
| Git-push deploys | Built in | Built in | Build it yourself |
| Preview URL per pull request | Built in | Usually | Build it yourself |
| Instant rollback | Atomic switch | Usually | Manual |
| Automatic HTTPS + redirects | Built in | Built in | Configure yourself |
| Backend env vars kept in sync | Linked Da8a backend | Via integrations | Manual |
| Noisy neighbours | None | Possible | None |
Pricing
Every plan includes git-push deploys, previews, custom domains with HTTPS, instant rollback and the CLI. Move a project from shared hosting to your own server in one click.
Shared hosting
$0/mo Launching soon
Shared hosting
$7/mo Launching soon
Your own server · 2 vCPU / 4 GB
$39/mo
Your own server · 4 vCPU / 8 GB
$99/mo
Your own server · 8 vCPU / 16 GB
from $349/mo
FAQ
Your sites build and run on a dedicated server provisioned for you. No other customer’s workloads share it, so there are no noisy neighbours, and your code, builds and logs stay on that server.
Node 22 and Python. Static sites and single-page apps are served directly; server apps such as Next.js, Nuxt and Express run as processes and are health-checked before traffic is swapped to a new version.
Yes. Connect a repository from either; pushes trigger deploys and pull requests get a preview URL with a commit status.
Each deploy is kept as an immutable build. Rolling back switches the live pointer to an earlier build atomically, so there’s nothing to rebuild.
Connect a site to a Da8a backend with one click. Chapong then keeps SUPABASE_URL, the anon key and your auth redirect URLs in sync — including for preview deploys.
A Free / Hobby shared tier is coming soon. Today, Chapong runs on a dedicated server.
Yes. Create a deploy hook and have your CMS send a POST to its URL whenever content changes. See deploy hooks.
Connect a repo and get your first preview URL in minutes.