The databases and apps you already run — pre-sealed
The fastest entry into confidential computing isn't a migration project — it's deploying a service you already use, delivered sealed. Pick from the catalog, deploy, done.
Data & Apps is the on-ramp: many estates start here, then extend to Buckypaper and Dyneemes for their own workloads.
Confidential computing's shortest time-to-value
Every organization runs the same critical building blocks — databases holding the crown jewels, collaboration and identity services holding everything else. Each is a place where sensitive data is processed, and therefore exposed, on conventional infrastructure. The Data & Apps catalog delivers those building blocks pre-packaged as confidential services: the upstream software you know, wrapped in hardware enclaves, wired to attestation-bound key custody, deployable through eMCP in minutes.
That makes it the natural first project: no application of yours changes, no migration is scoped — you simply deploy the next database or service sealed instead of exposed, and collect the attestation evidence that proves the difference.
Categories below; the concrete catalog is versioned in the product. [PLACEHOLDER — confirm the current service list with the product team before naming specific projects publicly; examples must match what's actually offered.]
Relational, document and in-memory databases delivered sealed — contents encrypted during query processing, not just on disk: the tier where data-in-use protection pays off first.
Collaboration, identity and workflow services from the catalog run enclave-wrapped — the shortest path to “our most sensitive shared data is sealed.”
Every catalog deployment ships with attestation wired in — evidence of sealed operation is available the day the service goes live.
Catalog services bind to vHSM/Vault for custody — the convenience of ready-made never costs you control of the keys.
Deploy the same sealed service to a European provider, a hyperscaler or your own datacenter through eMCP — placement is a dropdown, not an architecture decision.
Catalog services track their upstream projects — you get the software your teams already know, with the runtime doing the sealing.
Workload starts
Code, config and platform state measured by the CPU
Evidence produced
Hardware-rooted attestation report, signed
Policy checked
Nitride verifies the measurement against your policy
Keys released
vHSM and vault unseal — only now, only to this workload
Workload starts
Tampered image, injected container or rogue host
Evidence produced
Measurement does not match what you approved
Policy rejects
Mismatch logged with its reason, for the audit file
Nothing released
No keys, no secrets — the data stays ciphertext
What teams ask about Data & Apps
Is this a marketplace or a managed service?
The catalog is deployable through eMCP into your own environments — your tenancy, your keys. Managed operation is a deployment-model conversation.
Can we bring a service that isn't in the catalog?
Yes — that's exactly what Buckypaper and Dyneemes are for: your own workloads, sealed the same way. The catalog covers the common building blocks so those don't need a project.
How current do catalog services stay?
Services track upstream releases through the catalog's versioning.
Deploy your first sealed service this week
Pick the database or application your DPO worries about most — we'll show you the sealed version running, with the attestation evidence to prove it.
Ready to go hands-on? Start with eMCP. Your own workloads next? Buckypaper.
.png)
