InkRider is in public beta. You can create an account today; the Word add-in and features are still evolving before general availability. About InkRider

Why InkRider exists

We embrace Microsoft Word and make it far more capable. InkRider lets you type what should stay human, and run Python where repeatability and data matter, in the same document.

Made by xwzlabs

InkRider is developed by xwzlabs, s.r.o., a software company based in Prague, Czech Republic. For corporate registry details, registered office, and legal identifiers, see xwzlabs.com.

xwzlabs, s.r.o.

xwzlabs.com

Mixed documents, not all-or-nothing

Typing in Word is the simplest way to finish a deliverable. Manual-only does not scale. Rendering everything from code sacrifices the edits people still need. InkRider is the deliberate middle.

Honor manual work

Judgment, tone, and one-off language stay in Word as plain prose. No render step, no pipeline, no dependency graph for a paragraph only you can write.

Automate what must be reliable

Tables, figures, fees, and branching sections anchor to notebook cells. Re-run when data changes. Drift warnings when a human edit should not be overwritten blindly.

Stay in Word end to end

No notebook-to-DOCX factory. Colleagues still redline a normal file. You add a runtime beside the editor, not a replacement for it.

What we optimize for

Build a Word-native tool for mixed documents: human where it matters, programmatic where it must be, without forcing a clumsy export pipeline.

Usefulness

Ship features that help people produce high-quality documents, not features that only impress engineers.

Clarity

Make it obvious which parts of a file are live from code and which are free-form text.

Control

Keep users close to their code, output, and document. No hidden generation step.

Fit with Word

Design around how people actually write, revise, and approve in Word, and improve that flow instead of fighting it.

Selective automation

Not everything should be code. The product should make that distinction practical, not philosophical.

How we got here

InkRider exists because there is still a gap between computational work and the documents people actually send.

Python is excellent for numbers, structure, and analysis. Word, with its styling and review culture, is still where a huge share of business, research, and legal content gets finished. The industry keeps asking teams to choose: treat the document as a build artifact, or treat it as something you type by hand forever.

We refused that trade. The goal is simple: keep Word as the home for the deliverable, attach a real runtime for the pieces that should not be manual, and make the boundary visible (anchors, drift, re-run) so mixed documents stay trustworthy.

That is the product we want to use ourselves, and the one we are building for everyone who lives in Word but is tired of paying the hidden tax of paste, version sprawl, and numbers that do not agree.

Our founder

Jakub Pecanka

Founder

Jakub started InkRider because he strongly believes that the best way to create high-quality documents is to combine the flexibility of manual design with the reliability and speed of code-based automated generation. Teams should not have to choose between typing in Word and automating with code. Pure manual work can be slow and error-prone, while pure code-based pipelines can be cumbersome, overly demanding to maintain, and weak on layout and aesthetics. InkRider is the product that makes that combination practical.

Jakub's background spans academic research in statistics and the life sciences, with a published track record in peer-reviewed work, as well as consulting and quantitative analysis in banking and finance. This experience gave him a deep understanding of the challenges of creating high-quality documents, and the need for a product that makes that combination practical.

Across those roles, the same friction kept appearing: the numbers lived in code, but the deliverable still had to be finished by hand, under revision pressure, with copy-paste and version sprawl hiding mistakes. InkRider is his answer to that gap: keep Word as the home for the document, leverage its powerful styling and layout features, and attach code only where repeatability and data integrity matter.