Every push to your production branch triggers a new deployment. Deploxa builds your app, uploads it to the CDN, and atomically switches traffic — with zero downtime.
Git push detected
The GitHub App webhook fires on every push to a connected branch. Deploxa creates a Deployment record and queues a build.
Builder starts
An isolated build container (ECS Fargate) starts. Each build runs in a completely fresh environment — no shared state between builds.
Repo cloned
Your repository is cloned at the specific commit SHA. Submodules are initialized if present.
Dependencies installed
npm install / pip install / etc. is run. Build cache is used when available to speed up repeat builds.
Build runs
Your configured build command is executed. Output is streamed in real-time to the build log.
Artifacts uploaded
The output directory is compressed and uploaded to S3. Node.js and Next.js SSR builds are also packaged into a Lambda.
Traffic switched
The proxy is updated to route all traffic for your domain to the new deployment. Previous deployment stays available for instant rollback.
The build is waiting for an available build slot. Paid plans have priority queue access.
The builder is cloning your repo, installing dependencies, and running your build command.
Build artifacts are being uploaded to the CDN and the deployment is being activated.
Your deployment is live and serving traffic. This is the active production deployment.
The build or deployment failed. Check the build log for the root cause.
The deployment was manually cancelled before it completed.
Every pull request gets a unique, isolated preview URL. The preview is updated on each commit push to the PR branch.
Preview deployments use the same environment variables as production unless you configure per-environment overrides. See the Env Vars guide.
Rolling back to a previous deployment does not trigger a rebuild. Deploxa switches traffic to the previously uploaded artifacts instantly — typically under 5 seconds.
How to rollback
No rebuild required
Build logs stream in real-time via WebSocket while a deployment is in progress. After completion, logs are persisted and remain accessible from the deployment detail page.
Automatic. Fires on every push to a connected branch.
HTTP POST to a unique URL. Useful for CMS webhooks, CI systems, and cron-triggered rebuilds.
Click Redeploy on any previous deployment from the dashboard.
POST to a deploy hook URL from your own pipeline or scheduler.
Happy with a preview, or with an older build? Promote it and it becomes the live deployment immediately — no rebuild. Promotion re-points your production URL at that already-built artifact and invalidates the proxy cache, so it is effectively instant. Rollback is the same mechanism in reverse.
| Limit | Free | Pro | Team |
|---|---|---|---|
| Builds / month | 100 | Unlimited | Unlimited |
| Concurrent builds | 1 | 3 | 10 |
| Build timeout | 10 min | 30 min | 60 min |
| Build memory | 512 MB | 2 GB | 8 GB |
| Log retention | 7 days | 30 days | 1 year |
