Choose your flavor
TheoWorks runs two ways. They share the same editor, the same git-native model, and the same schema system — the difference is where it runs and whose infrastructure holds your data.
Web demo
Best for: a first look, evaluating the editor, trying it on a sample project without installing anything.
- Open it in your browser; no install.
- Explore a ready-made sample project or start a blank one.
- Fastest path from "never seen it" to "editing my first need."
Start here: Quickstart → Web demo quickstart.
Self-hosted
Best for: real projects on your own repository, teams with data-residency requirements, and anyone who wants TheoWorks running entirely on their own infrastructure.
- A single guided launcher binary sets up and runs TheoWorks on your machine or server.
- It works against your Git repository — your data never leaves your infrastructure.
- On-premise and cloud-free by design.
Start here: Quickstart → Self-hosted quickstart, then Self-hosting.
At a glance
| Question | Web demo | Self-hosted | | --- | --- | --- | | Install anything? | No | Yes — the launcher | | Where does my data live? | Hosted trial environment | Your own infrastructure | | Works on my private repo? | Use a sample/blank project | Yes — your Git repo | | Good for evaluating the editor? | Yes — fastest | Yes | | Good for real, private work? | No | Yes |
The mental model is identical across flavors — a need is a need, a link is a link, RST round-trips the same way. You can evaluate on the web demo and move to self-hosted without relearning anything.