CEDX 2026 Kernel Release: Single-tenant isolation, canonical Postgres schema, workflow bus, and immutable audit trail Explore the CEDX Workflow architecture ->
CEDXSystems
EnglishTalk to sales
PLATFORM & IDENTITY CEDX Workflow
Pulse Workflows Triggers Workflow & Tour Operators TCO Model 14-Day Sandbox Live build ↗
PLATFORM & IDENTITY CEDX Workflow · Platform · workflow.cedxsystems.com

Automation that keeps its own ledger.

Thirty-six workflows and 243,896 runs in the demo estate, with the parts automation tools usually hide priced on screen: retries at $165 a month, a 94.7% success rate held against a 99% SLA target, and 8 approvals waiting on a human, by design.

Open live CEDX Workflow -> Inspect 4-screen build tour
36 workflow definitions 243,896 runs in the catalog 72 agent runs in view Zero-ETL Shared Postgres Record
CEDX Workflow Enterprise Architecture Briefing
CEDX Workflow · 36 workflow definitions

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation fro..."

Marcus Vance · Chief Revenue Officer · Meridian Systems · 0.01s Canonical Sync
CEDX Workflow reads and writes the exact same canonical Postgres record as CEDX Events, CEDX Notify, and CEDX Entitlements with zero third-party webhooks.
🔒 https://workflow.cedxsystems.com/workspace/live
CEDX Workflow · Pulse (Reliability as attainment, not uptime theatre)
workflow.cedxsystems.com · 01 Pulse · Live Canonical Dataset
● Pulse Active · 0.011s Sync Open /app/workflow ↗
WORKFLOW DEFINITIONS
36
17 live · 10 draft · 9 paused
RUNS IN THE CATALOG
243,896
94.7% average success
AGENT RUNS IN VIEW
72
tool-call executions
APPROVALS PENDING
8
human-in-the-loop, by design
Platform Subsystem / Node Canonical Schema Binding Tenant & RBAC Scope Throughput / Event Rate Cryptographic Audit SLA Availability
Canonical Entity Graph v26.4CEDX Workflow · Record #1040 132 Apps · Shared Primary Keys Global Multi-Entity Root 48.2M Events / Day ● SHA-256 Chain Verified 99.995% Uptime
Workflow Deterministic BusCEDX Workflow · Record #1041 Cross-App Triggers (CRM->Books) Zero-Middleware Execution 1,840 Workflows / Min ● Idempotent Replay Log 0.012s p99
Enterprise Directory & RBACCEDX Workflow · Record #1042 418 Principals · 38 Roles SCIM + SAML + Passkeys Zero Standing Drift ● Every Grant Priced 100% Enforced
Immutable Compliance LedgerCEDX Workflow · Record #1043 SOC-2 / ISO / GDPR Evidence Tamper-Evident Storage 100% Write Coverage ● Auditor Read-Only View Verified Live
✦ CEDX Workflow Copilot · Canonical Entity Graph v26.4
Pulse Verified
Reliability attainment reads 96% of target, and the alerts carry causes: a schema mismatch fanning out to 8 workflows that share a connector class; retry cost concentrated in one dunning path; a 99% success streak on nightly inventory reconcile held up as the good example.
CEDX Workflow operator workspace in natural daylight
FIELD DOCUMENTARY · PLATFORM & IDENTITY

Workflows with their track record attached

The most honest card on the Pulse is the smallest: approvals pending, 8, human-in-the-loop. The automation stops where a person should decide, and says so.

CAMERA: CANON EOS R5 · 35MM F/1.4 · NATURAL DAYLIGHT ESTATE ROUTE: /APP/WORKFLOW
CORE CAPABILITIES · CEDX WORKFLOW

Three architectural jobs CEDX Workflow gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · PLATFORM & IDENTITY FOUNDATION

Workflows with their track record attached

The definitions table carries runs, ok %, p95 and open failures on every row: the order-to-invoice flow has 48,200 runs at 98.4% with a 1.2s p95, next to a paused dunning pack at 88.7% and 10 seconds. Drafting starts from a sentence. The describe-an-automation bar is on the screen.

