Chapter III · The runtime
Ajo Engine
Sealed before it sails.
A focused runtime built on QuickJS-NG. Its compiler turns a Kit build into precompiled bytecode with a manifest of hashes, capabilities and filesystem roots; the engine loads nothing else and refuses to start when anything does not match.
What Ajo Engine gives you
- Parserless productionThe runtime executes precompiled QuickJS-NG bytecode. It has no parser, eval, REPL or Node module loader.
- Declared authorityRuntime modules, filesystem roots and FIFOs must be declared; a module grant never bypasses a filesystem check.
- Fail-closed startupMissing or mismatched files, an unknown pin or missing required environment stop the App before it runs.
- A sealed artifactA manifest records the engine pin, every chunk’s SHA-256, client assets, declared authority and the feature scan.
- What Kit needsHTTP with SSE and static files, bounded fetch, SQLite with backups, and crypto including Argon2id.
- Honest limitsHashes prove consistency, not publisher authenticity. The security model lists what remains open.
In practice
Seal and run on Linux x64
Status Pre-release. The native packages are verified on Linux x64 (Alpine musl and Freedesktop glibc).
ajo-engine0.2.0The native runtime for sealed applications.
ajo-engine-compiler0.2.0Seals a Kit build into precompiled, hash-pinned bytecode.
pnpm add --save-optional --save-exact ajo-engine@0.2.0 ajo-engine-compiler@0.2.0
pnpm kit build
NODE_ENV=production HOST=127.0.0.1 PORT=8080 APP_URL=http://localhost:8080 \
pnpm exec ajo-engine dist/ajo