Manage ɳSelf projects under the multi-tenant master controller.

Each project is fully isolated: dedicated Postgres schema, Hasura metadata source, Nginx virtual host, JWT secret, Redis key prefix, and MinIO bucket.

Requires: NSELF_FLAG_MULTI_TENANT_CONTROLLER=true

nself project <subcommand> [flags]

Provisions a new project in under 10 seconds (p50 target: 4s).

nself project create --slug <slug> --domain <domain>

Steps: schema + role provisioning, Hasura source registration, Nginx vhost generation, JWT secret generation.

Example:

nself project create --slug myapp --domain myapp.myserver.com
# Project ready: https://myapp.myserver.com (id: abc123...)

Deletes a project and removes all associated resources. Irreversible.

nself project delete --slug <slug> --force

Teardown sequence: Hasura source deregistered, Nginx vhost removed, Redis keys flushed, MinIO bucket dropped, Postgres schema + role dropped, audit log written.

Lists all projects managed by the controller.

nself project list

Output:

SLUG    DOMAIN                  STATUS  CREATED
myapp   myapp.myserver.com      active  2026-04-23T10:00:00Z

Shows health and resource stats for a single project: connection count, schema size, last active.

nself project status --slug <slug>

Runs pending database migrations for a project schema. Delegates to nself deploy with the project schema targeted.

nself project migrate --slug <slug>

Opens a psql shell authenticated as the per-project role, with search_path set to the project schema.

nself project shell --slug <slug>

Rotates the project role password and JWT secret. Updates the project .env file and Hasura source connection string.

nself project rotate-credentials --slug <slug>

B46 uses tenant_id UUID for Cloud SaaS isolation, NOT source_account_id. These are distinct mechanisms. See the Multi-Tenant Convention Wall.

• nself controller, Daemon management
• Multi-Tenant Hosting Guide
• Agency Setup Guide