Quick Start

Getting Started with Apployd

Use this guide to move from a new workspace to your first reliable production deployment using Apployd workflows.

What Apployd is designed for

Apployd is a deployment and operations platform for SaaS teams that need predictable releases, secure configuration handling, and clear runtime visibility.

The goal is not only to deploy quickly, but to keep release quality, reliability, and operational ownership consistent as your product grows.

Initial setup flow

Create a workspace, connect your repository, and define runtime settings such as build command, start command, and target port.

Add environment secrets before first launch so the application can boot correctly in production-like conditions.

  • Create workspace and select organization context.
  • Connect source repository and branch.
  • Configure runtime commands and service settings.
  • Add required environment secrets.
  • Run first deployment and verify health.

Choose the correct project type before first deploy

Apployd supports three main deployment modes. Choose the one that matches how your application runs in production, then fill the runtime fields for that mode instead of leaving them generic.

Set Root directory for monorepos, confirm the app binds to 0.0.0.0:$PORT, and add required environment variables before the first production deployment.

  • Web Service: use for Node.js APIs, SSR apps, and full-stack services. Typical values are root apps/api, build npm run build, start npm run start:prod, port 3000.
  • Python: use for Django, Flask, and FastAPI. Typical values are root backend, optional build python manage.py collectstatic --noinput, start uvicorn main:app --host 0.0.0.0 --port $PORT, port 3000.
  • Static Site: use for React, Vue, Vite, Astro, and exported Next.js apps. Typical values are root apps/web, build npm run build, output directory dist, and no start command.
Use Static Site only when the project builds to files. If the app needs SSR, API routes, or a persistent Node server, choose Web Service instead.

How to start safely

Begin with one critical service, validate your deployment process and rollback path, then roll the pattern out across additional services.

Recommended: document your release checklist internally before scaling to multiple production services.