Skip to content
KITABOO
KITABOO
Request a demo
KITABOO SDK

Build your reader.
Not your backend.

Describe the reader you want. Get a fully branded one back, running on a backend that is already live.

Tell us what to buildSee five we built

One paragraph is enough to start. We come back with a reader, not a brochure.

Your promptA kids’ reader in bright colours with big friendly type and read-aloud audio
A children's reader with illustrated storybook pages, large friendly type and a read-aloud controlA magazine reader with a lime header, a full-bleed feature spread and a contents panelA classic literature reader on warm paper, set in a serif face with a contents panel
KITABOO backendAlready running
The preview follows the prompt as it is written, then settles on the reader itself.

Trusted by global leaders

The same platform underneath

Trusted worldwide

Trusted by leading publishers, associations, and enterprises in 25+ countries.

KITABOO client logoKITABOO client logoKITABOO client logoKITABOO client logo99.97%guaranteed uptimeKITABOO client logo
KITABOO client logoKITABOO client logoKITABOO client logoKITABOO client logoKITABOO client logo20 statesserved by Money Vehicle
KITABOO client logoKITABOO client logoKITABOO client logoKITABOO client logoKMK Optometry4000 usersKois Center multi-platform growth

“”

A custom reader used to take a team.

Engineers, designers, and months of work before anyone opened a book. Then the same again for the next brand, and the one after that.

Now it takes an idea. You describe the reader you want and the SDK builds it.

Which means the imprint you shelved because it could not carry its own build is back on the table.

Describe it. Ship it.

No engineers. No designers. No backend to stand up.

01

Describe it

Say what the reader should look like and how it should behave.

PromptA kids’ reader, bright colours, big type
02

It gets built

Theme, fonts, layout and shell, applied to your brand.

03

Ship it

It goes out on a backend that is already live and already running.

Live for your readers

Any identity. Same engine.

Five readers that look nothing alike, running on one backend.

  • A children's reader with illustrated storybook pages and a playful toolbar

    K12

  • A dark corporate reader with a table of contents panel and business course content

    Enterprise

  • A green magazine-style reader with featured article cards

    Magazine

  • A dark reader with a pink accent and a full-bleed feature image

    Dark edition

  • A classic literature reader on warm paper, set in a serif face

    Academic

One engine under all fiveOurs to run

Everything included.

Nothing extra to build.

Theme

Your colours, applied across the whole reader.

Fonts

Your typefaces, at reading sizes that hold up.

Animations

Page turns and transitions, already tuned.

Reader UI layout

How the page, margins and controls are arranged.

Reader shell

The frame around the content, branded as yours.

TOC and resources

Contents, navigation and everything alongside the book.

A month of work, now an afternoon.

The same reader, the same backend, without the build in between.

BeforeOne month per readerNowA few hours
Bar lengths are drawn to the stated figures.

Who this is for.

The teams already running catalogues on KITABOO, and the ones about to.

Publishers

A different reader for every imprint, without a project for each one.

Ed-tech

Your product's look, on a reading engine you did not have to write.

Enterprise L&D

Training material that looks like the company it belongs to.

The backend you are not building.

Already built, already running, and ours to keep running.

Content pipeline

Ingest and packaging, ready for whatever format your catalogue arrives in.

Protection

Encryption, entitlements and who is allowed to open what.

Delivery

Every device your readers own, online and off, kept in sync.

Infrastructure

Hosting, scale and monitoring, through your busiest week of term.

When we improve any of it, your reader gets the improvement. You do not ship anything.

25+
Countries deployed in
34M+
API calls a day
1.5M+
eBooks delivered
6M+
Active users
99.97%
Guaranteed uptime

Answers

Before you ask

Do we need engineers for this?
Not to get a branded reader. You describe what you want and the SDK builds it. If you do have engineers and want to go further than the description takes you, tell us and we will scope that with you.
How different can two readers actually look?
Theme, fonts, animations, layout, shell and navigation all change. A K12 reader and a dark enterprise one share an engine and nothing visible.
What do you run, and what do we run?
You own how your reader looks and behaves. We run the content pipeline, protection, delivery, hosting and scale.
Can we change it after it is built?
Yes. Describe the change the same way you described the reader.
What happens when you update the backend?
Improvements reach your reader without you shipping anything.
How do we start?
Tell us what you want your reader to look like. We will show you one.

Your reader. Your rules. Built today.

Write the reader you want in a line or two. We build it and send it back for you to open.

No deck, no discovery call firstNothing for your engineers to installYou see the reader before you decide anything

Tell us what to build

Describe the reader you want. We reply with a reader built to your description, usually within two working days.

We respect your privacy. We do not share your information. Please see our Privacy Policy.