Self-host docs

Run Flowstace locally with Docker and keep the OSS path intact.

This setup boots PostgreSQL and the Next.js app locally. AI and Stripe are optional. The product works as a self-hosted agency workspace without either integration.

Back to landing Create local workspace

Quick start

1. Prepare env

Copy `.env.example`, set the database URL, Better Auth values, and choose whether AI, email delivery, or Stripe should stay enabled.

2. Start Docker

Bring up Postgres and the Next.js app with `docker compose up --build`. The web container installs deps, pushes the schema, and starts dev mode automatically.

3. Create the first org

Open the app, sign up, and complete onboarding. For self-hosted OSS use, choose the `OSS` plan in onboarding.

4. Optional SaaS config

If you later want hosted billing behavior, add Stripe price IDs and webhook secret, then expose `/api/billing/webhooks/stripe` publicly.

5. Optional automation cron

Set `AGENCYOS_AUTOMATION_SECRET` and call the daily and weekly digest endpoints from cron. This keeps email digests available without adding a separate worker yet.

Commands

cp .env.example .env
docker compose up --build

# optional, outside Docker
npm install
npm run db:push
npm run dev:web

# optional daily digest cron
curl -X POST http://localhost:3000/api/automation/digests/daily \
  -H "Authorization: Bearer $AGENCYOS_AUTOMATION_SECRET"

# optional weekly digest cron
curl -X POST http://localhost:3000/api/automation/digests/weekly \
  -H "Authorization: Bearer $AGENCYOS_AUTOMATION_SECRET"

Operational notes

Every data query is organization-scoped. The first onboarding run creates the first tenant membership.
Choose `OSS` during onboarding if you want AI features locked by default.
Stripe billing is optional for self-host. Without it, Billing renders safely but checkout stays unavailable.
Email 2FA on paid plans works with Resend, or falls back to local capture/logging in development when no mail provider is configured.
Daily and weekly digests can be triggered by cron through `/api/automation/digests/daily` and `/api/automation/digests/weekly` with the automation bearer secret.
If Prisma schema changes while Docker is already running, rerun `docker compose exec -T web npm run db:push` and restart `web`.