Isolated sites on shared hosting
On the shared pool, each site builds and runs as its own sandboxed system user, separate from other sites.
Security
Security built into how Chapong works
The practical protections in the platform today, described plainly.
Your own server
On an own-server plan, your sites run on a dedicated server that runs only your projects. Your code, builds, logs and Da8a database stay on it.
Write-only secrets
Secrets can be set or replaced but not read back: the dashboard and build logs mask them, and backend function secrets only ever show their names.
Deployment protection
Password-protect any deploy, so previews and staging sites are only seen by the people you share them with.
HTTPS everywhere
Certificates are issued automatically for default addresses and custom domains.
Scoped, revocable access tokens
CLI and API access uses personal access tokens. Deploying needs the sites scope, and you can revoke a token from the dashboard. API calls run as you, with the same permission checks as the dashboard.
Databases kept off the internet
For Da8a projects on your server, SQL from the CLI runs as a job on that server; the database isn’t exposed to the internet for it.
An assistant that asks first
McManus, the built-in assistant, proposes changes and explains them. Nothing changes until you click Apply.
Immutable deploys
Every deploy is kept as an immutable build, so you can always return to a known-good version instantly.
Your part
A few habits that keep your sites safe on any platform.
- Never put secrets in variables your framework exposes to the browser, such as
VITE_ones - Keep a Da8a
service_rolekey on servers only: it bypasses Row Level Security - Treat deploy hook URLs like passwords and rotate them if they leak
- Revoke access tokens you no longer use