Modules Core
iOS integrates KeelModuleCore.xcframework through SPM; Android uses com.appunvs:keel-module-core from Maven.
RUNTIME · TOOLCHAIN · KAS
Every layer can be understood, replaced, and verified independently. A backend is not part of Keel's core ABI.
iOS integrates KeelModuleCore.xcframework through SPM; Android uses com.appunvs:keel-module-core from Maven.
One KeelRuntimeHost load owns one isolated Hermes sub-runtime and mounts an ordinary React Native root view.
keel prebuild turns a managed JS project into compilable iOS / Android native projects.
@keel-ai/cli owns start, doctor, prebuild, build, publish, and rollback; a separate create package scaffolds projects.
Build produces real native installers; Update manages compatible bundles through manifests, runtimeVersion, rollout, and rollback.
The credential-vault boundary is independent; real Submit store drivers ship individually as integrations are delivered.
NO HOSTING
Keel has no keel build web and no Hosting layer. Web, backend, and application framework choices remain replaceable. Read the public docs →