Does Qidu write my documentation from scratch?

No. It edits what you already have, and leaves everything the change does not touch alone.

Do we have to move our documentation somewhere?

No. The pages stay where they are. Qidu is not a place to write documentation, it is the thing that notices yours has gone out of date.

Is this only for engineering teams?

No. A price change or a policy decision dates a page just as a shipped feature does. The correction goes to whoever owns the page.

Who decides what gets published?

You do. Every correction waits for a person. Edit it, discard it, or leave it sitting.

Qidu: documentation that stays true

Early accessGet a demo

Qidu lands each change you ship where it belongs, then tells whoever needs to know: customers, teams, agents.

You’re shipping faster than you can tell. The product changes. Most pages don’t. Some people find out the hard way. The rest never do.

FIG 0.1

Nobody owns it

Every change is someone's job to make. The pages it contradicts are no one's, so they are the only thing left unattended.

FIG 0.2

It drifts

Never all at once. A sentence at a time, until the page and the product are describing two different companies.

FIG 0.3

Nobody says so

And when a page is finally put right, the people who acted on the old one are not told, because telling them was nobody's job either.

Three ways in. One queue.

1.0Intake

A message in a channel, a customer ticket, a pull request. Qidu picks the change up where the work already happens and goes looking for the pages that now disagree.

1.1A message in a channel
1.2A support ticket
1.3A shipped change
1.4A price or policy update

Every page, in its own words.

2.0Publish

The same fact is worded differently in every system it lives in, and one of them never uses the number at all. There is nothing to find and replace, so each page gets its own correction and the rest of it is left alone.

2.1Only the sentence that is wrong
2.2Its wording, not ours
2.3Every space at once
2.4Reversible, and recorded

Correcting is not telling.

3.0Announce

The approved corrections become a what's new panel you embed in your own product, a digest for the people who were never going to check the help centre, and an MCP endpoint so agents read the same corrected pages your customers do. Same source, written once.

3.1A what's new panel to embed
3.2A digest on your schedule
3.3An MCP endpoint for agents
3.4All of it from what you approved

Early access. No card required.

The communication layerfor your product.