Foundation of the Urrora platform
Cryptographic Capsule Layer
CCL is a modular cryptographic architecture that protects sensitive data from the point it’s captured, through transport and authorised processing, into protected storage. Your application can still do its job. Everything around it no longer needs to be trusted with the data.
v1.0 in development
How it works
Sealed everywhere it doesn’t need to be read.
- SealedBrowserSealed before it’s sent
- SealedEdge & gatewayMoved, never opened
- SealedInternal servicesPassed on, never opened
- Authorised useYour applicationOpened only here, by you
- SealedStorageSealed again before it rests
Modular
Four modules. Use one, or all of them.
Each module only needs to understand the one before it and the one after it. That means you choose where protection begins and ends, and extend it as your architecture evolves.
- In the browser
Browser SDK
Seals data in the browser, before it leaves the page. Lightweight and unaware of your business logic.
- At the edge
Gateway
Validates and routes sealed data through public-facing infrastructure without opening it. Can be your starting point if the browser isn’t.
- Inside your boundary
Broker
Hands data to the application you authorise. It cannot open your data on its own.
- At rest
Protected Storage
Returns data to a sealed state after processing, so storage never needs to read it.
Example deployments
- Browser SDK
- Gateway
- Broker
- Your app
- Protected Storage
- Gateway
- Broker
- Your app
- Browser SDK
- Your app
- Protected Storage
Why CCL
What changes for you.
A smaller blast radius
If a gateway, internal service or database is compromised, your clients’ data isn’t automatically compromised with it.
Fits what you already run
Retrofit is a core requirement. Start protecting data where your architecture allows today, and extend over time.
Your data, your keys
Urrora doesn’t hold your data, your database, your business logic or your cryptographic trust.
Ready for what comes next
Designed for crypto-agility, including post-quantum algorithms such as ML-KEM and ML-DSA, so cryptography can change without changing your apps.
Standard, reviewed cryptography
Recognised, independently scrutinised primitives such as AES-256-GCM. Security never depends on keeping the design secret.
Quiet by design
No behavioural tracking, no telemetry about your customers. CCL protects data. It doesn’t interpret it.
Works with what you have
How CCL fits alongside your existing security.
| Technology | What it protects | How CCL relates |
|---|---|---|
| TLS | Protects the connection. | Protects the data itself, after the connection ends. |
| Encryption at rest | Protects disks and databases. | Keeps each record sealed, so anything with database access still can’t read it. |
| KMS and HSMs | Protect keys and cryptographic operations. | Complements them. CCL defines how data moves; your KMS or HSM can hold the keys. |
| Tokenisation and vaults | Move sensitive values into a central store. | Keeps data in your own infrastructure, protected on its journey. No central custodian. |
| End-to-end encryption | Stops every intermediary, including your app, from reading data. | Lets the application you authorise read it, and seals it everywhere else. |
Use cases
CCL in your industry.
Protecting payment data from checkout to settlement
Card numbers, bank details and identity documents pass through checkouts, gateways, fraud tools and support systems. CCL keeps them sealed until the service that needs them.
Read →HealthcareProtecting patient data without getting in the way of care
Patient records move between portals, integration engines, labs and clinical systems. CCL keeps them sealed in transit and at rest, and readable only where care happens.
Read →SaaS, HR & payrollProtecting your customers’ employee data on shared platforms
HR and payroll platforms hold salaries, bank details and ID numbers for thousands of employers. CCL keeps that data sealed across shared infrastructure and support tools.
Read →FAQ
Questions we’re asked about CCL.
What is the Cryptographic Capsule Layer?
CCL is a modular cryptographic architecture from Urrora. It seals sensitive data into a cryptographic capsule at the point it is captured and keeps it sealed through transport and infrastructure, so only the application you authorise can read it. The data is then sealed again for storage.
Is CCL end-to-end encryption?
Not in the strict sense. Strict end-to-end encryption stops every intermediary from reading data, including your own application. CCL is designed for systems where an authorised application genuinely needs to process the data. It protects the data across its journey and confines readable access to the points you authorise.
Do we have to rewrite our applications?
No wholesale rewrite. CCL is modular and retrofit is a core design requirement. You can start at the gateway without changing your front end, or at the browser, and add modules over time. Your application does need a light integration at the point where it receives the protected data.
Does Urrora hold our data or keys?
No. CCL is designed so that Urrora does not become the custodian of your data, database, business logic or cryptographic trust.
Is CCL post-quantum ready?
CCL is designed for crypto-agility, and its roadmap includes the NIST post-quantum standards ML-KEM and ML-DSA. We avoid the term “quantum-proof”: the aim is to change algorithms as standards evolve without redesigning your applications.
What is the performance impact?
We will publish benchmarks measured on CCL itself, across payload sizes, deployment options and workloads. We don’t quote figures borrowed from other products.
Has CCL been independently tested?
Independent cryptographic architecture review, secure code review and penetration testing are part of the path to CCL v1.0. We will share results with customers as part of due diligence.
Contact
Get in touch.
Whether you’re exploring how to protect your clients’ data, interested in CCL, or want to work with us, we’d like to hear from you.