CEDX 2026 Kernel Release: Single-tenant isolation, canonical Postgres schema, workflow bus, and immutable audit trail Explore the CEDX Files architecture ->
CEDXSystems
PLATFORM & IDENTITY CEDX Files · Platform · files.cedxsystems.com

The file estate, with its exposure showing.

Three hundred twenty files and 120 share links in the demo workspace, and the console counts what file tools usually leave for the incident review: 46 links open to anyone, 99 files untouched in 90 days, and classification labels on only 63% of the library.

320 files in the library 46 anyone-links open 99 files idle 90 days or more Zero-ETL Shared Postgres Record
CEDX Files Enterprise Architecture Briefing
CEDX Files · 320 files in the library

"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 Files reads and writes the exact same canonical Postgres record as CEDX Search, CEDX Knowledge, and CEDX Drive with zero third-party webhooks.
🔒 https://files.cedxsystems.com/workspace/live
CEDX Files · Overview (Workspace health at 25%, and why)
files.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/files ↗
FILES IN THE LIBRARY
320
48 folders · 18 GB
ANYONE-LINKS OPEN
46
public, no sign-in
FILES IDLE 90 DAYS OR MORE
99
stale, counted
FILES AI-PROCESSED
79
summary and Q&A ready
Platform Subsystem / Node Canonical Schema Binding Tenant & RBAC Scope Throughput / Event Rate Cryptographic Audit SLA Availability
Canonical Entity Graph v26.4CEDX Files · 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 Files · Record #1041 Cross-App Triggers (CRM->Books) Zero-Middleware Execution 1,840 Workflows / Min ● Idempotent Replay Log 0.012s p99
Enterprise Directory & RBACCEDX Files · Record #1042 418 Principals · 38 Roles SCIM + SAML + Passkeys Zero Standing Drift ● Every Grant Priced 100% Enforced
Immutable Compliance LedgerCEDX Files · Record #1043 SOC-2 / ISO / GDPR Evidence Tamper-Evident Storage 100% Write Coverage ● Auditor Read-Only View Verified Live
✦ CEDX Files Copilot · Canonical Entity Graph v26.4
Overview Verified
The health ring is blunt: 25%, driven by 46 open anyone-links, 99 stale files and 63% label coverage. The alerts are root-caused: the Confidential archive on a public link is named with its file, its class and its share type.
CEDX Files operator workspace in natural daylight
FIELD DOCUMENTARY · PLATFORM & IDENTITY

The library, with risk per row

The finding that writes the page: a Confidential archive reachable through an anyone-link, no sign-in required. The console found it; nothing else was going to.

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

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

The library, with risk per row

All files as one table: type, folder, share class, opens, size, idle days and owner on every row. The AI column is honest about its scope: 79 files processed, summary and Q&A ready, marked with a chip. The stale and external counts are header cards, not filters you have to build.

✓ 320 rows, 22K opens counted across the libraryVerified
✓ Share class per row: Private, Internal, Org, External, AnyoneVerified
✓ Idle days on every row: 99 files at 90 or moreVerified
02 · LIVE EXECUTION

Folders as policy boundaries

Forty-eight team spaces with members, files, size, external-link count, policy and classification per row. The folders that matter sort themselves: a Confidential archive with 19 external links under an External OK policy is visible in the same glance as a Restricted folder with 10.

Folders as policy boundaries
CEDX Files Live Telemetry ● 320 files in the library
03 · DETERMINISTIC GOVERNANCE

Shares that expire, or say never

The links table shows type, opens, recipients, expiry and status per link: Anyone, Org or Named. The never in orange is the governance: most of the active links have no expiry at all, and the expired-and-revoked tab keeps the other 15 of the 120 on record.

✓ 105 active links of 120 all-timeActive
✓ Expiry dates in black, never in orangeActive
✓ Opens and recipients counted per linkActive
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Files build looks like when you open /app/files.

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

FILES IN THE LIBRARY
320
48 folders · 18 GB
ANYONE-LINKS OPEN
46
public, no sign-in
FILES IDLE 90 DAYS OR MORE
99
stale, counted
FILES AI-PROCESSED
79
summary and Q&A ready
4-SCREEN RUNNING BUILD TOUR

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

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

01 OVERVIEW
Workspace health at 25%, and why
The health ring is blunt: 25%, driven by 46 open anyone-links, 99 stale files and 63% label coverage. The alerts are root-caused: the Confidential archive on a public link is named with its file, its class and its share type.
02 ALL FILES
The library as a working table
Three hundred twenty rows where opens, idle days and share class sit next to the filename. Sorting by opens puts a 420-open brief beside a 251-open zip on an anyone-link: popularity and exposure in one view.
03 FOLDERS
Where the policy actually lives
Folder rows carry the controls: a Board folder with 49 files and 15 external links, an Events folder at 23.4 GB, each with policy and class attached. External OK is a deliberate state. You can see which folders chose it.
04 SHARES
The link estate, expiry by expiry
One hundred five active links with opens, recipients and expiry. An onboarding PDF opened 90 times through 120 recipients with no expiry is a different object from a named link expiring in September, and the table shows both.
01 OVERVIEW · FILES.CEDXSYSTEMS.COM

Workspace health at 25%, and why

● Live Screen Capture

The health ring is blunt: 25%, driven by 46 open anyone-links, 99 stale files and 63% label coverage. The alerts are root-caused: the Confidential archive on a public link is named with its file, its class and its share type.

✓ Share mix: 95 private, 59 internal, 78 org, 53 external, 35 anyoneVerified in /app/files
✓ Files by type: 46 presentations to 34 imagesVerified in /app/files
✓ AI units tracked: 18K of a 25K monthly planVerified in /app/files
Workspace health at 25%, and why
OPERATING CADENCE · PLATFORM & IDENTITY

How CEDX Files 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 Files 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 FILES

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

Records management using CEDX Files

Records management

Owns classification: 63% coverage today, and the 99 files idle 90 days or more that pollute search and storage alike.

● stale files · 99
Security review using CEDX Files

Security review

Owns the anyone-link queue, 46 open with one on a Confidential archive, and the never-expiring links the orange text keeps asking about.

● anyone-links · 46
IT administration using CEDX Files

IT administration

Owns the plan arithmetic: 18 GB of 500 GB used, 18K AI units of the 25K monthly plan, and the folders growing past 40 GB.

● storage · 18 GB
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

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

CEDX Files 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.

ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Files.

"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 Files 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 Files + 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 FILES

Questions operators and architecture teams ask before piloting CEDX Files.

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/files . It runs on demo data, which the page says next to the figures rather than in a footnote.
02 What is an anyone-link and why does it matter? +
A share link that opens without sign-in. The demo workspace has 46 of them active, and the Overview alert that matters is one such link on a Confidential archive, reachable by anyone holding the URL. The console counts and exposes them; what you then revoke is your call.
03 How does expiry work on share links? +
Every link carries an expiry date or the word never, rendered in orange. Most of the 105 active links in the demo have no expiry, which is exactly the governance gap the column exists to make visible. Expired and revoked links stay on record under their own tab.
04 What does AI-processed mean? +
Scoped on the screen: 79 files have been processed for summary and Q&A, marked with an AI chip on the row, metered against an 18K-of-25K monthly units card. Nothing broader is claimed.
05 What counts as a stale file? +
Ninety days without activity. The demo library has 99 of them, counted on the Overview header, because stale files pollute search results and storage budgets alike.
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

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

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

Open live CEDX Files (/app/files) -> Book an estate architecture map