About

We build the layer under a reading app that nobody sees when it works: getting a whole volume onto a device, at full resolution, before the reader needs it.

Why we started

We came out of manga and comics app teams, and we kept writing the same thing. Every reader eventually needs to work with no connection — on the Chuo line between stations, on a flight, in a basement izakaya — and every app rebuilds the same offline cache to make that happen. Downloading volumes ahead of time, resuming when the signal drops, checking what a reader is actually allowed to keep, verifying a page didn't arrive corrupt: each one is small, and together they eat a quarter.

None of it is the reason anyone opens the app. It is also unforgiving — get it wrong and a reader is staring at a half-loaded page in a tunnel with no way to recover. So teams keep rebuilding it, carefully, instead of working on the reading itself.

What we do about it

Orihon is a delivery endpoint and a reader SDK. You package a volume; the SDK pulls what a reader is entitled to and holds it on the device. Bundles are immutable and content-addressed, so re-issuing a corrected page is a new checksum, not a migration, and a reader's library heals itself on the next open.

We are deliberately not a storefront and not a rights system. We don't run your payments, your accounts, or your catalogue of who-owns-what — we take the entitlement decision you've already made and make the bytes show up. Being in those other paths would mean being in the way.

Where we're at

We're still early. One region, publishers brought on one at a time, and a habit of turning down anything that pulls us off keeping delivery quiet and predictable. If that's the stage you want a vendor at, get in touch.