Documentation
From git push to live.
Deploy static sites to European, GDPR-compliant infrastructure. Guides for every step: connect a repository, ship a build, put it on your domain.
Start here
- 01 Connect your repository
GitHub, GitLab, Bitbucket, or Codeberg — pick a repo and a branch.
- 02 Push to deploy
Builds run in isolated jobs. Commits on the default branch go live automatically.
- 03 Add your domain
Point DNS at deploybase and the SSL certificate is provisioned for you.
Deploy your framework
Concepts
- Build System
- Builds run in isolated Kubernetes Jobs with per-framework images and resource limits.
- Deployments
- An immutable snapshot of built files. Every successful build produces one.
- Preview Deployments
- Every non-default branch gets an automatic public preview URL, served from CDN.
- Share Links
- Send any deployment to a stakeholder, with optional password protection and expiry.
- Teams
- The multi-tenancy boundary: every project, domain, and plan belongs to one team.
- Projects
- A static site with its git source, build configuration, and deployment history.
Guides
- Custom Domains
- Add your own domain with DNS verification and automatic SSL provisioning.
- Environment Variables
- Build-time variables scoped per environment, encrypted at rest with AES-256-GCM.
- Rollbacks
- Promote any earlier deployment back to production. Instant, and no rebuild.
- Forms
- Collect submissions from any site with spam filtering and GDPR-compliant storage.
- API Keys
- Create dbk_ keys for programmatic access from CI, scripts, and the MCP server.
- DNS Providers
- Which Dutch and German providers support ALIAS/ANAME records for root domains.
Build on the API
Everything in these docs is scriptable. The dashboard, the CLI-style curl examples
on these pages, and the MCP server are all clients of the same REST API.
https://api.deploybase.eu