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

The people record, kept honest.

Every identity in the demo directory (340 of them) carries a source system, a status, a kind and an owner. The ones that do not are not a discovery project: they are a scored queue of 160 orphan rows.

Open live CEDX Directory -> Inspect 4-screen build tour
340 identities in the directory 48 identities with no source system 160 groups in the tenant Zero-ETL Shared Postgres Record
CEDX Directory Enterprise Architecture Briefing
CEDX Directory · 340 identities in the directory

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

Elena Rostova · Chief Financial Officer · Northline Group · 0.01s Canonical Sync
CEDX Directory reads and writes the exact same canonical Postgres record as CEDX Identity, CEDX Admin, and CEDX People with zero third-party webhooks.
🔒 https://directory.cedxsystems.com/workspace/live
CEDX Directory · Overview (Hygiene as a score with a queue behind it)
directory.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/directory ↗
IDENTITIES IN THE DIRECTORY
340
230 active
IDENTITIES WITH NO SOURCE SYSTEM
48
orphan signal
GROUPS IN THE TENANT
160
16 empty · 34 ownerless
HYGIENE SCORE
84
components printed beside it
Platform Subsystem / Node Canonical Schema Binding Tenant & RBAC Scope Throughput / Event Rate Cryptographic Audit SLA Availability
Canonical Entity Graph v26.4CEDX Directory · 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 Directory · Record #1041 Cross-App Triggers (CRM->Books) Zero-Middleware Execution 1,840 Workflows / Min ● Idempotent Replay Log 0.012s p99
Enterprise Directory & RBACCEDX Directory · Record #1042 418 Principals · 38 Roles SCIM + SAML + Passkeys Zero Standing Drift ● Every Grant Priced 100% Enforced
Immutable Compliance LedgerCEDX Directory · Record #1043 SOC-2 / ISO / GDPR Evidence Tamper-Evident Storage 100% Write Coverage ● Auditor Read-Only View Verified Live
✦ CEDX Directory Copilot · Canonical Entity Graph v26.4
Overview Verified
Hygiene health reads 84, with the components beside it: owner coverage 79%, 230 active users, 16 high-orphan accounts, 8 high-sprawl groups. The alerts are root-caused: 26 near-duplicate group pairs, 31 leavers past SLA, one service account active with no manager and no source.
CEDX Directory operator workspace in natural daylight
FIELD DOCUMENTARY · PLATFORM & IDENTITY

Every identity knows where it came from

The alert that matters is one line: 48 identities have source = None. Nothing federates, nothing syncs, and the directory says so on its own front page.

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

Three architectural jobs CEDX Directory 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

Every identity knows where it came from

The Users table carries source on every row (HRIS, LDAP, Cloud IdP or Manual) next to kind, status, group count and a profile-completeness bar. The header does the arithmetic for you: 340 identities, 230 active, and 48 with no source at all.

✓ HRIS · LDAP · Cloud IdP · Manual as source valuesVerified
✓ Workforce and Contractor separated as kindsVerified
✓ Profile completeness as a percentage on every rowVerified
02 · LIVE EXECUTION

Orphan risk is a score, not a hunch

Hygiene scores all 160 orphan rows and puts the worst on top: ghost-hire-09 at 86, three service accounts at 70 to 80, each with its top signal printed (no authoritative source system). Filter chips at 30, 45 and 70 turn the list into a work queue.

Orphan risk is a score, not a hunch
CEDX Directory Live Telemetry ● 340 identities in the directory
03 · DETERMINISTIC GOVERNANCE

Groups with sprawl measured

160 groups, and the table shows why some are a problem: all-employees with 280 members, tmp-old-81 with 106 and a nested flag, 16 sitting empty. Sprawl has a number (the worst group on the Overview scores 76) and 34 groups have no owner at all.

✓ Type, members, owner, nested, empty and review on a rowActive
✓ Department · Application · Dynamic · Distribution chipsActive
✓ 16 empty groups called out as archive candidatesActive
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Directory build looks like when you open /app/directory.

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

IDENTITIES IN THE DIRECTORY
340
230 active
IDENTITIES WITH NO SOURCE SYSTEM
48
orphan signal
GROUPS IN THE TENANT
160
16 empty · 34 ownerless
HYGIENE SCORE
84
components printed beside it
4-SCREEN RUNNING BUILD TOUR

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

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

