kernablekernable Cloud
Preview Access · by invitation

Your kernels,
looked after from one place.

Your application and its kernable kernels run in your own infrastructure. kernable Cloud keeps a sealed copy of each writer for your readers anywhere, backs it up, and manages your teams. It never runs your code.

A sealed copy

Each writer sends what it writes to its copy, encrypted with a key only your kernels hold. kernable stores and forwards it and reads nothing.

Readers anywhere

Read-only replicas in other sites and clouds follow the copy. The writer accepts no connection from outside its network.

Backed up

Every copy is backed up within seconds and daily, kept seven days, sealed like the copy itself.

In the EU

Every copy and every backup stays in the EU. Your root key stays offline, with you.

How it fits

your network kernable Cloud (EU) anywhere writer ── kernable push ──sealed──▶ relay: copy shop.eu ◀──sealed── readers ▲ backups, usage │ └────────────── writes sent to a reader travel back the same way ─────┘

kernable Cloud is in Preview Access: no SLA and no on-call yet, support in business hours. The kernel, the SDKs and everything that runs in your infrastructure are open source under the MIT license.