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 — and, from the same layout, the finished PDF. Hands-free: there is no InDesign, desktop or Server, 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 — and, for a whole edition, the finished PDF, written by the engine from the same layout. No export step in between.
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 inherits the recipe, changes only what differs, and carries its own copy of the format — not a second pipeline.
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 and, when the title asks for it, writes the PDF from the same layout | The final package is exported, then the PDF from it |
| 5 · RELEASE | Hands both over as one release | 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 — as IDML, and as PDF from the same composed pages. 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 on 8 November 2026 with TypePlus 2.0: a complete 16-page edition — 16 tables, 8 charts, 2 advertisements, a linked contents page — composed and written as an editable InDesign file and a finished PDF in 2.7 seconds on a single 2-vCPU cloud instance. The first edition after a fresh start, InDesign file only, took 6.3 seconds.
Environment, in full: AWS Fargate on linux/x86_64, 2 vCPU and 4 GiB, JVM heap 2 GB pre-touched, Amazon DocumentDB 5.0, object storage in the same region, Java 17 and Spring Boot 4.0.8. The PDF is painted inside the engine with Apache PDFBox 3.0.8, from the glyphs HarfBuzz shaped during composition.
Where the seconds go
Fetching the InDesign model from storage 892 ms · composition 837 ms · writing the IDML package and the PDF 862 ms, of which painting the PDF 683 ms · contents page 63 ms · hyperlinks 7 ms · fillers 2 ms. Warm, every edition we measure was written as both files in under three seconds, its PDF in under one. 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
2,669 ms — the whole run
- Fetching the InDesign model from storage
- 892 ms
- Writing the IDML and the PDF
- 862 ms
- Composition
- 837 ms
- Contents page
- 63 ms
- Hyperlinks
- 7 ms
- Fillers
- 2 ms
The six phases add up to 2,663 ms; the run itself measured 2,669 ms. The 6 ms left is the code between the timed phases. Writing the two files includes painting the PDF: 683 ms. 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 files. There is no InDesign, desktop or Server, anywhere in the pipeline: the engine writes the IDML and paints the PDF itself, 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 beside the PDF rather than a flat file alone.
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 and, when you ask for it, the PDF of the same edition. 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?
Two files from one run. A fully editable IDML package — a whole document or a single snippet, depending on what you asked the pipeline for — and, for a whole edition, a PDF the engine writes itself from the same layout: fonts embedded with their licence terms respected, text that searches and copies, the contents page with its links and bookmarks, charts and placed advertisements, and PDF/A when a title asks for it. Set beside the PDF that InDesign exports from the same IDML, no page of the editions we measure differs by more than 1.3 % of its surface. What the PDF does not do yet, we would rather say here than in the third meeting: it is not tagged for accessibility, it writes neither PDF/X nor spot colours, and the EPUB is still exported from the IDML in InDesign. The IDML stays the upstream — the state where a line break can still be moved by hand. A page corrected there by hand is exported from InDesign, the way your team does it today.
What happens when we need a new language?
A new language inherits the rules of the title it comes from and overrides only what differs. It gets its own copy of the format — not a second pipeline to maintain. The same publication has produced three language editions of one title, all from the same engine.
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, with the PDF of the same pages where your format is within what the PDF handles today. Then you open them and judge the page, not the promise.