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.
Who we are
InkRider is developed and operated by Inkansen s.r.o., a software company based in Prague, Czech Republic.
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.
Our Mission
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.
Our Story
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.