Skip to content
Appunvs Mobile

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

One KeelRuntimeHost load owns one isolated Hermes sub-runtime and mounts an ordinary React Native root view.

03

Managed prebuild

keel prebuild turns a managed JS project into compilable iOS / Android native projects.

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 produces real native installers; Update manages compatible bundles through manifests, runtimeVersion, rollout, and rollback.

06

Submit and Credentials

The credential-vault boundary is independent; real Submit store drivers ship individually as integrations are delivered.

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 →