Skip to content
Appunvs

RUNTIME · TOOLCHAIN · KAS

From a JavaScript project to a native delivery chain.

Every layer can be understood, replaced, and verified independently. A backend is not part of Keel's core ABI.

01

Modules Core

iOS integrates KeelModuleCore.xcframework through SPM; Android uses com.appunvs:keel-module-core from Maven.

02

Isolated runtime

Each app load uses an isolated Hermes sub-runtime and mounts a standard React Native root view.

03

Managed prebuild

Use keel prebuild to generate compilable iOS and Android native projects from a JavaScript project.

04

CLI and scaffolding

@keel-ai/cli owns start, doctor, prebuild, build, publish, and rollback; a separate create package scaffolds projects.

05

Build and Update

Build native installers locally, then manage updates and rollbacks by runtime version and release channel.

06

Submit and Credentials

Manage signing credentials in one place. Store submission is still being developed; check current platform support.

NO HOSTING

Appunvs Mobile stays focused on native mobile.

Keel has no keel build web and no Hosting layer. Web, backend, and application framework choices remain replaceable. Read the public docs →