Developers
Everything your team needs to build on the Kernel Engine: the manifest specification, the artifact lifecycle, and the Control Plane API.
Back to Arqen PlatformDocumentation
Three documents define the integration contract. Everything else — engines, sync, enforcement — follows from them.
Manifest Specification
The declarative contract: meta, five engines, expression namespaces, security rules, and practical authoring pitfalls.
Publish → Pull → Verify
The artifact lifecycle: how a manifest reaches the fleet, gets verified, and hot-swaps without downtime.
API Reference
Control Plane endpoints: edge sync channel, bootstrap claim, admin operations, and the Stripe webhook.
You write the manifest. We run the engine.
Your application is a signed JSON manifest plus its UI assets. The kernel supplies the runtime: five deterministic engines, the offline-first store, the audit chain, and the sync channel. You never fork the engine — you publish a new manifest version.
What you build
Manifest (screens, actions, rules, roles), SQL migrations, plugin logic and UI — packaged and published through the Control Plane.
What the kernel runs
Deterministic execution, tenant isolation, audit chain, outbox sync, license enforcement — identical on every node.
What you get back
A signed, auditable, offline-proof application your customers can run anywhere — with distribution handled for you.