Docs that stay docs.
A fast, markdown-first knowledge base for specs, decisions and the knowledge your team records, connected to execution so it stays useful to whoever works next.
<shared memory/>
Knowledge should survive the conversation that discovered it.
A document can explain a process, record a decision, or capture what an agent learned. Nowrox keeps those objects connected to the work around them, so the context stays useful after the original interaction ends.
Relationships, not folders
A decision affects a launch, explains an issue, and results in work. Those links are typed, so they can be navigated rather than remembered.
Source content stays authoritative
The document remains the record. Relationships make it navigable without copying it into three other places.
Properties you define
Status, type and category: configurable properties that drive filters and the page graph, rather than a fixed schema to work around.
Publishing you control
A page is private to its space, shared by unlisted link, or public. The unlisted link is the credential and is never indexed.
<coming from an all-in-one tool/>
If you're coming from Notion
Tools like Notion are genuinely good at flexibility. One surface, endless databases, almost anything possible in one place. For some teams that is exactly right. Nowrox Docs takes a different approach: a knowledge tool that stays legible because it is not also trying to be your tracker.
All-in-one workspace tools
Nowrox Docs
Philosophy
One flexible surface for everything
A focused knowledge tool, linked to execution
Docs and tasks
Live in the same database and interface
Separate apps, one account and one vocabulary
Best if…
You want one surface and will maintain its structure
You want each tool to stay good at its one job
Stop starting over.
Give your work a place where the context survives the next handoff, session, person and agent.