ADBAROS CLOUD CONSOLE

Application operations centerSandbox workspace

Seven operational workspaces, distinct from user-data administration. All telemetry and commands are local simulations.

Operations control plane · local simulation

No real hosts, credentials, user records or external services are accessed. Production commands are disabled.

STAGING SIMULATION

Operational identitySimulation roleDemo roles only · not authenticated access

ADBAROS · APPLICATION OPERATIONS

Keep the platform running.

Infrastructure, releases, queues, transport and recovery — separate from managing user accounts and content.

No live connectionNo user-data mutationsStaging rehearsals only

CONTROL PLANEFuture server integration

APIWorkersStorageLive

Operational domains7Specialized control workspaces

Rehearsals recorded0Local events, not server receipts

Maintenance rehearsalOffDoes not affect application availability

Production controlDisabledAwaiting server and authorization layer

1 sample alerts

Compute & network

Servers & service fleet

Host telemetry, service dependencies, safe restart rehearsals, and capacity planning.

Open workspace

Planning workspace

Delivery & change control

Releases & maintenance

Staging release inventory, deployment gates, rollback rehearsal, and maintenance windows.

Open workspace

2 sample alerts

Processing pipeline

Media queues & workers

Video / image job queues, worker health, failed attempts, and retry rehearsals.

Open workspace

2 sample alerts

Realtime media infrastructure

LiveKit & call infrastructure

LiveKit/TURN planning, connection quality, recording pipelines, and recovery drills.

Open workspace

3 sample alerts

Delivery infrastructure

Email & push delivery

Transport health, delivery latency, quotas, failed jobs, and retry policies.

Open workspace

Planning workspace

Data resilience

Storage & recovery operations

Retention planning, upload compatibility, object inventory, and backup restore rehearsals.

Open workspace

2 sample alerts

Reliability & access boundaries

Incidents, traces & operator access

Operational alerts, correlated service traces, incident runbooks, and distinct operator roles.

Open workspace

Operational dependency map

Architecture plan · every node is unconnected

PLANNED TOPOLOGY

Edge / API gatewayTLS · rate limits · routing

Dridoud applicationAPI · auth · realtime

PostgreSQL / backupMedia / delivery workersObject storage / CDNLiveKit / TURN

Administration and operations are separate

DATA ADMINISTRATION

Users, posts, verification, support

Leave real content decisions and account mutations in the existing Dridoud admin panel. Its source and backend stay untouched.

APPLICATION OPERATIONS

Hosts, releases, workers, delivery, recovery

Reuse existing read-only metrics through future adapters. Grant operator privileges independently from moderation privileges.

Separate operational role model

Simulation only. Actual roles must be enforced by the server with MFA and scoped service authorization.

Permission	Owner	Operator	Observer
Read operational metrics	Read	Read	Read
Restart service / retry job	Simulate	Simulate	—
Staging deployment / maintenance	Simulate	Simulate	—
Rollback / isolated restore	Simulate	—	—
User-account / content moderation	Separate admin panel	Separate admin panel	Separate admin panel
Production control	Disabled	Disabled	Disabled

Local command receipts

Editable browser storage · not a tamper-proof operational audit log

0 LOCAL EVENTS

No operational simulations recorded yet.