Docs

Deployment Intelligence Engine

Automatic, and explained.

Every platform says it deploys automatically. Deployxa shows you what the engine decides: framework, package manager, runtime, Docker, health checks, rollbacks, SSL, CDN and scaling.

See every step
deployxa · engine scan
→ Scanning repository tree…✓ Framework: Next.js 14 (App Router)✓ Package manager: pnpm (pnpm-lock.yaml)✓ Runtime: Node 20 (engines.node)→ Generating multi-stage Dockerfile…✓ Image built · non-root user · layer cache✓ Health probe /api/health 200 OK✓ TLS issued · CDN cache invalidated✓ Ready to promote: https://my-app.deployxa.online

01 / What it automates

Nine decisions, made from your repo.

No YAML and no buildpack guessing. The engine writes the plan from what is already in your repository.

  • Framework detection

    Scans package.json, config files, monorepo layouts, and source structure to identify Next.js, React, Vue, Laravel, Express, NestJS, FastAPI, Django, static sites, and more. Picks the correct build command and output directory automatically.

    • next.config.*
    • vite.config.*
    • composer.json
    • requirements.txt

    Framework: Next.js 14 · Build: next build · Out: .next

  • Package manager detection

    Lockfiles decide the installer. We honor pnpm-lock.yaml, yarn.lock, package-lock.json, bun.lockb, Pipfile.lock, poetry.lock, and composer.lock so installs match your local machine and CI stays reproducible.

    • pnpm-lock.yaml
    • yarn.lock
    • package-lock.json
    • bun.lockb

    Package manager: pnpm · Install: pnpm install --frozen-lockfile

  • Runtime detection

    Engines fields, .nvmrc, .node-version, runtime.txt, and Docker base images pin Node, Python, PHP, Go, and friends. No “works on my machine” version drift between laptop and production.

    • engines.node
    • .nvmrc
    • runtime.txt
    • go.mod

    Runtime: Node 20 LTS · Python 3.12 · PHP 8.3

  • Docker generation

    When no Dockerfile exists, the engine synthesizes a hardened multi-stage build: install deps, build app, slim runtime image, non-root user, health endpoint. Bring your own Dockerfile and we use that instead.

    • multi-stage build
    • non-root user
    • layer cache
    • distroless-ready

    Generated Dockerfile · image optimized · ready to ship

  • Health checks

    After the container starts, we probe your health route (or a sensible default). Traffic flips only on clean responses. Failed probes stop the rollout before users see a broken deploy.

    • GET /health
    • GET /api/health
    • custom path
    • startup grace period

    Probe 200 OK · promote to production

  • Rollbacks

    Every successful image is versioned. One click (or API call) re-routes traffic to a previous known-good release — no full rebuild required.

    • image history
    • traffic flip
    • zero rebuild
    • one-click restore

    Rolled back to v4.2.0 · no rebuild

  • SSL

    Certificates are issued and renewed automatically for Deployxa subdomains and custom domains. TLS 1.3 by default, HSTS-ready, zero manual Certbot steps.

    • Let's Encrypt
    • TLS 1.3
    • auto-renewal
    • wildcard ready

    Certificate active · https://app.deployxa.online

  • CDN

    Static assets and edge routes fan out to our global CDN on every deploy. Cache invalidation rides with the release so users never get stuck on stale JS after a push.

    • Anycast edge
    • cache bust on deploy
    • gzip / brotli
    • geo routing

    Cache invalidated on deploy · assets compressed

  • Scaling

    Horizontal scaling reacts to CPU, memory, and request load. Scale-to-zero for idle free tiers; dedicated cores for production. No capacity planning spreadsheet required for day one.

    • HPA signals
    • scale-to-zero
    • load balanced

    Replicas 1 → 4 under load · auto cool-down

02 / Why it matters

Intelligence is the product.

When an AI tool hands you a full-stack app, you do not want a YAML tutorial. You want an engine that detects the stack, builds the container, wires up SSL and CDN, checks health and scales.

  • Zero-config for AI-generated and hand-written apps
  • Deterministic installs from lockfiles and engine pins
  • Safe rollouts with probes and instant rollbacks
  • Production networking (SSL and CDN) without tickets
Detect → Build
framework · package manager · runtime
Ship → Secure
Docker · SSL · CDN
Run → Recover
health checks · scaling · rollback

Ready when you are

Push code. Let the engine decide.

Start free. The same intelligence pipeline runs on every plan.

How it works