Bring the platform online

Three gates to live: stack preflight → data layer & mail relay → lock the install.

1Stack preflight

2Settingsure the data layer

3Lock the install

Stack preflight

Readiness probe across the runtime, Python modules, optional database clients, and writable paths. Hit Install on any failed row to let the wizard remediate it. The Proceed lever arms only when every required probe is green.

0cleared

0blocked

0advisory · optional

Admin escalation · sudo key

Hand the wizard a one-shot sudo password if any system package (gcc, libpq-dev, build-essential) needs to land via apt. The credential is piped straight into sudo per install — never written to disk, never logged. Leave blank to handle system packages yourself and the wizard will surface the manual command instead.

Probing the runtime…

Brand stamp

Burned into the topbar, every outbound email, and the lobby header.

Brand name

Data layer

Ship SQLite for a fast local probe, PostgreSQL for production traffic, MySQL for the pure-Python lane.

SQLite — zero-settings local file PostgreSQL — production-grade MySQL — pure-Python driver

Host

Port

Database name

User

Password

Probe the socket before committing the install.

Root admin

First sign-in credential for the admin console — keep this under lock.

Admin email

Admin password (min 8 chars)

Outbound mail relay

Optional — drives welcome mail, payment receipts, renewal nudges, and admin campaigns. Skip now and wire it later from Admin → Settings → SMTP without re-running the wizard.

SMTP host

SMTP port

SMTP user

SMTP password

From email

From name

STARTTLS (port 587) Implicit SSL (port 465)

Edge & session

Public URL is what tenant EAs dial home to. Session secret is minted locally — keep it cold.

Public server URL

Session secret

Advanced — tenant limits & rate limits

Limit ladder — signals per cycle

Trial

Basic

Pro

Rate ceiling / min