The product

Six things, done in one place.

Write, reuse, keep it right, control who sees it, find it again, and run the work that comes from it. Each with the piece of the product that shows it.

Write

A comfortable editor, and the things a technical page needs.

Write like a documentA visual editor with a familiar toolbar: headings, lists, bold, tables, images. What you see while you type is what readers get.
Markdown, if you prefer itSwitch to Markdown or Preview at any moment, and choose which one new notes open in. Every note is stored as plain Markdown, so nothing is locked in.
Diagrams from textFlowcharts, sequence diagrams and ER diagrams render live from a few lines.
Images, documents, links and videoUpload a picture once with its alt text and caption, then use it from any note.
Polls, forms and API operationsAsk readers a question inside a note, or cite one operation of an imported API spec as a live badge.

Order path

A failed payment leaves the order pending and asks for another card.

Owner: platform team

Diagram source (Mermaid)

flowchart LR
  Web --> Orders
  Orders --> Payments

Same note, three views. Click a tab.

Reuse

Say it once. Use it everywhere.

Include a whole noteA source note appears inside others and stays current, with no copies to chase.
Claim a term, link by nameDefine a term in one note; anywhere else, refer to it and readers land on the definition.
Stable addressesEvery note has a permanent four-letter address. Rename it or move it and links still work.

Keep it right

Review that comes to you, rather than a calendar reminder nobody keeps.

One question when a source changes"Does this change what it says?" Say yes and every note that includes it is flagged. Say it's wording and nothing is.
Due for reviewGathers notes past their review date, notes whose source changed, and notes citing an API operation that has since gone.
See the web of notesA note's relationships are shown before you change or delete it. One still in use can't be deleted by accident.
Version historyStep back through earlier versions and compare them.

Control who sees what

Roles, audiences and an approval step, without heavy process.

Four rolesReaders read and search. Editors write. Publishers approve and publish. Admins manage people and settings.
Audience blocksMark a paragraph for admins, editors or everyone else. Readers who shouldn't see it never receive it: not hidden, absent.
Publish on purposeEditors send work for review, publishers approve or send it back, and a few seconds of Undo cover a slip.

Find and learn

Answers from what your team wrote, not from the internet at large.

Search that shows the passageResults show the sentence that matched, with your words highlighted, not just a title.
Ask about thisSelect a passage and ask. The answer is grounded in the note, and you choose whether to keep it for everyone. How AI works here →
Summaries, quizzes and flashcardsMade on request and stored with the note, each marked out of date once the note changes.
Draft a noteAnswer a short question and an assistant writes a first draft for you to edit.

Run the work

Turn knowledge into progress, and share it outwards.

Tasks from searchTick the results you need, add them to a task, and watch progress on Home.
A feed for your own siteKeep a website in step with your published notes, and see whether it still is.
Usage and analyticsSee what is read, what is never read, and which sites are syncing.
Switch off what you don't useAdmins decide which features each workspace has, so people only see what applies.

One place to write it down, find it again, and trust it.

Tell us a little about your team and what you'd keep here first, and we'll follow up.