🔭 Vision

Important

TINO is functional today, but what follows is where we want to take it. These are not features on a roadmap with dates — they are the direction we are working towards and the problems we want TINO to solve.

Replacing desktop document applications

Word processors like Microsoft Word and Apple Pages were designed for a world where documents lived on a single person’s machine. Collaboration meant emailing files, version control meant _v2_final_FINAL.docx, and automation meant macros.

TINO is designed for a different world. Documents live in a git repository, are edited in the browser, and can be generated by a machine as easily as by a human.

The goal is to make the desktop word processor unnecessary — not by mimicking its interface, but by making the underlying workflow so much better that there is no reason to go back.

Note

Word and O365 are fine products for people who enjoy watching a 50-page document silently reformat itself because a colleague opened it on a machine with a slightly different version installed. We did not enjoy that, and we never will. TINO is, in part, our answer to thirty years of _final_v42_ACTUALLY_FINAL_UNSIGNED.docx — we refuse to build on that legacy.

TINO as the automation layer

Typst is a compiler — it turns markup into documents. TINO is the layer on top and it provides:

  • The interface to author those documents

  • The storage to version and organise them

  • The collaboration infrastructure to work on them as a team

This separation is deliberate.

By wrapping Typst in a clean REST API, TINO makes document production a first-class participant in any automation pipeline. Letters, contracts, quotes, reports — anything that can be described as a template and a set of data can be generated, compiled, committed, and delivered programmatically, without a human ever opening an editor.

We see Typst & TINO as the glue between raw data and polished, versioned documents.

TINO as the glue for AI integration

Typst’s structured, readable syntax and TINO’s API together provide a strong foundation for AI-driven document generation. By exposing TINO’s capabilities as tools — most likely via MCP — an AI model can be given the ability to create and edit files, compile documents, and commit results directly into a bucket.

This makes TINO the glue between the AI model and the documents: the model reasons and generates, TINO handles the storage, versioning, and compilation. The result is a versioned, professionally typeset artefact — produced end-to-end without manual intervention.