Capture & Ingest
Records land in CEDX Functions already linked to the canonical customer, employee, or vendor ID.
Functions is the estate's compute runtime: 80 functions across 6 regions, every invocation timed, every cold start costed in dollars, and an error budget that says how burned it is, not just that it is.
"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production dat..."
| Endpoint / Function / App | Bound Estate Resource | Owner & Deployment Env | Request Rate & Latency | Blast Radius & Quota | Build Status |
|---|---|---|---|---|---|
| POST /v2/quotes/approve-rampCEDX Functions · 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 Functions · 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 Functions · 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 Functions · Record #1043 | Automated Flake-Scored Test Suite | Release Engineering | 412 Specs · 0 Flakes | ● Auto-Rollback Armed | Deployed 4m ago |
The most expensive line on the cold-cost board reads fn-slot-book · $173.92. When a slow function costs real money, the bill should name it. This one does.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
The Invocations table is a 320-row sample with kind, status, milliseconds, init time and region on every row. fn-ledger-post sits at a 500 with a 13,707ms init. That is a cold-start failure you can point at, not a mystery. Chips cut the view to cold, warm, 5xx, slow or throttled.
us-west-2 carries 7.17M invocations a day at 6% cold; eu-central-1 runs colder at 8.6% with a 0.42 error rate; the global edge tier runs 0.5% cold at a 414ms p99. Each region's share of spend is on the same row, so placement is an economic decision, not a habit.
280 lines sampled with level, function and message: fn-cart-merge fails with “OOM heap limit exceeded”, fn-tax-calc with “Throttled concurrency cap”, and fn-catalog-search logs “Unhandled error” three rows running. Timeout and OOM get their own filter chips because they deserve them.
Every figure below is directly inspectable in the running CEDX Functions application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Functions moves from initial intake to verified cross-estate completion.
Invocations at 24.9M a day, error rate 0.2%, p99 at 380ms, cold starts at 10.6% of the sample, and then the cost cards: $1.7K a day in cold-start spend with 45 budgets on watch. Alerts arrive root-caused: a cold spike on billing-settle names init p99 1.8s and a 72%-burned error budget.
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 Functions 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 placement and budgets: which of the 80 functions sit in which region, and why the cold bill is $1.7K a day rather than twice that.
Reads the error budget like a gauge: 72% burned on billing-settle means the fix ships this week, not this quarter.
The callers behind the traffic: scheduled jobs, event handlers, retries. They read invocations by trigger and argue about cost from the same table.
CEDX Functions 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.
The route table in API names the fn-* functions backing each path, blast radius and all.
Scheduled automation runs on the same metered model: duration billed in minutes, failures logged by name.
A function ships through the same risk-scored deploy pipeline as everything else: canary, window, rollback.
A cloned environment is where a cold-start fix gets rehearsed before it touches the production region split.
"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."
"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."
"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."
Drag the seat slider to compare your current stitched stack (Retool Enterprise + Kong API Gateway + AWS Lambda + Postman + LaunchDarkly) against running CEDX Functions natively on the unified CEDX estate.
Explore the live CEDX Functions workspace on canonical demo data at /app/functions, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Functions pre-loaded with canonical demo records and connected across the 132-application CEDX estate.