Playbook: spin up a client service

The per-client instance pattern for platforms like Listmonk.

The pattern for giving a client their own instance of a platform (Listmonk today; others follow the same shape).

1. Choose the substrate. Openship box for new spin-ups once live; Railway otherwise.
2. Provision: container + database + persistent volume as the platform requires. Name it <client>-<service>.
3. Domain: <service>.<clientdomain> or <client>-<service>.backpackops.com when the client domain is not cut over. We control DNS, so records are automatable.
4. SSO/credentials: admin credentials go straight into the secrets manager, never chat or docs.
5. Register the instance in the services registry (client, service, URL, substrate) so the console modules can surface it.
6. Verify the instance serves over HTTPS and log in works, then hand off with the live link.

Keep instances boring and upstream-standard. Custom behavior belongs in configuration or in our fork repos (iese), never in snowflake in-place edits.