Frequently asked, honestly answered.

No. You record walkthroughs, Tome Robot writes the articles. You review and publish. Most teams spend more time approving than authoring.

Install the Chrome extension, click record, walk through the task, click stop. That's it. An in-app recorder is coming so you can embed it in your own product.

Record five of your most-asked workflows. By the time your coffee is cold, you have a searchable KB with grounded answers.

Password fields are never captured — not the keystrokes, not the screenshots. For everything else, deterministic and vision-based redaction blurs PII before an article is ever published.

On Cloudflare's edge: D1 for metadata, R2 for screenshots and audio, Vectorize for embeddings. You can request a regional deployment on Enterprise.

Not yet. The stack is portable (Cloudflare Workers, D1, R2) but we haven't productized self-hosting. Talk to us if it's a blocker.

A nightly job re-fingerprints the screens referenced by each article. If a button moved or a label changed, the article is flagged and a draft update is auto-generated from recent recordings.

Owners and editors by default. You can route them into Slack or a helpdesk via webhooks.

Only if something materially changed. Tome Robot reuses screen fingerprints across recordings, so a single updated walkthrough can heal many articles.

A seat is anyone who can create recordings or edit articles. Readers of a public KB are free and unlimited.

Yes — on Business and above. Internal ones stay behind auth; public ones live at your custom domain.

Side projects and evaluations. Up to 10 recordings/month, one seat, Tome Robot branding on the public KB.

Chrome and Chromium-based browsers (Edge, Brave, Arc) today. Firefox and Safari are on the roadmap.

Not yet. Today the recorder is web-only. A desktop recorder based on Tauri is in early work.

Yes. Every article, recording, and screenshot is exportable via the REST API as Markdown + a bundle of original media.