01 OVERVIEW
Hygiene as a score with a queue behind it
Hygiene health reads 84, with the components beside it: owner coverage 79%, 230 active users, 16 high-orphan accounts, 8 high-sprawl groups. The alerts are root-caused: 26 near-duplicate group pairs, 31 leavers past SLA, one service account active with no manager and no source.
02 USERS
The roster, with provenance
340 rows where the columns do the governance work: source system, kind, status, group count, profile percentage, last login. A suspended engineer sourced from Manual next to an active exec from HRIS is the whole story of the directory in two rows.
03 HYGIENE
Orphans and sprawl, scored
The orphan tab ranks accounts by score and prints the signal that produced it: no authoritative source system on the top rows. Group sprawl, the cleanup simulator and the scoring model are one tab over, so the rule is inspectable, not magic.
04 GROUPS
Where sprawl actually lives
all-employees at 280 members is expected; tmp-old-81 at 106 with a nested flag is not, and the table lets you see both at once. Empty groups are counted (16) and ownerless groups are counted (34), because those are the two ways a group becomes a problem.
01 OVERVIEW · DIRECTORY.CEDXSYSTEMS.COM

Hygiene as a score with a queue behind it

● Live Screen Capture

Hygiene health reads 84, with the components beside it: owner coverage 79%, 230 active users, 16 high-orphan accounts, 8 high-sprawl groups. The alerts are root-caused: 26 near-duplicate group pairs, 31 leavers past SLA, one service account active with no manager and no source.

✓ Source mix: 150 HRIS, 39 LDAP, 41 Cloud IdP, 62 manual, 48 noneVerified in /app/directory
✓ Headcount versus churn events, dailyVerified in /app/directory
✓ 176 lifecycle rows open in the joiner-mover-leaver queueVerified in /app/directory
Hygiene as a score with a queue behind it
OPERATING CADENCE · PLATFORM & IDENTITY

How CEDX Directory 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 Directory 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 DIRECTORY

Three roles open CEDX Directory 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.

People operations using CEDX Directory

People operations

Owns the joiner-mover-leaver queue. The 176 open lifecycle rows and the 31 leavers past SLA are their Monday list, not a quarterly project.

● lifecycle open · 176
IT administration using CEDX Directory

IT administration

Owns the source mix. Every identity on Manual or None is theirs to reconcile: 110 rows in the demo directory between the two.

● no source · 48
Governance using CEDX Directory

Governance

Owns the review dates on the group table and the owner coverage number: 78.8% is the figure they report, and the 34 ownerless groups are the gap.

● owner coverage · 78.8%
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

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

CEDX Directory 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 /identity/ ->

CEDX Identity

The 340 identities Directory keeps clean are the principals Identity puts behind MFA and policy: same rows, different job.
CONNECTED MODULE 02 Open /admin/ ->

CEDX Admin

Directory knows who exists; Admin knows what their seat costs. Idle accounts in one become reclaimed spend in the other.
CONNECTED MODULE 03 Open /people/ ->

CEDX People

The HRIS feed that sources 150 demo identities is the record People maintains: hire there, staged here.
CONNECTED MODULE 04 Open /audit/ ->

CEDX Audit

Lifecycle events (176 open rows, 31 past SLA) are exactly the event classes Audit retains and scores.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Directory.

"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

"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."

Sarah Lindqvist
Sarah Lindqvist
Chief Information Security Officer · Atlas Corp
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 Directory 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 Directory + 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 DIRECTORY

Questions operators and architecture teams ask before piloting CEDX Directory.

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/directory . It runs on demo data, which the page says next to the figures rather than in a footnote.
02 What is an orphan account, exactly? +
An identity nothing authoritative claims. The Hygiene screen scores them (160 rows in the demo directory) and prints the top signal on each row; the highest-scored ones simply read no authoritative source system, with a score like 86 attached.
03 How does the directory stay current? +
Through the source mix on the Overview: 150 identities arrive from HRIS, 41 from a cloud identity provider, 39 from LDAP, 62 are manual. The lifecycle queue holds 176 open joiner-mover-leaver rows, and leavers past SLA are an alert: 31 of them in the demo data.
04 What counts as sprawl? +
A group whose membership score crosses the threshold: 55 in the demo configuration. Eight groups are past it, led by review and temporary groups at 76, and the 16 empty groups are counted separately as archive candidates.
05 Can we keep our existing HR system as the source? +
That is the design: HRIS is the authoritative feed for most of the demo directory. Which systems bind in your estate is what the estate map conversation works through.
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

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

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

Open live CEDX Directory (/app/directory) -> Book an estate architecture map