Capture & Ingest
Records land in CEDX Scripts already linked to the canonical customer, employee, or vendor ID.
Scripts runs the estate's scheduled automation: cron, interval and event triggers, agent-initiated runs that queue for human approval before touching production secrets, and every run priced in minutes and cents.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."
| Endpoint / Function / App | Bound Estate Resource | Owner & Deployment Env | Request Rate & Latency | Blast Radius & Quota | Build Status |
|---|---|---|---|---|---|
| POST /v2/quotes/approve-rampCEDX Scripts · Record #1040 | Quotes + Books + Sign Transaction | Core Commerce SDK · Prod | 1,420 req/m · 14ms p99 | ● Scoped Token · Tier-1 | Passing 100% |
| fn_custom_rebate_accrual.tsCEDX Scripts · Record #1041 | Serverless Edge Function · Node 22 | Finance Eng · Sandbox->Prod | 840 exec/m · 9ms cold | ● Read/Write: Books Subledger | Deterministic |
| Internal Field RMA Builder AppCEDX Scripts · Record #1042 | CEDX Builder Low-Code Surface | Ops Systems Team · 68 Users | Zero Maintenance Debt | ● Inherits Corporate SSO | Live v2.4 |
| CI/CD Canary Pipeline #8841CEDX Scripts · Record #1043 | Automated Flake-Scored Test Suite | Release Engineering | 412 Specs · 0 Flakes | ● Auto-Rollback Armed | Deployed 4m ago |
The run table shows its arithmetic: compact-audit succeeded in 2.4 minutes for $0.10; allocate-stock failed in 20.2 seconds for $0.03. Automation you cannot price is automation you cannot govern.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
23 runs sit in the awaiting-approval queue: agent-triggered work that touches production secrets. ledger-post, ar-dunning and fx-rate-pull each hold an Approve and a Reject button, with the initiating agent named. Automation proposes; a person disposes.
320 runs with status, duration, cost, trigger and actor. run_0eadcb13 (compact-audit, agent-triggered, approved) succeeded in 2.4 minutes at $0.10. notify-digest failed in 2.8 minutes at $0.20. Success and failure both get a bill.
The Logs view covers 47 distinct scripts across 240 lines, and the overview's secret board names the exposure: sec_billing_settle_db at 312 days, sec_legacy_v1_token at 401, both at risk 95. Thirteen credentials sit past rotation SLA, as an alert, not an audit finding.
Every figure below is directly inspectable in the running CEDX Scripts application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Scripts moves from initial intake to verified cross-estate completion.
320 runs at 62.8% success against a ≥95% target. The ring shows 63%, not a rounded-up fiction. Alerts arrive root-caused: a retry storm on partner-orbit-sync at 11.4% fail with the retry budget often exhausted, and a ledger-post timeout cascade under event fan-out.
Every custom app in Builder, every Function, and every webhook runs inside the same identity, audit log, and transactional boundary as native CEDX apps.
Records land in CEDX Scripts already linked to the canonical customer, employee, or vendor ID.
Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.
Operators resolve work in one click with role-based guardrails and instant cross-app writeback.
Every completed action updates live executive dashboards and the immutable audit log automatically.
Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.
Owns the schedules and the scripts behind them, and reads the retry storm on partner-orbit-sync as a design problem, not bad luck.
Works the failed and timeout rows: 40 failed, 28 timed out in the sample, each with a log line and a retry button rather than a shrug.
The human in the loop for the 23 queued agent runs: approve or reject, with the secret scope and the initiating assistant on the card.
CEDX Scripts 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.
Event-driven schedules subscribe to estate events: order.settled and invoice.paid are the streams Scripts listens to.
Script runs execute on the same metered runtime: duration billed, cold starts costed, failures logged.
A script ships through the same environments and risk gates as any other deploy before its schedule goes live.
The agent runs writing into records land here. Fill bars and agent-run states are Tables' side of the same work.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."
"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
Drag the seat slider to compare your current stitched stack (Retool Enterprise + Kong API Gateway + AWS Lambda + Postman + LaunchDarkly) against running CEDX Scripts natively on the unified CEDX estate.
Explore the live CEDX Scripts workspace on canonical demo data at /app/scripts, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Scripts pre-loaded with canonical demo records and connected across the 132-application CEDX estate.