Contact for pricing
A manuscript that compiles to a real EPUB3, written against a world that checks itself.
Requires Aardvark Studio Core (free)
Desktop workbench · Release 1.0.0
The studio reads your book. You approve what it makes from it.
Give it an ePub and its narrated audiobook and it builds a cited, searchable edition of both — the narration aligned to the prose, the scenes and the cast pulled out, every answer clicking back into the page it came from. That part is free. Four add-ons turn that reading into a finished book, a rendered film, a published podcast, or the look they are all cast in.
Runs on your machine, against a server you deploy. No account on our infrastructure, because there isn't any.
The free Core
A book you can question, not just search
The Core is the whole reading floor and it stands on its own. It splits and transcribes the audiobook, binds each stretch of narration to the sentences it reads, breaks chapters into scenes and beats, and pulls out the characters, props and places along with how they change across the story.
Then you can ask it things — one book, a selection, or every book in the portfolio at once — and every answer cites the passages it drew on. Click a citation and you are in the prose, at that sentence, with the narration ready to play from there.
Everything in the free CoreIngest
ePub plus audiobook, split, transcribed and aligned to the sentence.
Breakdown
Chapters into scenes and beats; the cast, props and places extracted.
Book Assistant
Cited answers across one book or the whole portfolio.
Reference Library
Approved outside sources, fetched politely, cited separately.
Review
An inbox, a queue and a run dashboard. Nothing advances itself.
Cost
GPU-seconds, tokens and machine time at rates you set.
Four products
Each one makes a finished thing
Buy one, or none. Each stands alone on top of the free Core, and each is named for what comes out of it rather than for what is inside it.
Contact for pricing
The whole book as something you watch — every approved frame, timed to the narration, chapter markers already in it.
Requires Aardvark Studio Core (free)
Contact for pricing
An episode grounded in the book, cast to voices, mastered, and pushed to your targets with the feed written last.
Requires Aardvark Studio Core (free)
Contact for pricing
A trained LoRA plus the four prompt blocks that make it renderable — verified present on the render host before it enters the catalog.
Requires Aardvark Studio Core (free)
How it fits together
One reading of the book, underneath everything else
The Core does the reading once. Each product works from that same reading, and hands back something finished. Nothing is re-derived and nothing is guessed at twice.
The platform
Aardvark Studio Core
Ingest · alignment · breakdown · entities · citations · review · cost
Free
Loomwright
A finished book
VisualBook
A long-form video storybook
LitCaster
A published podcast episode
LookBook
A published casting style
And every step of it is gated
A person decides. That is the shape of the whole product.
Work lands for review rather than landing in the finished piece. Approve it, send it back for rework, or reject it and watch the studio supersede everything downstream that rested on it. A rejected frame provably never reaches the cut, because membership is derived from what you decided rather than from a flag somebody could set.
- 1
A stage runs
The studio
It produces artifacts and stops.
- 2
It lands in review
Review inbox
Marked, queued and attributable to the run that made it.
- 3
You decide
A person
Approve, rework, reject — or select individual pieces without closing the run.
- 4
The next stage unlocks
The pipeline
And only then. A gate is not a notification.
Owning two
Pairs that do something neither does alone
None of these is a bundle you have to buy. Each product is complete by itself; these are what happens when two of them are looking at the same book.
Loomwright → VisualBook
Write it here, then film it
Publishing the manuscript compiles an EPUB3 and pre-seeds the breakdown. VisualBook casts and storyboards from exactly that, so the film is made from the book rather than from a description of it.
LookBook → VisualBook
Cast a whole book in one look
A published style is org-wide. The per-book decision is a single choice at Pre-Production ▸ Cinematography, and every frame after it is cast in that look.
Core → LitCaster
A podcast, owning nothing else
LitCaster needs the Core’s reading of the book and nothing from the screen pipeline. It is the shortest path from an ingested book to something you can publish.
What it looks like
The workbench, in three surfaces
Screenshot slot
Book Text, with the narration following along
Screenshot slot
The Book Assistant answering with citations
Screenshot slot
The review inbox — everything waiting on a person
No customer stories here yet
Nothing on this site is a testimonial, a benchmark or a case study, because none has been cleared for publication. When there are numbers worth quoting they will be quoted with the hardware they were measured on.
Before you download
This runs on your hardware
The desktop app talks to a server you deploy — one container and a compose file — and that server holds your books. Some work needs a GPU host you point it at: everything VisualBook and LookBook render, and the speech LitCaster synthesises. On-premise and air-gapped installs are ordinary, not exotic.
- Desktop
- macOS, Windows or Linux — see the download page for what is actually published today.
- Server
- A container image and a compose bundle. One host, one command.
- AI provider
- An Anthropic API key. Every assistant and analysis stage calls it.
- GPU
- Only for the products that render or synthesise. The Core needs none.