DINA / Platform

White-label administration · Local development

Super Admin

Sign in using your platform account and authenticator. This is separate from clinic staff access.

Use an authenticator code or one unused recovery code.

Password recovery

Requires BOTH your current authenticator code and one unused offline recovery code. If both are lost, use the local maintenance CLI with an existing password.

Clinic domains

Register a unique domain, then publish its DNS TXT challenge. Verification does not enable HTTPS or routing automatically.

1. Register a domain

2. Verify DNS ownership

3. Request routing changes

The status becomes ACTIVE after HTTPS and clinic identity checks pass. Route removal must be applied before registration can be released.

Registered domains

Release a domain registration

Request route removal and have the operator apply it before releasing a domain.

Account security

All changes require the existing password and active authenticator. Recovery codes are shown only once; store them offline.

Change password

Replace recovery codes

Replace authenticator



Create clinic
















Encrypted clinic backups




Each clinic needs its own backup key initialized offline before the first archive. Never restore over an existing clinic database.








Recent backup requests


Local backup and isolated restore history


Offsite encrypted clinic backups
Only VERIFIED copies have passed download, SHA-256 and authenticated decryption checks. Keep the original clinic backup key and tenant encryption keys separately for recovery. Only bundles with POSTGRESQL and CMS scopes include website media. Older database-only archives do not.










SaaS subscription management (TEST)


Only platform subscription fees are billed here. Clinic customer payments use separate Connect accounts. Cancellation is at period end, never deletion of clinical records.









Platform audit activity


Clinic preparation


Clinic setup


This checklist uses saved operational records. Missing or old observations remain unconfirmed. It does not certify a production launch.


Loading setup records…




Production deployment
Actions are queued for a separate Kubernetes operator. READY requires observed services, verified HTTPS, owner MFA, billing and full backup/restore evidence.