Managed server guide

The managed server adds authenticated durable operation around the ReplicaDB replication core. It provides datasource profiles, jobs, schedules, run history, diagnostics, permissions, users, and audit events.

What the server owns

The server stores the operational intent and history that a standalone CLI invocation does not keep: datasource profiles, job definitions, permissions, schedules, attempts, audit events, and safe diagnostics. The API serves the browser frontend and control plane; workers execute durable runs in a distributed deployment. PostgreSQL and the encryption keyring are part of this managed state boundary.

Follow an operator workflow

1. Install and choose a server profile.
2. Sign in and manage your profile.
3. Create and verify datasources.
4. Create a job and run it manually.
5. Inspect its run and diagnostics.
6. Schedule recurring work only after the manual run is understood.
7. Apply resource permissions, manage users, and review audit events as administrative operations.

Use the dashboard to locate operational changes, but use the job and run views to investigate their causes. For deployment, monitoring, backup, and recovery procedures, continue to the Operations guide.

The frontend is a usability layer. Backend authorization remains authoritative for every resource and action. A visible control can still fail after a role, permission, binding, or resource changes; the page reports the safe error and preserves context where possible.