Docs

Deployxa Cloud

One control plane, from push to production.

Connect a repository and deploy. Zero-config builds, autoscaling, automatic TLS and domains, logs and metrics, and team access in a single platform.

See pricing

No credit card required.

Deploy any stack: frameworks, runtimes and containers

01 / Deployments

Push to deploy. We handle the rest.

Every commit triggers a build in an isolated container: static output or a Docker image, depending on your stack. No servers to maintain, no pipeline to write.

  • Framework, runtime and package manager detected from the repo
  • Health-checked rollout before traffic switches
  • Preview deployments for every branch on Pro and up
~/my-app
$ git push origin main→ Webhook received · cloning main→ Detected Next.js · running next build→ Image built with cache · pushing→ TLS certificate issued (Let's Encrypt)→ Health check 200 OK · switching traffic✓ Live at https://my-app.deployxa.online

02 / Scaling

Capacity that follows your traffic.

Deployxa watches CPU, memory and request rate and adds load-balanced replicas when traffic spikes, then scales back down when it settles.

  • Requests balanced across healthy replicas
  • Scale idle apps down to save resources
  • Dedicated cores for production plans

03 / Security

Hardened from commit to runtime.

Every app runs in its own container namespace on a private network. Only the TLS-terminating proxy can reach it. Secrets are stored encrypted and injected at runtime.

  • Private networking between your services
  • Edge filtering for abusive Layer 7 traffic
  • Encrypted environment variables, never in build logs

04 / Observability

See what your app is doing.

Track CPU, memory and bandwidth per project, and stream stdout and stderr live while you debug. Every request is logged with method, path, status and response time.

  • Live log streaming from build and runtime
  • Per-project resource charts
  • Alerts by email, Slack or webhook when errors spike
logs · my-app · production
12:04:11 GET  /api/projects 200 18ms12:04:12 POST /api/auth     201 42ms12:04:12 GET  /dashboard    304 6ms12:04:14 GET  /api/metrics  200 23ms12:04:15 GET  /docs/missing  404 9ms12:04:17 POST /api/orders   200 61ms

05 / Teams

Built for teams that ship together.

Group projects in an organization, give each member the role they need, and keep a record of every deploy and settings change.

  • Owner, Admin, Developer and Billing roles
  • One invoice across every project
  • Audit log of deploys, domains and secrets changes

06 / Platform

Everything around the deploy.

Every deployment includes

  • Automatic TLS certificates with HTTPS redirects
  • Zero-downtime rollbacks to any previous release
  • Health checks verified before traffic switches
  • Encrypted secrets, environment variables and API keys
  • Managed PostgreSQL, MySQL and Redis with backups
  • Custom domains and DNS on every plan

07 / Production grade

Engineered for real workloads.

The subsystems behind builds, routing, data and compliance as your app grows.

  • HTTP/3 and QUIC

    Modern UDP-based transport for faster handshakes, especially on unstable mobile connections.

  • Custom ingress rules

    Rewrite headers, map paths to services and set rate limits with advanced reverse-proxy routing.

  • Private networking

    Connect containers to private databases in AWS, GCP or Azure through VPC tunnels and private endpoints.

  • Audit trails

    Every deploy, environment change, CLI command and sign-in is recorded for later review.

  • Build cache

    Node modules, PyPI packages and Cargo dependencies are cached between builds, so repeat builds run faster.

  • Point-in-time recovery

    Restore a database to an earlier point in time after a bad migration or accidental delete.

Plan limits for CPU, memory and storage are on the pricing page.

08 / FAQ

Common questions.

How does scaling handle cold starts?

Replicas start from prepared images when load rises, and idle apps can scale down to save resources. On the free plan, an app that has been idle wakes on its next request, so that first request takes a little longer.

Can I use apex domains and wildcard DNS?

Yes. Point a root domain at Deployxa with CNAME flattening or A records. Certificates, including wildcard certificates via DNS-01 validation, are issued and renewed automatically with Let's Encrypt.

How are workloads isolated from each other?

Every app runs in its own container with separate namespaces, network and resource limits. Workloads do not share file systems or storage. Security controls are designed to support future compliance work such as SOC 2.

Do you support monorepos and private submodules?

Yes. Point a project at a workspace directory (Turborepo, Nx, Yarn or pnpm workspaces) and set build and output settings per project. Private submodules are fetched with your Git provider token.

Are databases provisioned for me, and how are backups handled?

Add PostgreSQL, MySQL or Redis to a project and Deployxa provisions it on SSD storage. Snapshots are taken automatically, and you can restore to an earlier point in time.

How does billing work for teams?

Usage across every project in an organization rolls up into one bill. Role-based access control keeps members from changing plans or resources they should not touch.

Ready when you are

Ship your next app on Deployxa.

Free to start. The same pipeline runs on every plan.

Read the docs