Actinis Chimera
Coming soon

arm64 on x86_64, through Native Bridge.

A clean-room, open-source Native Bridge for Android. arm64 apps run on x86_64 hosts through Chimera's interpreter and translation tier, with the same Native Bridge interface the closed-source alternatives use — but licensed so you can actually ship it.

chimera · native bridge · build + runtime
# AOSP device build · include Chimera as the Native Bridge
building libchimera.so
linking into system image
image ready · flashable
$ adb logcat · runtime, after boot
I nativebridge detected foreign ABI · arm64-v8a
I nativebridge loading via Chimera
app running on x86_64 · unmodified
$_
What it is
// chimera.md

Chimera is a Native Bridge for Android: arm64 app code is loaded through Android's own guest linker and executed on x86_64 by Chimera's interpreter and translation tier, without a separate emulator beside the runtime.

It's a clean-room, open-source implementation of the Native Bridge interface Android has shipped for years — the same interface the closed-source alternatives use — licensed so you can actually ship it.

Chimera is layered: a shared host runtime core plus thin platform frontends. Today that means an Android/bionic frontend (for AOSP devices); tomorrow a Linux/glibc frontend lets Drion host Android apps on Linux with the same translator.

Under the hood

One runtime core, thin platform frontends

01 · Shared core

Platform-neutral runtime

Runtime lifecycle, guest ELF loading, namespace policy, proxy dispatch, and execution-engine coordination live in a single core that doesn't depend on Android properties or glibc launcher assumptions.

02 · Android frontend

NativeBridge, clean-room

An Android/bionic frontend exports libchimera.so as the system Native Bridge and ships into the system image alongside the guest ARM64 payload. The same interface the closed-source alternatives use — just source-available.

03 · Linux frontend

Host Android apps from Drion

A Linux/glibc frontend lets Drion use the same translator to run arm64 Android apps on Linux hosts. One translator, two host worlds — a direct bridge between the Actinis stack's two open-source pieces.

04 · Correctness first

Interpreter before translation

Chimera brings up an interpreter first, then a translation tier with code caching. We're optimizing for apps that load and run unmodified — not for synthetic benchmarks.

05 · Scope, by design

Not trying to be QEMU

ARM64 guest, x86_64 host, Android-shaped guest payload. Not a generic ARM64 userspace emulator. No ARM32. No x86 guest. No GPL or QEMU code pulled in by default. Not a drop-in copy of Google's private implementation — it's the spec-compatible, source-available one.

Who it's for

Built for the x86_64 Android that closed-source Native Bridges can't ship into.

01

x86_64 Android builds

AOSP-based device builds and emulator products that need arm64 app compatibility on x86_64 hardware without shipping a closed-source Native Bridge.

02

Cloud Android operators

Hosts running Android on x86 servers — including ourselves — who need a Native Bridge they can audit, modify, and re-license.

03

OSS Android forks

LineageOS-class projects, research platforms, and sovereign-compute builds that can't legally ship the closed-source alternative.

Open source

Readable. Auditable. Yours to run

Chimera ships under the European Union Public Licence 1.2 — compatible with GPLv3, drafted by the European Commission, and legally sound in every EU member state.

// public repos coming at launch
Waitlist

Know when Chimera ships

We'll email once — when the code is public. No drip campaigns.