✓ 17 live, 10 draft, 9 paused; status is a chipVerified
✓ Trigger type, steps and owner per rowVerified
✓ Describe an automation in words, draft it in placeVerified
02 · LIVE EXECUTION

Triggers with lag measured

Thirty-two triggers across webhook, schedule, event, queue, record and manual, each with fires per day and lag in seconds. The order-paid webhook fires 1,240 times a day at 0.4 seconds; eighteen triggers sit over the three-second lag line, which is a count, not a vibe.

Triggers with lag measured
CEDX Workflow Live Telemetry ● 36 workflow definitions
03 · DETERMINISTIC GOVERNANCE

Every run priced and explained

The run ledger shows cost, duration, steps and retries per row. A nightly reconcile takes 46 seconds and 26 cents, with failures named: network reset, connector down, timeout. Agent runs are a kind of their own: 72 tool-call executions in view.

✓ 240 of 328 ledger rows completed okActive
✓ Costs from $0.09 to $0.64 per run in viewActive
✓ Success · Failed · Timed out · Cancelled as statusesActive
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Workflow build looks like when you open /app/workflow.

Every figure below is directly inspectable in the running CEDX Workflow application workspace with zero synthetic projections.

WORKFLOW DEFINITIONS
36
17 live · 10 draft · 9 paused
RUNS IN THE CATALOG
243,896
94.7% average success
AGENT RUNS IN VIEW
72
tool-call executions
APPROVALS PENDING
8
human-in-the-loop, by design
4-SCREEN RUNNING BUILD TOUR

Four screens captured from workflow.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX Workflow moves from initial intake to verified cross-estate completion.

01 PULSE
Reliability as attainment, not uptime theatre
Reliability attainment reads 96% of target, and the alerts carry causes: a schema mismatch fanning out to 8 workflows that share a connector class; retry cost concentrated in one dunning path; a 99% success streak on nightly inventory reconcile held up as the good example.
02 WORKFLOWS
The catalog, with drafts included
Thirty-six definitions with status, trigger, steps, runs, ok %, p95, open failures and owner. The paused rows are as legible as the live ones: a queue-triggered dunning pack at 88.7% is paused with its record attached, not quietly deleted.
03 TRIGGERS
Where work actually starts
Every trigger lists what it starts, how often it fires and how late it runs. A schedule trigger at 7.5 seconds lag and a webhook at 0.4 are different operational facts, and the table treats them that way.
04 RUNS
The ledger, row by row
Run ids with workflow, status, kind, cost, duration, steps, retry count and error. The 8 approvals pending are a chip on this screen. A person is the step the automation is waiting on, and the wait is visible.
01 PULSE · WORKFLOW.CEDXSYSTEMS.COM

Reliability as attainment, not uptime theatre

● Live Screen Capture

Reliability attainment reads 96% of target, and the alerts carry causes: a schema mismatch fanning out to 8 workflows that share a connector class; retry cost concentrated in one dunning path; a 99% success streak on nightly inventory reconcile held up as the good example.

✓ Open failures counted at 76 across the catalogVerified in /app/workflow
✓ Blast radius scored 99 on the worst failuresVerified in /app/workflow
✓ SLA freeze: no publish on the critical band without dual reviewVerified in /app/workflow
Reliability as attainment, not uptime theatre
OPERATING CADENCE · PLATFORM & IDENTITY

How CEDX Workflow runs across the week, in the exact order work happens.

Platform governance is not bolted on after purchase: Admin, Directory, Workflow, Audit, and Vault form the substrate every CEDX app compiles against.

STAGE 01

Capture & Ingest

Records land in CEDX Workflow already linked to the canonical customer, employee, or vendor ID.

STAGE 02

Score & Triage

Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.

STAGE 03

Execute & Approve

Operators resolve work in one click with role-based guardrails and instant cross-app writeback.

