Built for teams that ship faster than they can document.

Cactus learns your product from the code and explains it to anyone who asks.

Every release makes yesterday's answers a little more wrong.Cactus rewrites them while you build.

Pied Piper DocsAccountSigning in

Signing in

Sign in with your password, Google or a magic linksingle sign-on.

A reset link works once and lasts fifteen minutesan hour.

Two-factor codes come by SMSfrom an authenticator app.

Docs that keep up with your code.

Cactus writes your help site from your code. When you ship, it rewrites the pages your change touched, the same day.

Anything you write yourself, Cactus leaves alone.

Live support that knows your product.

Customers ask in your product or on your help site. Cactus answers right away and shows the page it used.

If they'd rather talk to a person, your team takes over with the whole conversation.

And your docs are agent ready.

Customers ask Claude, ChatGPT and Cursor about your product too. They read your help site and give the same answer Cactus would.

There's nothing to set up.

How an AI client reads your help site

ClaudeChatGPTCursorClaude CodeWebMCP

How long does a password reset link last in Pied Piper, and how do I get a new one?

Read Resetting your password from docs.piedpiper.com

Claude

A reset link works once and lasts an hour. To get a new one, press Forgot password on the sign-in page and open the newest email, since asking again cancels the older link.

Resetting your passworddocs.piedpiper.com

Ask a follow-up

Ask Cactus about Cactus.

What do I have to write?

Nothing. Cactus writes the help site from the code. Anything you'd rather say yourself, edit, and it stays.

How long does it take to set up?

About five minutes. Connect your code, and Cactus reads it and writes your whole help site while you wait. From then on, ship a change and the pages it touched are rewritten the same day, with a Changelog entry to match.

Can customers trust the answers?

Each answer comes from what the code actually does and names the help page behind it, so a customer can read on. Each page cites the commits it was written from.

Where can customers ask?

In your product, on your help site, or from Claude, ChatGPT or Cursor. The answer is the same everywhere, with the help page behind it.

Ask your own question

Keep shipping. We'll handle the explaining.

Invites go out in order. We'll write when yours is ready.