TypePlus is out.
Full speed. Full control.
A fully-fledged market report, composed in seconds.
TypePlus is an in-memory engine for end-to-end editorial layout production. It reads the format you already own as an InDesign model, applies your rules to today’s content, and writes a complete, fully editable IDML file. There is no InDesign runtime anywhere in the pipeline.
The same page, before and after
On the left, your publication format as the engine receives it: frames, styles and space-division rules in place, the content areas still empty. On the right, the same page after one run — text flowed, tables built, charts placed, line breaks decided.
Drag to see the same page before and after composition.
The left-hand page is illustrative: the content areas are shown cleared, so the difference reads at a glance. The right-hand page is not. It is the file the engine wrote, opened in InDesign, with every element still editable. Deterministic by design: the same input gives the same output, and a gate re-measures it at every release.
Quality and speed have, until now, lived in different rooms
Manual typesetting
Skilled, flexible, faithful to the brand — but expensive and slow at scale.
Most automation tools
Fast, but they tend to impose rigid templates, complex configuration, and a residue of manual rework that lands back on your production desk.
The gap is automation that respects the typesetter’s craft. That is the gap TypePlus was built for.
The TypePlus approach
Format-aware
It reads styles, fonts and space-division rules directly from your InDesign model. Your format lives in IDML — not as a template to overwrite, as a property repository.
Content-driven
No rigid grids. The output is shaped by what the content requires, within the rules you defined.
Output-ready
Complete layouts or single snippets, as fully editable IDML, ready to enter the print and digital hand-off you already run.
Three editorial ingredients · One engine · One project
Publication × Policy × Norm Input → Pipeline → Project
Each part has a clear owner and a distinct rate of change. Stable parts stay in stable places; changing parts stay in changing places.
| Component | What it is | Owner | Rate of change |
|---|---|---|---|
| Publication | The format identity of the title: InDesign model, structural schema, brand metadata | Design | Rare — redesigns, brand refreshes |
| Policy | The declarative rules: placement priorities, typographic behaviours, content transformations, fallbacks, localisation variants | Production and senior design | Medium — refinements, new languages, edition variants |
| Norm Input | The day’s payload: any structured source — HTML, XML, JSON, packaged archives — plus images and tabular data | Editorial, CMS, feeds | Continuous — every issue |
| Pipeline | The engine | Engineering | Internal — invisible to editorial users |
Inside the Publication, meaning is carried by naming: any element of the InDesign model given a unique name becomes a Logic Unit Type. A policy addresses that name, not a coordinate on the page.
If the contents are the ingredients, the policies are the recipe. A new language is a policy variant, not a fork of your format.
Five stations, one production line
Each station maps to a step your team already performs by hand.
| Station | What it does | Manual workflow equivalent |
|---|---|---|
| 1 · RAW | Imports the sources as they arrive | The editor delivers the materials |
| 2 · NORM | Normalises content into clean XML | The production assistant pre-flights and prepares the content |
| 3 · COMPOSITION | Styles, sizes and places the content | The senior designer lays out the issue |
| 4 · BUILD | Assembles the final IDML package | The final package is exported |
| 5 · RELEASE | Hands the package over | Delivery to print and digital distribution |
Not a black box. An error is attributable to a station, and a re-run is safe.
What happens inside composition
Every placement decision sees the page as the previous ones left it — the same thing a typesetter does when a story runs long and the next table has to find another home. Composition is single-threaded on purpose; the only parallel work is reading from and writing to storage.
The whole IDML model is read into memory once per run and stays there. Composition never goes back to storage: it works on the in-memory document and writes it out at the end. Text metrics are computed from the font data itself, which is why no Adobe software has to be running anywhere in the path.
Where it earns its place
Data and financial reports
Complex layouts with tables, charts and dynamic data, composed on the day the data lands. This is the family the engine has been built and measured against.
Business and trade media
Newsletters, magazines and briefings where the schedule is part of the product.
Technical, scientific and medical publishing
Structured content that demands precise typographic control, held consistent across large volumes.
High-volume catalogues
Format-intensive publications where manual layout is the dominant cost driver.
What we measured
Measured: a complete 16-page edition — 17 articles, 16 tables, 8 charts, a linked contents page — composed and written in 3.0 seconds on a single 2-vCPU cloud instance. Under 7 even on the very first render of a freshly started instance.
Environment, in full: AWS Fargate on linux/x86_64, 2 vCPU and 4 GiB, JVM heap 2 GB pre-touched, DocumentDB 5.0, object storage in the same region, Java 17 and Spring Boot 3.5.15.
Where the seconds go
Composition 2,019 ms · fetching the InDesign model from storage 838 ms · contents page 93 ms · packaging 77 ms · hyperlinks 8 ms · fillers 5 ms. Four sessions across three builds: 5.7 to 6.0 seconds cold, 3.0 to 3.7 seconds once warm. Every figure is one composition at a time. We have not measured throughput or concurrent load, so we quote none.
One composition, phase by phase
3,026 ms — the whole run
- Composition
- 2,019 ms
- Fetching the InDesign model from storage
- 838 ms
- Contents page
- 93 ms
- Packaging
- 77 ms
- Hyperlinks
- 8 ms
- Fillers
- 5 ms
The six phases add up to 3,040 ms; the run itself measured 3,026 ms. The 14 ms difference is overlap between the instrumented phases, not rounding. One composition at a time, on the environment described above.
Questions procurement asks first
Where does the engine run?
It is a container image with no desktop dependency, so it runs where you put it, provided that is linux/x86_64. What we have measured is a deployment on AWS Fargate with a managed document database and object storage in the same region. The whole environment is defined as infrastructure-as-code, and it is rebuilt from that definition and destroyed at every cycle, with a gate that checks no resource is left behind.
Do we still need InDesign?
Not to produce the file. There is no InDesign runtime anywhere in the pipeline, and no Adobe dependency is declared in the build — the only Adobe library in the graph is xmpcore, under BSD-3-Clause. You still need InDesign where you need it today: to open, review and change the IDML that comes out. That is the point of shipping IDML rather than a flat file.
Does this replace our CMS?
No. TypePlus does not store your content, manage your assets or own your workflow: it reads a structured payload — HTML, XML, JSON, a packaged archive — and returns an IDML file. Where the content lives before and after is your system’s business. And there are no supplied connectors: the integration point is the payload contract, not a plugin. If you already run a CMS, a DAM or a PIM, the engine sits beside them, not on top of them.
What exactly does it produce?
A fully editable IDML package — a whole document or a single snippet, depending on what you asked the pipeline for. It does not stop there: the PDF and the EPUB are exported from that same file in InDesign, the way your team exports them today. IDML is the only channel we have implemented, and we would rather say so here than in the third meeting. The order is what matters: a PDF holds the pages but not the layout that produced them, so a correction found late has to travel back upstream to whatever made it. The IDML is that upstream — the state where a line break can still be moved by hand, and the file both your print and your digital edition come from. What we hand you is not the end of the line. It is the document the other formats come out of.
What happens when we need a new language?
A language is a policy variant, not a second format to maintain. The same publication has produced English, Portuguese and Spanish editions of one title — 14, 16 and 18 pages — from one InDesign model.
How long does onboarding take?
We do not publish a standard figure, because we have not measured one across enough titles to stand behind it. Three pieces of work are prepared per title: your InDesign model is registered as the property repository, your placement and typographic rules are written as policies, and your content sources are mapped. After that, the content changes daily without touching either of the other two. We scope it against your own format before quoting a date.
See it on your own format
The question left is whether it holds on your format, and we answer it in the order that costs you least: show us the InDesign model behind one title, and we read it before either side commits to a pilot — that read is on us. You get back a plain account of what the engine handles today, what would have to be written as policy, and what we would not take on. If the format fits, we scope a pilot on one title together — your model, your rules, your sources, the work named on both sides and agreed before either of us starts. What comes back is a complete market report — tables, charts, news — composed on your format and your rules, and written as a finished, fully editable IDML file. Then you open it in InDesign and judge the page, not the promise.