STAGE 04

Reconcile & Report

Every completed action updates live executive dashboards and the immutable audit log automatically.

OPERATOR WORKSPACES · WHO RUNS CEDX WORKFLOW

Three roles open CEDX Workflow every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

Operations using CEDX Workflow

Operations

Owns the approval queue: 8 pending human decisions between a run and its side effects, worked from the same screen the automation waits on.

● approvals · 8
Platform engineering using CEDX Workflow

Platform engineering

Owns the trigger estate and the failure ledger: 18 triggers over the lag line and 76 open failures are theirs to work down.

● open failures · 76
Finance operations using CEDX Workflow

Finance operations

Owns the retry cost base: $165 over 30 days, argued per path. The dunning path alone is the line item the alert names.

● retry cost · $165
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

One Identity, One Data Model, One Permission Graph Under Every Application

CEDX Workflow is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /events/ ->

CEDX Events

Event triggers are one of the six trigger types on the Triggers table. The streams Events runs are what they fire on.
CONNECTED MODULE 02 Open /notify/ ->

CEDX Notify

Dunning paths and alert relays end as deliveries. The campaigns and templates Notify tracks are workflow outputs here.
CONNECTED MODULE 03 Open /entitlements/ ->

CEDX Entitlements

Gated rollouts and dual-review freezes are flags in Entitlements; the workflows respect the same gates.
CONNECTED MODULE 04 Open /functions/ ->

CEDX Functions

Custom steps run as functions: the unit a workflow step becomes when the built-in actions are not enough.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Workflow.

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."

Marcus Vance
Marcus Vance
Chief Revenue Officer · Meridian Systems

"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."

Elena Rostova
Elena Rostova
Chief Financial Officer · Northline Group

"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."

David Okafor
David Okafor
VP of Enterprise Systems · Harbor Holdings
LIVE TCO & CONSOLIDATION MODEL · PLATFORM & IDENTITY

Stop paying five vendors to re-sync the same platform & identity record.

Drag the seat slider to compare your current stitched stack (Okta Workforce + Workato + MuleSoft + Vanta + Splunk Audit) against running CEDX Workflow natively on the unified CEDX estate.

Organization Seats 250 seats
25 seats 500 seats 1,250 seats 2,500 seats
Legacy Stitched Stack
Okta Workforce + Workato + MuleSoft + Vanta + Splunk Audit
$1,380,000 / yr
CEDX Workflow + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr
Verified Annual Hard Savings
Plus 0 middleware sync failures
$1,113,000 / yr
TECHNICAL & PROCUREMENT FAQ · CEDX WORKFLOW

Questions operators and architecture teams ask before piloting CEDX Workflow.

01 Is the software on this page real? +
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/workflow . It runs on demo data, which the page says next to the figures rather than in a footnote.
02 What does human-in-the-loop mean here? +
A workflow can declare an approval step, and the run waits there: 8 approvals are pending in the demo ledger, visible as a chip on the Runs screen. The automation does not improvise past a decision that belongs to a person.
03 How are failures handled? +
Three ways, all visible: retries with a priced cost base ($165 over 30 days in the demo), error names on the failed rows (network reset, connector down, timeout), and blast radius scoring on the failures that fan out. The worst score 99 and share a connector class.
04 What can start a workflow? +
Six trigger types, each on the Triggers table: webhook, schedule, event, queue, record and manual. Fires per day and lag in seconds are measured per trigger. The busiest fires 1,240 times a day at 0.4 seconds.
05 Can we draft automations without code? +
The Workflows screen opens with a describe-an-automation bar and a Draft workflow button. The placeholder itself gives the example: an overdue-invoice chase that waits for approval. What it generates still lands in the same ledger as everything else.
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

CEDX Workflow is running right now. Open it and inspect the record.

Explore the live CEDX Workflow workspace on canonical demo data at /app/workflow, or book a 30-minute architecture session to map your first entity rollout.

Open live CEDX Workflow (/app/workflow) -> Book an estate architecture map