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

PageShows
DatabasesEvery database; New database, drop
EnginesEvery 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
PerformanceLatency percentiles, slow queries with their plans
Account (Settings)Name, email, password

Per database

PageShows
OverviewEach engine's numbers, the database's URLs for every protocol
TablesRows (edit, add, delete), structure, policies and grants, an access check that runs as any role and tenant
SQLAn editor with results, plans, and Run as
SearchIndexes, lag, rebuild, a search box
CacheKey browser, values by type, expiry, a command box
StreamsMessages, publishing, consumer groups and their lag
ObjectsFolders, drag-and-drop upload, previews, versions, public links
MigrationsA guided start, live progress, cutover and rollback
API keysRole keys with tenant and user, revoke
Audit logWho did what, with the SQL
Data safetyVerify, 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.