KetoyVM is a Kotlin execution runtime for Android that runs Ketoy Bytecode compiled from plain Kotlin source, including Jetpack Compose, coroutines, ViewModels, and Navigation, delivered as a .ktx bundle. Hilt and Room stay in the host app; KetoyVM exposes their functions for new features because updating them requires a Play Store release.

How do I ship Android app updates in seconds?

Write Kotlin, run ./gradlew ketoyBundle, upload the resulting .ktx to Ketoy Cloud, and the KetoyRuntime on every device fetches and executes the new bundle in about 60 seconds without Play Store review or binary split.

Is KetoyVM a server-driven UI framework?

KetoyVM is stronger than a server-driven UI DSL: it executes real Kotlin on device with native Jetpack Compose rendering, real coroutine semantics and real ViewModel lifecycles, so you keep full-surface Compose without a custom schema.

Is this like CodePush or Hermes?

What Hermes is to React Native's JavaScript, KetoyVM is to Kotlin and Compose: a purpose-built execution runtime, not a script interpreter wedged into a different stack.

Postmortem: the 3 AM bundle that wouldn't cancel.

At 3:12 AM a bundle went live that would not cancel. The rollout was at 5%. Here is what we changed in the runtime before 4:00 AM.

A LaunchedEffect(Unit) { while (true) } slipped through. Our cancellation path assumed cooperative suspension; the loop had none. The fix: a deadline hook in the scheduler and a verifier rule that requires a suspension point within any unbounded loop inside LaunchedEffect.

— I.M., Mar 06 2026

Isabel Moreau

Works on coroutines, structured concurrency, and the bundle boundary.