Skip to content
Apply for the pilot
In pilot

Push to GitHub, and it’s running.

Dekka builds every push, gives each pull request its own preview and keeps the last good deploy one step away. Your web apps, APIs, workers and scheduled jobs run side by side and reach each other on a private network.

Apply for the pilotRead the docs
storefront · DeploymentsExample project
  • Fix the checkout total3f2a9c1 · mainLive
  • Add mobile money receiptsb81e4d0 · pr-142Preview
  • Cache product images9c07a2e · mainPrevious
  • Upgrade to Next.js 1651d3f88 · mainFailed
  • Add the orders pagee2a61b7 · mainPrevious
Build log3f2a9c1
  1. 1Cloning example/storefront at 3f2a9c1
  2. 2Installing dependencies with pnpm
  3. 3Building the Next.js app
  4. 4Image built and pushed
  5. 5Starting 2 replicas in gh-1
  6. 6Health check passed on /
  7. 7Routing storefront.apps.dekka.cloud to the new deploy
Push to deployEvery commit to your branch builds in isolation and ships.
Preview environmentsEach pull request gets its own temporary copy to try.
RollbacksReturn to any earlier successful deploy in one step.
Custom domainsBring your domain, and Dekka handles the certificate.
Variables and secretsConfiguration per service, with secrets encrypted and revealed only on purpose.
Private networkingServices find each other by name on dekka.internal.
Health checksUnhealthy instances are noticed and restarted.
Logs and metricsBuild and runtime logs, with CPU, memory and health over time.
Workers and cron jobsBackground workers and scheduled tasks beside your web services.
ScalingSet CPU, memory and replicas for each service within your plan.
VolumesDurable storage for the services that need to keep files.
Deployment historyEvery release with its commit, its log and who shipped it.

The rest of Dekka