Docs and wiki

Make knowledge part of delivery, not another destination.

Write and organise durable team knowledge, link it to work, and control who can read or change it.

How it works

Write, connect, and keep current.

Docs become useful when they remain close to decisions and delivery.

  1. 01

    Write

    Create structured pages with covers, icons, headings, text, and media.

  2. 02

    Connect

    Link related documents through explicit references and backlinks.

  3. 03

    Govern

    Apply document-level access to explicit members and teams.

Capabilities

A working wiki, not a content silo.

Keep authoring and access practical for the whole team.

Rich pages

Structured writing with covers, icons, headings, text, and media.

Spaces

Organise knowledge with explicit organisation and access scopes.

References

Connect related documents with explicit reference and backlink records.

Sharing and export

Manage sharing from the document header and open the export path when needed.

Control point

Use docs as grounded context.

Workspace search can bring matching docs, work, and memory together before AI drafts or proposes an output.

  • Docs, work, and memory
  • Source context
  • Draft assistance
  • Review before trust

Deployment and security

Control the deployment and the boundary.

Use TOW Cloud, run TOW on controlled infrastructure, or operate an air-gapped Docker Compose deployment. Permissions, identity settings, exports, and AI provider choices stay visible to administrators.

Explore self-hosting
Docker

FAQ

Questions worth answering clearly.

Current product, deployment, and commercial boundaries.

Can document access differ from project access?

Yes. TOW supports space and document access controls in addition to organisation and project scope.

Can existing Markdown be imported?

Yes. TOW includes Markdown import for bringing existing written knowledge into docs.

See TOW in your environment

Bring work, knowledge, and review into one controlled workspace.

Product screenshot