ZentraOps
One place to see, decide, and act.
ZentraOps is the command layer for operations. It shows what needs attention, why, what context matters, what should happen, and whether it worked.
01Product model
Every screen follows one model.
- 01Business systems
- 02Events
- 03Signals
- 04Context
- 05Decision
- 06Workflow
- 07Action
- 08Outcome
- 09Analytics
02Command Center
Current state, attention, cause, action, outcome.
The Command Center is built around what an operator needs first: what needs attention now. Select a marker on the timeline or an item in the attention rail.
Current state
6 signals need action. 3 are at SLA risk. 11 workflows are running.
- Active signals
- 24
- Requires action
- 6
- SLA risks
- 3
- Running
- 11
- Resolved today
- 187
Operational timeline
- signal
- at risk
- workflow running
- verified
Inspect · sig_0412
Payment reconciliation mismatch
Payment reconciliation mismatch
payments-gw · 12:20
17 related records in batch B-2291; similar incidents rising
Run investigation workflow.
Requires action
Resolution flow · today
Workflow status
- run_88213InvestigationRunning
- run_88291Reassign and notifyRunning
- run_88304Approval routingWaiting
03Signals
A stream of what matters, with the context beside it.
- Signal stream with filters and priority
- Selected signal with related records
- Recommended action and workflow state
Signal stream
Selected signal
Payment reconciliation mismatch
- type
- reconciliation.mismatch
- source
- payments-gw
- delta
- amount differs between ledger and gateway
- evt
- evt_7Q2K9
Context and action
- related
- 17 records in batch B-2291
- history
- similar incidents increased over 24h
- owner
- Finance Ops
Recommended: Start investigation workflow
Inspect in the signal canvas04Operations
Cases with owners, SLAs and a next action.
- Active, at-risk, waiting, escalated and resolved views
- Owner, priority, SLA and next action on every case
- Bulk assignment and saved views
| Case | Signal | Owner | Priority | SLA | Next action |
|---|---|---|---|---|---|
| CASE-2081 | Ticket nearing SLA breach | Support lead | High | 42m | Reassign |
| CASE-2079 | Order stuck in fulfilment | Fulfilment | Medium | 5h | Await update |
| CASE-2077 | Reconciliation mismatch | Finance Ops | High | 3h 58m | Review context |
Sample cases
05Workflows
Decisions become repeatable execution.
- Trigger, context, decision, action and verification
- Runs, failed runs and templates
- Versioned, with a full run history
06AI Context
Interpretation that shows its evidence.
- What was observed, why it matters, supporting context, suggested action
- Links to the records behind each claim
- Acts only within policy
Settlement mismatch in batch B-2291.
Settlement SLA closes in under 4 hours. Unresolved variance blocks close.
17 related records. Similar incidents increased over 24h. 14 of 17 share a gateway route.
Start the investigation workflow in review mode and assign to Finance Ops.
07Policies
Automation, inside your rules.
- Auto, review or block modes
- Approval gates with named approvers
- Every decision written to Activity
Sample policies
08Analytics
Answers to operational questions.
- Where are cases waiting longest?
- Which exceptions keep recurring?
- How much did automation resolve?
Which exceptions keep recurring?
Sample counts · last 30 days
09Underneath
Eight layers, one loop.
Integrations and the API sit at the bottom. Analytics at the top. Explore the architecture.
10API
Send an event. Get a signal.
curl -X POST https://YOUR_ZENTRA_HOST/api/v1/events \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: evt-2026-03-04-0001" \
-d '{"type":"reconciliation.mismatch","source":"payments-gw","occurred_at":"2026-03-04T08:32:11Z","entity":{"kind":"settlement_batch","id":"B-2291"},"data":{"ledger_total":118450,"gateway_total":118195,"currency":"INR"}}'- Receiving event…
- Enriching context…
- Evaluating policy…
- Preparing workflow…
// Response appears here after you send the example event.
Sample data is used throughout this site.