FREE CRM

Before you deploy

Ready is a checklist.
Not a green button.

Choose a path, confirm every boundary, then deploy with credentials that stay in your account. This page links each check to the authoritative repository guidance.

Start the check ↓
01

NO CLOUD KEYS

Local device or Docker

No cloud account, identity provider, or API key is required. Keep the listener private and back up the state you own.

  1. Supported runtime

    Node.js 22.13.0 or newer for native use, or a current Docker installation.

    Device requirements ↗

  2. Reviewed repository state

    Use a clean clone of the release or protected main, preserve package-lock.json, and run the release checks before trusting a change.

    Release verification ↗

  3. Private runtime choice

    Use the loopback-only launcher or Docker volume. Do not expose local-owner mode directly to the internet.

    Device and Docker guide ↗

  4. Identity and credentials

    Local-owner mode is only for loopback access. Local operation needs no cloud identity provider and no cloud credentials.

    Security deployment checklist ↗

  5. Database and files

    Confirm the local D1/SQLite state directory or Docker volume is persistent and included in your backup routine.

    Ownership and limits ↗

  6. Cost and capacity

    The software is free. Your device, storage, backups, and network remain your responsibility; review the documented record envelope.

    Current limits ↗
02

YOUR PROVIDER ACCOUNTS

User-owned cloud

Cloud credentials belong only in your provider secret store. Production stays sealed until storage and exact-owner identity are verified.

  1. Runtime and release path

    Choose native Vercel or the protected Cloudflare first-install path. Only reviewed main should become production.

    Runtime comparison ↗

  2. Exact-owner identity

    Configure GitHub OAuth on Vercel or an exact-owner Cloudflare Access policy before entering data.

    Identity setup ↗

  3. Durable database

    Provision user-owned D1 and apply the canonical migrations; Vercel additionally needs the narrowly scoped D1 RPC boundary.

    D1 data plane ↗

  4. Private object storage

    Use private R2 on Cloudflare or private Vercel Blob. Do not enable a public bucket or object URL.

    Private file storage ↗

  5. User-supplied credentials

    Create least-privilege, short-lived provider credentials and store them as encrypted environment values—not source, commands, screenshots, or logs.

    Credential handling ↗

  6. Provider cost and quotas

    FREE CRM has no subscription fee, but infrastructure providers may charge. Check current storage, request, build, and identity quotas in your own accounts.

    Runtime ownership notes ↗

  7. Recovery and verification

    Verify the identity gate, health response, provider recovery copy, and a portable export before calling the deployment ready.

    Recovery boundary ↗

EVERY CHECK COMPLETE?

Deploy sealed.
Verify before data.

Choose a deployment path →Stay in the synthetic tour