Control Center
The browser console, built into the propus binary: open the server's address.
Signing in
The owner account is created once, from the setup link that propus init, propus setup-link or the installer prints. There is one account per server; a forgotten password is reset with a link from propus recovery-link --email <email> on the server.
Pages
Server
| Page | Shows |
|---|---|
| Databases | Every database; New database, drop |
| Engines | Every engine checked live every 5 s: a read of each database file, SELECT 1 on each database, the Postgres, Redis and Kafka listeners connected to, caches, streams, buckets, search lag, migrations, replicas and backups; each marked Running, Idle, Needs a look, Failing or Off |
| Performance | Latency percentiles, slow queries with their plans |
| Account (Settings) | Name, email, password |
Per database
| Page | Shows | |
|---|---|---|
| Overview | Each engine's numbers, the database's URLs for every protocol | |
| Tables | Rows (edit, add, delete), structure, policies and grants, an access check that runs as any role and tenant | |
| SQL | An editor with results, plans, and Run as | |
| Search | Indexes, lag, rebuild, a search box | |
| Cache | Key browser, values by type, expiry, a command box | |
| Streams | Messages, publishing, consumer groups and their lag | |
| Objects | Folders, drag-and-drop upload, previews, versions, public links | |
| Migrations | A guided start, live progress, cutover and rollback | |
| API keys | Role keys with tenant and user, revoke | |
| Audit log | Who did what, with the SQL | |
| Data safety | Verify, backups, encryption status |
Day and night themes; works at phone width.
How it stays safe
The browser holds only an HTTP-only, same-site cookie. The server adds the session when it forwards the console's calls and refuses calls from other origins; the browser never sees a key. --no-console turns the console off.