Deploying
How deployments work
Build types, what happens during a deploy, deployment states, runtime limits and timeouts, Deploy vs Reload, rollback, cancel and the monthly allowance.
Build types
Set on the project's General tab under Build Type, then Save.
| Build Type | What MarvX does |
|---|---|
| Nixpacks (default) | Detects your language and builds with Nixpacks. A root Dockerfile, if present, is used instead. |
| Dockerfile | docker build with the root Dockerfile, using the repository root as context |
| Cloud Native Buildpacks | Builds with the Paketo buildpacks builder |
| Static site (nginx) | Serves files with nginx, no build step (see Language guides and static sites) |
Deploy from Image skips the build. A saved Docker Compose file overrides both. See Dockerfiles, images and Compose.
What happens during a deploy
- queued: waiting for a builder.
- deploying: shallow clone of the branch (no submodules), image build, then the running container is replaced.
- About 10 seconds after start, MarvX checks the container: running means succeeded; exited or crash-looping means failed.
Build errors show on the Deployments tab (full text on AI Debug); runtime output on Logs. There's no HTTP health check, so an app on the wrong port still shows succeeded and returns 502.
Runtime limits
- Memory per app: Free 512 MB, Starter 1 GB, Pro 2 GB, Enterprise 8 GB. Exceeding it kills the app (exit code 137).
- CPU and process count: capped per app at a platform default (contact support for values).
- Crashed apps restart automatically unless you stopped them.
Timeouts
| Step | Limit |
|---|---|
| Git clone | 5 min |
| Nixpacks or Dockerfile build | 15 min |
| Buildpacks build | 20 min |
| Static site build | 10 min |
| Docker Compose up | 20 min |
Deploy Settings buttons
| Button | Effect |
|---|---|
| Deploy / Rebuild | Fresh build of the latest commit with current settings |
| Reload | Restarts the container in place; does not apply new variables or settings |
| Stop / Start | Takes the app offline / back online; volumes and settings kept |
| Open Terminal | Shell inside the running container |
| Autodeploy | Deploy on every push (GitHub) |
Changes to variables, volumes, ports or build settings apply on the next Deploy.
Roll back and cancel
- Rollback (project Deployments tab or Deployments page) works on any succeeded deployment. It redeploys that deployment's image without rebuilding, with your current variables and settings.
- Cancel stops a queued deployment. If the build already started it may still finish, so check afterwards and roll back if needed.
Monthly deployment allowance
Free 10, Starter 100, Pro 500, Enterprise unlimited per calendar month (UTC). Every deployment you start counts, including failed ones, pushes, rollbacks and a new project's initial deploy. Redeploys MarvX makes to apply domain changes, and preview deployments, don't count. When the allowance is used up, deploys are refused ("you've used all … deploys…"); paid plans can buy a 100 deploys pack or upgrade. See Plans, limits and add-ons.