Identity.
One directory, one session, one set of credentials. A person who joins the organisation exists once, and every application they are entitled to open already knows who they are.
About CEDX Systems
One platform. One hundred and seven applications. One audit trail.
We build the software an organisation runs on, sales, service, finance, people, security and the developer platform underneath all of it. Founded in London in 2011 and still headquartered there.
- Founded
- 2011
- Applications
- 132
- People
- 4,200
- Full product sites
- 8
The thesis
Buying a hundred systems is not the same as buying one.
Most organisations do not have a software problem. They have a hundred small software solutions that were each sensible on the day they were bought, and no agreement between them about who a person is, what they are allowed to see, or what happened last Tuesday.
The cost of that shows up as integration projects, as reconciliation, as a quarterly access review nobody can complete honestly, and as the three weeks it takes to onboard someone who needs eleven accounts. None of it appears as a line item, which is why it persists.
CEDX was built on the opposite bet. Write the platform once — identity, entitlements, events and audit, and then write applications that inherit it rather than reimplement it. The first product took eighteen months. The hundredth took eleven weeks.
The result is a catalogue you can buy one product from and still have the rest of it fit when you need it. Nobody deploys all 132. Almost nobody stops at one.
What every application inherits
Four things nobody has to build twice.
These four services are the whole argument. An application that reimplements any of them is a liability to the estate rather than an addition to it.
Entitlements.
Permission is answered in the platform, not in each product. That is what allows an approval rule written once in finance to hold in procurement, in the service desk and in the AI layer.
Events.
Every meaningful change is published to one bus. Products subscribe to each other rather than integrate with each other, which is why adding the twelfth application costs roughly what the second one did.
Audit.
One trail across the estate, written by the platform rather than by each product. An auditor asks one question in one place and gets an answer that covers everything.
By the numbers
The company, stated plainly.
Availability is measured against the platform control plane and published monthly on the status page. The rest is as at the end of the last quarter.
2011
Founded in London, still headquartered there
132
Applications in the product index
8
Products with composed sites
4,200
People, across six offices
11
Data regions with residency controls
History
How it got to this shape.
Fifteen years, told through the eight decisions that still constrain what we are able to build.
Four people and an accounting ledger.
CEDX was founded by four engineers who had spent the previous decade wiring other companies' systems together. The first product was Ledger, because accounting was the system every integration eventually had to reconcile against.
Identity, before anything else.
Gate shipped as a second product and immediately became the first. Every application written after it inherited authentication, session handling and entitlements rather than implementing its own: the decision the rest of the company is built on.
The platform is extracted, not designed.
CEDX OS was named after the fact. Identity, the event bus, the integration runtime and the entitlement model had already been pulled out of four products that each needed them; naming the result made it something we could commit to.
Frankfurt opens and data stops travelling.
The first region outside the United Kingdom, built because European customers were being asked by their regulators where their records physically sat. Regional isolation has been a product constraint ever since rather than a deployment option.
The fiftieth application, and Forge.
Fifty products in, the queue of things customers wanted was longer than the queue we could build. Forge released the same primitives to customers so the fifty-first application could be theirs.
We start running what we sell.
Managed operations began as a handful of engagements with customers who had bought the platform but could not staff it. It is now a service line with its own on-call rota and its own service levels.
An AI layer a legal team will sign off.
Mira shipped three years after the first internal prototype. The delay was entitlements: a model that can read anything is a model no regulated customer can deploy, so Mira waited until it could be constrained by the same permissions as a person.
One hundred and seven, and counting slowly.
The catalogue grows at roughly six applications a year now. Every one of them has to justify itself against the alternative of being a feature inside something that already exists.
How we work
The things we are not willing to trade.
Four positions we have held long enough that they now decide most arguments before anyone has them.
The platform is the product.
An application that reimplements identity, permissions or audit is a liability, not a feature. If two products need the same thing, it moves down into CEDX OS and both inherit it.
Boring where it counts.
Storage, authentication, billing and the audit trail change slowly and on purpose. Novelty belongs in the parts of the system a customer can turn off.
Write the migration first.
Nothing ships without a documented path off the system it replaces, and a documented path off us. A platform that is hard to leave is a platform nobody senior will approve.
One number, one owner.
Availability, response time and incident count each belong to a named person. Published figures come from the same instrumentation our on-call engineers are paged by.
Leadership
The people accountable for it.
Six executives, four of whom have been here more than a decade. Each of them owns a number that is published rather than described.
Offices
Where the work happens.
Six offices, and eleven data regions that are a separate matter entirely, where a customer's records sit is decided by their region, not by where we happen to have desks.
London
United KingdomRegistered officeRegistered office and headquarters
Sixth Floor40 BishopsgateLondon EC2N 4AJ- Telephone
- +44 20 7946 0112
- Local time
- GMT / BST
New York
United StatesAmericas sales and professional services
Suite 2100195 BroadwayNew York, NY 10007- Telephone
- +1 212 555 0148
- Local time
- ET
Frankfurt
GermanyEU data residency and regional operations
Neue Mainzer Straße 5260311 Frankfurt am Main- Telephone
- +49 69 5050 0139
- Local time
- CET / CEST
Toronto
CanadaPlatform engineering
18th Floor100 King Street WestToronto, ON M5X 1A9- Telephone
- +1 416 555 0173
- Local time
- ET
Singapore
SingaporeAsia-Pacific operations and support
Level 24Asia Square Tower 18 Marina View, 018960- Telephone
- +65 6808 0126
- Local time
- SGT
Sydney
AustraliaSales and customer success
Level 1168 Pitt StreetSydney NSW 2000- Telephone
- +61 2 8015 0194
- Local time
- AET
Recognition
Independently assessed.
GlobalCapital
Enterprise Platform of the Year
FS Tech
Most Innovative Product
RegTech Insight
Best Identity Solution
Cloud Excellence
Platform Team of the Year
SaaS Awards
Best Business Suite
Tech Fast 500
Ambition at Scale
Next
The shortest way to understand the platform is to watch it do something.
Most conversations start with the one system that hurts most today. We will tell you honestly whether we are the right answer to it.