No — and we don't try to be. Notion, Confluence, Slite, and Slab are great wiki platforms with broad content support. InstaGuide is a content GENERATOR: we fill your existing knowledge base with always-accurate, screenshot-rich how-to articles. Export to HTML and paste into Notion; export to PDF and attach to a Confluence page; or share an InstaGuide link directly. Use us alongside your wiki, not instead of it.

How-to articles. Anything that walks a reader through a specific task in a specific app — “$1” “$1” “$1” These are the articles that benefit most from screenshots and step structure, and the ones that go stale fastest in wikis when manual. For long-form knowledge (policies, FAQs, conceptual explainers), stay in your wiki — InstaGuide isn't built for those.

The two reasons KB articles rot: (1) screenshots are out of date because the app UI changed, and (2) nobody owns the article. InstaGuide tackles both. Re-capture a single step when the UI changes — InstaGuide replaces just that step rather than forcing you to redo the article. The change audit log (Pro+) records who edited what and when, so you can hold owners to a quarterly review cadence. For Confluence/Notion users this is the main reason teams switch their how-to articles to InstaGuide while keeping conceptual content in the wiki.

Yes — Embed is the cleanest option (Enterprise plan). Click Embed on any guide, copy the iframe snippet, and paste it into a Notion /embed block, a Confluence iframe macro, a SharePoint Embed web part, or any HTML editor that accepts iframes. The embedded guide auto-updates when you edit the source — no re-paste, no re-export. Fallbacks (available on all paid plans): share the public link directly (clicks through to the viewer in a new tab), or export to HTML and paste (works everywhere but loses the auto-update). See the <a href='/embed'>Embed feature page</a> for details.

Both. Internal KBs are the most common use case (IT runbooks, ops procedures, sales enablement). But the same exports work for customer-facing help centers: capture how to use your product end-to-end, polish the screenshots with annotations, export to HTML, and host on your help center domain. The Free tier covers 10 articles; Pro covers 200 — enough for most help centers.

Yes — every step's text is indexed and searchable across all your guides. Step descriptions written by InstaGuide are in clear imperative voice (“$1” not “$1”), which makes both search results and quick-scan reading much faster than scrubbing through screencast videos.

Yes. Many teams use InstaGuide as the canonical source for how-to articles and link to InstaGuide guides from Notion / Confluence / Slack / Zendesk. That way one update propagates everywhere, instead of N different copies needing to be kept in sync. Public share links (Enterprise) let external readers consume content without an account.