Blaze's own app engine for Android
Blaze Kiln runs apps inside Blaze, like a contained fire in a kiln, so the Blaze agent can use them on your behalf.
In development · not yet in a public releaseWhy we built it
For the Blaze agent to work with an app, the app has to run somewhere Blaze controls. Instead of renting servers to run apps remotely, we chose to run them on your phone, inside Blaze.
We first audited an existing open-source engine. We rejected it on provenance grounds: we couldn't be confident where all of its code came from or how it was licensed. So we decided to build our own.
How it was made
A clean-room build
Blaze Kiln was written from scratch by Blazeinchue, using only:
- Android's public documentation and the Android Open Source Project (AOSP)
- Permissively licensed libraries (Apache-2.0, MIT and BSD)
It uses no code from third-party virtualization projects, and no GPL, LGPL or unlicensed code.
How it works
At a high level, when an app is added to Blaze Kiln:
Read and validate
Kiln reads the app's package and checks that it's well formed.
Check integrity
It verifies the package hasn't been altered.
Give it its own storage
Each app gets isolated storage of its own.
Launch through Blaze
The app starts in a Blaze-managed slot, with its own launch tokens.
Where it stands
Core
Package reading, validation, storage isolation and launch routing. Passes its automated test suite. The first phone test build is due today.
Multi-screen apps
Follows in the coming weeks.
Broader compatibility
Follows after Milestone 2.
Each milestone ships as its own update, and only after testing on real devices.
Honest limits
Not supported
- Apps that need Google sign-in or push services
- Banking apps
- DRM-protected video
- Apps with anti-tamper protection
Trusted open-source apps only, for now
Full isolation between apps is still being built. Until it is, Kiln only allows trusted open-source apps.