Framework guides

Deploy the framework you already use.

Deployment guides for Node.js, Python, PHP, Go, Rust and Docker apps: what Deployxa detects, the build and start commands, environment variables and common questions.

01 / Guides

Pick your stack.

02 / Detection

Recognised from your repository.

Deployxa looks for these files to choose a runtime and build. Anything else ships with a Dockerfile.

  • next.config.js
  • package.json
  • vite.config.ts
  • nest-cli.json
  • artisan
  • composer.json
  • index.php
  • manage.py
  • requirements.txt
  • pyproject.toml
  • alembic.ini
  • go.mod
  • Cargo.toml
  • Dockerfile
  • app.py
  • wsgi.py
  • nuxt.config.ts
  • nuxt.config.js
  • svelte.config.js

03 / Included

The same platform for every stack.

  • Stack detection

    Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.

  • Isolated builds

    Every push builds in its own sandbox with cached dependencies and layers.

  • Managed databases

    Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.

  • HTTPS by default

    Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.

  • Health-checked releases

    Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.

  • Push to deploy

    Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.

Ready when you are

Not on the list?

Add a Dockerfile and Deployxa builds and runs it like any other app.

Docker guide