⚡ Drop to DeployDocs

Product demo

Watch a deployment, start to finish.

Push to Git and Deployxa detects your stack, builds it, health-checks the release and serves it over HTTPS. Here is every step.

How it works

01 / Replay

One push, one live URL.

~/bun-docker
$ git push origin main→ Cloning render-examples/bun-docker@main→ Detected: Dockerfile (port 8080)→ Building image… done in 118.9s→ Starting container… health check 200 OK✓ Live at https://bun-docker.deployxa.online

02 / Walkthrough

What happens on every push.

  1. 01 /

    Connect a repository

    Link GitHub, GitLab or Bitbucket, or deploy from your terminal with the Deployxa CLI.

  2. 02 /

    Stack detection

    Deployxa reads your lockfiles and config to pick the build command, runtime and port, or uses your Dockerfile.

  3. 03 /

    Build and go live

    The app is built in an isolated sandbox, health-checked, and served over HTTPS on a .deployxa.online URL or your own domain.

  4. 04 /

    Roll back

    Previous releases are kept, so you can switch traffic back to a known-good version without rebuilding.

03 / Release

Know exactly where a release stands.

The dashboard shows each stage as it runs, with the full build log, so a failed step is easy to find.

  • Live build and runtime logs
  • Health check before traffic switches
  • Automatic TLS certificates
  • One-click rollback to a previous release
See the full pipeline

04 / After deploy

What the dashboard shows once you are live.

The demo stops at the live URL. This is what you work with from then on.

  • Release phases

    Each deployment moves through Queued, Build, Release and Live. A failure marks the exact phase that broke and stops the rollout there.

  • Build and runtime logs

    Logs stream while the build runs and stay attached to the deployment afterwards, so you can read back exactly what happened on any release.

  • Metrics

    CPU, memory, requests per hour, average and p95 latency, 5xx error rate and storage, per project and across your organization.

  • Rollback

    While the previous release is held on a warm standby, rollback swaps traffic back without a rebuild. After that window it redeploys the previous image from cache.

  • Environment variables

    Edit variables one by one or paste a whole .env file in bulk mode. Secret values stay masked until you choose to reveal or copy them.

  • Preview environments

    On plans with previews, pull requests get their own isolated environment and URL, removed when the PR is closed or merged.

05 / CLI

The same flow from your terminal.

The Deployxa CLI (@deployxa/cli on npm) covers the demo end to end: it links or creates the project, uploads your source, builds it remotely and streams the result.

  • deployxa deploy --watch redeploys as you save
  • Rollback targets: latest, previous, production or a deployment ID
  • deployxa promote ships the latest successful preview
  • --json output for scripts and CI
CLI reference
terminal · my-app
# install and sign in (browser login, or --token in CI)$ npm install -g @deployxa/cli$ deployxa login# deploy the current folder and follow it$ deployxa deploy$ deployxa status$ deployxa logs# configuration and health$ deployxa env set API_KEY <value>$ deployxa env pull   # writes .env.local$ deployxa metrics# something wrong? go back$ deployxa rollback previous

06 / FAQ

Questions about the demo.

Is the replay above a real deployment?

It is a scripted replay of the steps a typical deployment goes through, so you can see the order of events without signing up. Your own deploy log will show your build commands and output.

Do I need a Dockerfile?

No. Deployxa detects common stacks such as Next.js, React, Vue, Laravel, Django, FastAPI, Express and Go from your project files. If you do have a Dockerfile, it is used as-is.

Can I do everything from the terminal instead of the dashboard?

Most day-to-day work, yes. The CLI deploys, streams logs, shows status and metrics, manages environment variables and domains, promotes previews and rolls back. Billing and team settings are easiest in the dashboard.

What does a rollback actually do?

It points traffic at an earlier successful release. Shortly after a deploy the previous release is still warm, so the switch needs no rebuild; later on, Deployxa redeploys that release from its cached image.

Will a free app stay online?

Free apps go idle after 20 minutes without requests and wake on the next one, so that first request has a short cold start. The idle rule is part of the Free plan; see pricing for plan details.

Ready when you are

Deploy your first app.

Start on the Free plan and watch your own build go live.

See pricing

No credit card required.