DOCX → PDF
- 20 paying customers on the flagship engine
- 3 prepaid arm’s-length design partners at full price
- Its own charter, adopted
- A named maintainer
- The capacity floor clear — the flagship’s commitments funded and staffed first
01Gates · what opens what
Nothing is announced
before it exists.
One engine exists: Rendlio Sheets, which renders Excel workbooks to PDF and is documented and on sale today. Everything else on this page is a gate — the conditions that would have to be met before a build starts. Not a date, not a preview, not a waiting list. If a gate on this page is not met, the product behind it does not exist and nobody is working on its code.
02Gates · one card per engine
Three gates.
None of them open.
Each card below is the whole gate, not a summary of it: every condition listed has to hold before the first line of that engine is written. Until then the work is paper — a specification and observation of the reference software — and there is nothing to download, reserve, or pre-order.
ODF spreadsheets → PDF
- A written clean-room addendum covering the ODF reference implementation’s licence, adopted by counsel — this one blocks the specification, not just the build
- A pre-registered review of the scale decision
- 2–3 prepaid arm’s-length ISVs serving the public sector
PPTX → PDF, static rendition
- Rendlio Words through its own gate first
- 3 prepaid design partners at satellite pricing
- The shared drawing-model module shipped inside Rendlio Words
There is no bundle, in any state — nothing on this page is for sale, and none of it is packaged with what is. The charter behind each gate is an internal document; write to hello@rendlio.com and we will send you the one you asked about.
03Doctrine · why the gates stay
A fast pipeline is
not evidence of demand.
The obvious argument for building the whole family now is that we could. It was made, and it was rejected. This is the reasoning, so you can hold us to it.
Speed only moves one thing
Development here is substantially AI-assisted, and it is genuinely fast — but it is fast at exactly one task: executing a specification. Demand evidence, the cash and the legal clearance for a rendering oracle, a corpus specialist's time, sign-off against the quality rubric, and the hours of the people running the association do not move at that speed. Every gate on this page tests one of those, not our capacity to write code. So the gates stay: specification work may proceed before a gate; builds and launches may not.
Paper before a gate, code after it
Pre-gate work on a second engine is paper and observation only — the written specification, and measurements taken against the software we are comparing against. No parser, no scaffolding, no prototype. The engine's source is published, so any sibling-engine code sitting in it would be an announcement by accident, and this page would stop being true.
What a gate will not accept
Gates are counted, not argued. Having a team ready, a specification finished, or spare capacity in the pipeline satisfies no part of any gate above — a formed team is never admissible as gate evidence, and neither is enthusiasm. What counts is what each card lists: customers who paid, partners who prepaid, counsel who signed, a maintainer who is named.
If a gate opens
It will show up as a product, with documentation, a price, and its own compatibility report — mounted alongside the flagship rather than in front of it. No launch URL on this site is ever renamed or redirected to make room for a sibling engine, so nothing you link to today moves if one arrives.