HelpDocs
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by HelpDocs · www.helpdocs.io
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
HelpDocs at a glance
- Vendor
- HelpDocs
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Outside the EU by default source, captured 10 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 10 Nov 2026
- Panel verdict
- The AI panel rates HelpDocs 2.5/5, the mean of 6 judges. HelpDocs is a customer-facing knowledge base, scored strongest on access control and on publishing and integrations, both flat at 7: SAML 2.0 works with any standards-compliant identity provider, Require SSO covers everyone except guests, and the Lighthouse widget hands JWT-authenticated readers their permissioned articles inside your product, with Slack, an MCP server and a scriptable API. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
HelpDocs is a customer-facing knowledge base, scored strongest on access control and on publishing and integrations, both flat at 7: SAML 2.0 works with any standards-compliant identity provider, Require SSO covers everyone except guests, and the Lighthouse widget hands JWT-authenticated readers their permissioned articles inside your product, with Slack, an MCP server and a scriptable API. Portability and hosting scores 5-7: sixteen named import sources keep categories, set redirects and rehost images, with a staged review, a one-hour undo and whole-base export scriptable over the API with no exit fee. Sovereignty scores a flat 3: the pages state your data will be transferred to the US to be processed and name no subprocessor with a location; custom terms are signed only on the Enterprise plan. Pricing transparency scores 2-3: a 14-day free trial with no credit card is the only published price, while SSO, audit trail, widget and AI drafting sit on unnamed plans. Knowledge governance scores 4-5 on drafts, revisions and an audit trail exportable to CSV, with no public information on page ownership or review workflows.
Speaks for it
- SAML 2.0 documented to work with any standards-compliant identity provider, with Require SSO switching off password sign-in for the whole account except guests
- Sixteen import sources keep categories and structure, set redirects from old URLs and rehost images, with a staged review before anything is written and a one-hour undo
- Whole-base export as a single CSV or a ZIP of per-article folders with metadata, scriptable over the API with no exit fee or retention hold
- Lighthouse widget grants JWT-authenticated readers their permissioned articles inside your own product, with realtime search and right-to-left support
- Deletion requests answered within 30 days, with backup copies cleared within 100 days
Held against it
- Captured pages state your data will be transferred to the US to be processed, and no subprocessor is named with a location
- Custom terms and a customer-supplied DPA are signed only on the Enterprise plan
- We found no public information on per-page owners, review intervals, approval workflows or read confirmations
- The only published price is a 14-day free trial; audit trail, SAML SSO, the Lighthouse widget and AI drafting are each gated to unnamed plans
- AI imports cost 3 credits per page up to 50 pages per crawl, charged at preview even if you cancel the import
Best for
- You are moving a help center from Zendesk Guide, Intercom, Help Scout, Notion or Google Drive and need categories, redirects and rehosted images carried across intact
- You want in-product help — a widget with realtime search that serves permission-restricted articles to logged-in readers via JWT
- You need SAML 2.0 single sign-on with identity-provider group mapping and a switch that forces SSO account-wide
- You want a documented way out — scripted CSV or ZIP export with no exit fee and no retention period
Avoid if
- You need audited document control — knowledge governance scores 4-5, the audit trail sits on certain plans and its CSV export runs one page at a time
- You cannot accept the pages' stated US processing, or you need a custom DPA outside the Enterprise plan
- You must know your annual cost before committing — ask the vendor: the public pages we read do not show it
- Your content lives in Confluence or you need exported page history — Confluence is absent from the sixteen named import sources and no export described includes revisions
The scores
| Criterion | Panel median |
|---|---|
| Editor, structure & search | 3 of 5 |
| Verification, ownership & freshness | 2.5 of 5 |
| Permissions, SSO & administration | 3.5 of 5 |
| Help-center publishing & integrations | 3.5 of 5 |
| Import, export & self-hosting | 3.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1.5 of 5 |
Verification, ownership & freshness
Show reasoningHide reasoning
How this is scored
Whether the content stays true: page owners or experts named per page, verification with a review date and a reminder when it lapses, approval or publishing workflows with drafts and reviewers, read confirmations for mandatory pages, analytics on views, searches without a result and stale pages, duplicate detection, archiving rules, and an audit trail of who changed and approved what.
0 — No way to see who owns a page or when it was last checked beyond the edit date.
3 — Page history and last-edited dates; owners, verification, approvals and content analytics are basic or not described.
5 — An owner or verifier per page, a review interval with reminders, a draft and publish step, page view statistics, and archived pages kept out of search.
8 — Approval workflows with several reviewers, read confirmations for mandatory pages, analytics on failed searches and stale content, duplicate or outdated content flagged automatically, and an exportable audit trail of changes and approvals.
10 — Governance that a regulated organisation runs on: controlled documents with versioned approvals that meet a named standard (ISO 9001, GxP), expiry and review enforced per space, knowledge gaps reported from searches and AI questions, and every published statement traceable to an approved version.
The Operations Lead
Version history, drafts with a publish permission, archiving that keeps retired pages out of search, and an audit trail of all team actions exportable to CSV are shown. But we found no public information on a named owner or verifier per page, review intervals with reminders, approval workflows or read confirmations, which is the heart of keeping content true. 5 6
The IT Administrator
There is a real audit trail — Create, Read, Update and Delete events including logins, filterable, reviewable by Owners and Admins, exportable to CSV — plus drafts, publish permission, and archiving that keeps revisions and drops articles out of search and the sitemap. We found no public information on per-page owners, review intervals with reminders, approval workflows, read confirmations, or stale-content and failed-search analytics, so I could not present this to my auditor as document control. 5 6
The Support Knowledge Manager
Archiving is well designed for keeping content honest — an archived article keeps its revisions, records who archived it and why, and drops out of search and the sitemap — and the Audit Trail tracks create, read, update and delete with a CSV export, available on certain plans. We found no public information on per-page owners, review dates with reminders, approval workflows, read confirmations, or stale-content and failed-search analytics, which is exactly what a twenty-five-agent multilingual team needs to stay true. 5 6
The Engineering Lead
Draft, published and private statuses, per-article versions, and an audit trail of Create, Read, Update and Delete actions that filters by user and exports to CSV give me the who-did-what, and archived articles drop out of search and the sitemap while keeping their revisions. What's missing for content that stays true: we found no public information on named page owners or verifiers, review intervals with reminders, approval workflows with reviewers, read confirmations, or view and failed-search analytics. Governance here rests on edit history and an audit log rather than ownership and verification. 5 6 11
The Quality Manager
The audit trail is genuinely useful for a certifier: create, read, update and delete actions by team members are tracked, Owners and Admins can review activity per user and per article, and filtered results export to CSV — though one page at a time, and only on certain plans. Draft, published and private states exist, archiving preserves revisions and pulls pages from search, and unarchiving returns a draft that must be republished, which is a decent controlled-document shape. But we found no public information on named page owners or verifiers, review dates that expire pages, multi-reviewer approval workflows or read confirmations — exactly the machinery a regulated shop like mine runs on — so it cannot go higher. 5 6
The Skeptic
Drafts and a publish permission exist, archived articles drop out of search, the sitemap and llms.txt while keeping their revisions, and an audit trail tracks every team action with a CSV export — reviewable only by Owners and Admins, gated to certain plans, exported one page at a time. I found no public information on per-page owners, review intervals with reminders, approval workflows or read confirmations. 5 6
Permissions, SSO & administration
Show reasoningHide reasoning
How this is scored
Who may see and edit what, and how the administrator keeps control: roles and permissions per space and per page, restricted or private pages, guest and external access, groups synced from Azure AD/Entra ID, Google Workspace or LDAP, single sign-on (SAML, OIDC), SCIM provisioning, two-factor authentication enforced, an audit log of access and permission changes, and admin controls over sharing and public links. Where the data is hosted and certifications are scored under sovereignty.
0 — Everyone in a workspace sees and edits everything; no permissions of any kind.
3 — Admins, members and guests, or private and shared pages; per-space or per-page rights, SSO and an audit log are basic or not described.
5 — Permissions per space and per page, guest access with limits, single sign-on through Google or Microsoft, two-factor authentication, groups, and admin control over public sharing.
8 — SAML or OIDC single sign-on with any identity provider, SCIM provisioning or LDAP and directory group sync, enforced 2FA, an audit log of views, edits and permission changes, IP or domain restrictions, and permissions honoured by search and AI answers.
10 — Access control an enterprise auditor accepts as documented: granular roles with inheritance explained, just-in-time and external access with expiry, every access and permission change logged and exportable to a SIEM, and the permission model published with its limits.
The Operations Lead
SAML 2.0 single sign-on is documented down to the entity ID and group assertions that map our identity provider's groups onto permission groups with a read-only suffix, and Require SSO covers everyone including the owner. Permissions sit per article and category, guests sign in through their own organization, and the audit trail includes read events. We found no public information on enforced two-factor authentication, SCIM or LDAP provisioning, or IP restrictions. 5 7 8 9
The IT Administrator
SAML 2.0 is documented end to end — assertion consumer URL, Name ID by email, automatic account creation, email-domain restriction, a Require SSO switch applying to everyone including the owner, and group mapping from the identity provider into permission groups with a read-only suffix — and the page states any standards-compliant SAML 2.0 implementation should work out of the box, tested against Okta. Articles can be restricted to specific users and multiple groups, readers can carry groups via JWT, and the audit log records access events with CSV export. We found no public information on SCIM provisioning, enforced two-factor authentication or IP restrictions, and both SAML and the audit trail sit behind plan gates described only as certain plans. 5 7 8 9
The Support Knowledge Manager
SAML 2.0 single sign-on is documented in real depth — any standards-compliant identity provider, group mapping into permission groups with a read-only suffix, default roles, domain limits, and Require SSO for the whole account — and permission groups restrict individual articles to full-access or read-only readers, with JWT access to permissioned articles inside the widget. We found no public information on SCIM provisioning, enforced two-factor authentication or IP restrictions, and the captured pages do not say whether search and AI answers honour permissions. 7 8 9 5
The Engineering Lead
SAML 2.0 with any standards-compliant identity provider, Permission Groups mapped from the SSO assertion with a read-only suffix, a default role for new accounts, and Require SSO that disables password sign-in for everyone including the owner is the enterprise sign-in story I need. Article- and category-level groups with full-access or read-only members, a reserved public group, JWT groups for readers without accounts, and an audit trail that logs reads alongside edits cover most of the ground. We found no public information on SCIM provisioning, LDAP, enforced two-factor authentication or IP restrictions, and SSO is stated to be limited to some plans. 7 8 5 9
The Quality Manager
SAML 2.0 single sign-on works with any standards-compliant identity provider, tested against Okta, group memberships arrive in the SAML assertion (a:read suffix grants read-only), and Require SSO can shut off password sign-in for the whole account, owner included, with email-domain restrictions on who can sign up. Permission groups restrict individual articles and categories, multiple groups per user and per article, with read-only members, owners and admins seeing everything, and JWT-based groups for readers without an account. We found no public information on SCIM provisioning, LDAP, enforced two-factor authentication or IP restrictions, so it stops short of the enterprise-auditor level. 5 7 8 9
The Skeptic
SAML 2.0 is documented to work with any standards-compliant identity provider, permission groups arrive by assertion with read-only variants, Require SSO switches off passwords for everyone except guests, and articles are restricted per user with an audit trail of reads and updates. I found no public information on enforced two-factor authentication, SCIM provisioning, or whether search and AI answers honour the permissions. 5 7 8 9
Help-center publishing & integrations
Show reasoningHide reasoning
How this is scored
How knowledge reaches people outside the editor: public or password-protected sites and help centers with a custom domain, branding and SEO controls, an in-app widget or contextual help, ticket deflection in a help desk, multilingual publishing, integrations with Slack, Microsoft Teams, Jira, Google Drive, help desks and CRMs, a browser extension, a documented REST or GraphQL API, webhooks, and an MCP server or connector for AI assistants.
0 — Content cannot be shared beyond the editor and nothing connects to it.
3 — Sharing a page by public link and a few integrations such as Slack; a branded help center, an API and webhooks are basic or not described.
5 — A published site or help center with custom domain and branding, integrations with Slack or Teams and Google Drive or Microsoft 365, a documented API, and embeds of common tools.
8 — A help center with SEO controls, multilingual publishing, access for logged-in customers and analytics, a widget or contextual help inside the customer's product, help desk integration with ticket deflection, webhooks, and a connector or MCP server for AI assistants.
10 — Knowledge delivered wherever it is needed from one source: internal and public audiences served from the same pages with per-audience rules, a complete API with SDKs and rate limits stated, a marketplace of integrations, and every channel measured in one report.
The Operations Lead
Knowledge leaves the editor in several directions: a published help center with multilingual versions, an in-product widget with realtime search and JWT-gated access to permissioned articles, Slack search and notifications, an MCP server for AI assistants, and a documented API with sitemap and redirects. We found no public information on custom domains, help-desk ticket deflection or publishing analytics. 1 6 9 10 12
The IT Administrator
This is a help-center product at heart: multilingual publishing, a deeply documented in-app widget with realtime search, JWT access to permissioned articles, contact-form callbacks and live-chat hookups, an MCP server for AI assistants, and a Slack integration covering search, article creation and event webhooks. Zendesk, Intercom and Freshdesk appear only as import connections, and we found no public information on custom domains, SEO controls, help-desk ticket deflection, Teams or Jira integrations, or a browser extension. 1 9 10 11 12
The Support Knowledge Manager
The Lighthouse widget puts realtime search inside our product with JWT-gated access to permissioned articles, configurable language, RTL text direction and i18n strings, and the Slack integration searches, creates articles and sends notifications on publish and update events; an MCP server with archive tools and an API the whole knowledge base runs on round this out. We found no public information on custom domains, SEO controls, help desk ticket deflection or help center analytics in the captured pages, and the widget is noted as available on some plans only. 9 10 1 6 12
The Engineering Lead
The Lighthouse widget puts contextual help inside our product with realtime search, JWT access to permissioned articles, i18n with RTL, and live-chat handoff, while an MCP server exposes archive tools and Slack webhooks fire on Article Published and Article Updated — the pipeline-to-pages plumbing I want. Multilingual publishing is listed, and logged-in customers can reach restricted articles through the widget. We found no public information on help desk ticket deflection, publishing analytics, an integration marketplace, or rate limits and SDKs for the API, and the widget is gated to some plans. 9 1 6 10 12
The Quality Manager
This is a help-center product at heart, and the Lighthouse widget is documented down to callbacks, positioning, right-to-left text, pre-filled contact forms and JWT-granted access to permissioned articles from inside the customer's own product. Multilingual publishing, an MCP server for AI assistants, Slack with event webhooks and slash commands, and a documented API covering articles and archiving round out the upper levels. We found no public information on custom domains, SEO controls, help-center analytics or help-desk ticket deflection, which keeps it one step from the top. 1 6 9 10 12
The Skeptic
The widget carries configurable branding, language and right-to-left support, hands JWT-authenticated readers their permissioned articles inside the product, multilingual versions publish and archive per language, Slack searches and creates articles, and an MCP server plus a scriptable API are live. I found no public information on custom domains, help desk ticket deflection, or analytics across the publishing channels. 1 6 9 10
Import, export & self-hosting
Show reasoningHide reasoning
How this is scored
What arriving and leaving would cost: import from Confluence, Notion, Google Docs, Word and Markdown with structure, attachments and links kept, a full export of every space in an open format (Markdown, HTML, XML, PDF) with attachments and history, an API that reaches all content, a stated migration path from Confluence Server or Data Center, open-source code under a named licence, and a self-hosted or on-premise edition with its own documentation.
0 — Content cannot be imported or exported; it can only be read in the vendor's interface.
3 — Single pages export to PDF or Word and some files can be imported; a full export, a Confluence import and self-hosting are basic or not described.
5 — Import from Confluence or Notion and from Word or Markdown, a full workspace export to Markdown or HTML with attachments, a documented API covering pages, and a stated retention of data after cancellation.
8 — A Confluence migration tool or service that keeps hierarchy, permissions and attachments, a full export with history in an open format, a self-hosted or on-premise edition with installation and update documentation, and data returned or deleted on termination under stated terms.
10 — The customer owns the content end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete export another tool can import without loss, and the deletion of every copy on termination documented.
The Operations Lead
Sixteen named import sources keep categories, redirects and rehosted images, with staged review, an undo hour and rerun modes; exports cover the whole base as CSV, HTML folders, Word or PDF and a zip of every attachment, scriptable over the API with no exit fee. The captured migration page does not name Confluence among the sources, and we found no public information on exporting page history or a self-hosted edition. 2 11 12
The IT Administrator
The migration and export story is unusually honest: sixteen named import sources including Notion, GitHub and Google Drive that keep categories and structure, create redirects, rehost images and run in minutes over the source's API, plus a no-exit-fee export — the whole base as CSV, a ZIP of HTML articles with metadata and every attachment, scriptable over the API. But the migration page names sixteen sources and Confluence is not one of them, and we found no public information on a self-hosted or on-premise edition, an open-source licence, carrying permissions on import, or exporting page history — that combination stops the migration of my twelve-year-old page trees dead. 2 11 12
The Support Knowledge Manager
Sixteen import sources including Zendesk Guide, Notion, Intercom, Help Scout and Google Drive keep categories and structure, set redirects from the old URLs, rehost images, run in three modes with a staged review and a one-hour undo, and platform, CSV and Word/Markdown imports are free; export is the whole knowledge base as CSV or a zip of HTML article folders plus every attachment, scriptable over the API with no exit fee. We found no public information on a Confluence import in the captured source list, export of page history is not described, and we found no public information on a self-hosted edition. 11 12 2
The Engineering Lead
Sixteen documented import sources including Notion, Zendesk Guide, GitHub and Google Drive keep categories, rehost images, carry redirects across, run staged with review before anything lands, and offer an undo window — the best-documented arrival path I have seen. Leaving is nearly as good: the whole base as one CSV that other tools read back, per-article folders with index.html and metadata.yaml, a ZIP of every attachment, all scriptable over the API with no exit fee, support ticket or retention period, and deletion within 30 days with backups cleared within 100 days. Confluence is absent from the published source list, no export is described that includes revision history, and we found no public information on a self-hosted or open-source edition. 11 12 2
The Quality Manager
Arriving is well served: sixteen import sources including Notion, Zendesk Guide, Word and Markdown files, with categories and structure kept, images rehosted, redirects set from old URLs, every import staged for review before anything is written, and a one-hour undo window. Leaving is equally documented: the whole knowledge base as one CSV, a ZIP with an HTML page and metadata per article, Word and PDF runs, and a separate ZIP of every attachment, all scriptable over the API with no support ticket, retention period or exit fee. The migration list we captured names sixteen sources and Confluence is not one of them, we found no public information on exports including page history, and no self-hosted or on-premise edition is described. 11 12
The Skeptic
Leaving is documented better than most: sixteen import sources keep categories, redirects and rehosted images, and the whole base exports as a re-importable CSV, an HTML-and-metadata ZIP with a separate media ZIP, or Word and PDF — scriptable over the API with no exit fee or retention hold, and deletion answered within 30 days with backups cleared in 100. I found no public information on a Confluence import, on exporting page history, or on a self-hosted edition. 2 11 12
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where pages, attachments and search indexes are stored and processed, and who the subprocessors are (hosting, CDN, search, email, support, payment, and the AI model provider that reads pages for answers and summaries, with whether content is used for training). Independently sourced by the sovereignty pipeline; a wiki holds internal processes, customer data and trade secrets, so the whole chain counts, not only the database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU data residency available and an EU contracting entity or EU representative, but parts of the chain (CDN, search, email, support, AI model) run through non-EU providers without a stated safeguard, or EU residency is limited to the higher tiers.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the AI model provider, no training on customer content stated, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every page on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including AI, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Operations Lead
A data processing agreement sits in settings and Standard Contractual Clauses are claimed for vendors, but the captured pages state plainly that data is transferred to the US for processing and the subcontractors behind that are not listed. We found no public information on EU hosting, the contracting entity, security certifications, or where the AI models that read pages are run. 2
The IT Administrator
The privacy page states plainly that a lot of their vendors are based in the US and your data will be transferred to the US to be processed, with Standard Contractual Clauses and a self-serve GDPR, UK GDPR and CCPA data processing agreement in settings; on self-serve plans they will not review or sign a custom DPA or your legal team's terms, that being Enterprise-only. We found no public information on an EU contracting entity, named subprocessors with locations, where customer data is stored by default, security certifications, or any self-hosted edition — a chain my works council and regulator would not accept for internal processes. 2
The Support Knowledge Manager
A GDPR posture is documented — terms and privacy policy called GDPR-compliant, Standard Contractual Clauses with vendors, and a self-serve data processing agreement covering GDPR, UK GDPR and CCPA — but the same page states that data is transferred to the US to be processed, no default hosting location for customer content is stated, and no subprocessor list, AI model provider location or training commitment appears. Custom terms and a customer DPA are reserved for the Enterprise plan, and we found no public information on certifications or an EU contracting entity. 2
The Engineering Lead
The captured pages state that data is transferred to the US to be processed by US-based vendors, with a GDPR-compliant DPA covering GDPR, UK GDPR and CCPA available self-serve and SCCs with vendors, while a customer's own DPA is signed only on the Enterprise plan. Beyond that, we found no public information on where customer data is stored, the contracting entity, a named subprocessor list with locations, security certifications, or the AI model provider that reads pages and whether it trains on content. For a fintech under EU rules this reads as a US-processed chain with a standard DPA rather than a European one. 2
The Quality Manager
The captured privacy page states that a lot of the vendor's providers are US-based and that customer data will be transferred to the US to be processed, with Standard Contractual Clauses as the transfer safeguard, and we found no public information on an EU hosting option. A self-serve data processing agreement covering GDPR, UK GDPR and CCPA is offered in settings, while custom terms and customer-supplied DPAs are reserved for the Enterprise plan. We found no public information on the contracting entity or its jurisdiction, on named subprocessors, on ISO 27001 or SOC 2 certifications, or on a self-hosted edition, so the whole chain runs outside Europe as far as these pages show. 2
The Skeptic
The vendor states plainly that a lot of its vendors are US-based and that your data will be transferred to the US to be processed, offers a self-serve DPA covering GDPR, UK GDPR and CCPA with Standard Contractual Clauses, and signs customer terms only on the Enterprise plan. No subprocessor is named with a location, no AI model provider or training stance is stated, and I found no public information on EU hosting, certifications, or where stored data rests by default. 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, readers or guests free or charged, minimum seats, which features (SSO, SCIM, audit log, verification, help-center publishing, custom domain, AI answers, EU data residency) cost extra, the free tier and its limits, storage limits, the self-hosted edition's licence and support price, minimum term and setup or migration fees.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with users, readers or features is unclear.
5 — Tiers are public with their price per user and main inclusions, but at least one commonly needed piece (SSO, AI, readers or guests, EU residency, the self-hosted edition) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (editors, readers, guests, storage), add-ons priced, the self-hosted edition's licence and support cost stated, minimum seats, term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of editors and readers and a feature set, with every add-on, AI credit, setup, migration and support fee and the cancellation and data-return terms published.
The Operations Lead
A 14-day trial with no credit card is public, the PDF import model is priced flat per document, and a website crawl costs 3 credits per page, but the captured pages give no per-user tier price, reader or guest cost, or seat minimum. Single sign-on, the audit trail, the widget and AI drafting are each gated to unnamed plans, so I cannot compute what 180 people plus a read-only workshop would cost. 1 5 7 9 11 12
The IT Administrator
A 14-day trial with no credit card is the only price the captured pages state; we found no public information on per-user or per-tier prices, storage limits, minimum seats or term lengths. The cost drivers are pointed at but never priced — the audit trail, SAML SSO and the widget each sit on unnamed certain plans, while AI imports run on credits (three per crawled page, charged at preview even if the result is discarded) and PDF imports are priced flat per document. I cannot compute an annual cost for 900 staff from this. 1 5 7 9 11 12
The Support Knowledge Manager
The captured pages show a 14-day free trial with no credit card and some unusually specific operational costs — platform, CSV and Word/Markdown imports free, PDF import priced flat per document, crawls at 3 credits per page charged at preview, and no exit fee — but SAML SSO, the widget and the audit trail are each described as available on certain plans with no prices attached. We found no public per-user or per-tier prices, so a buyer cannot compute the annual cost from these pages alone. 1 12 11 7 9 5
The Engineering Lead
What is public amounts to a 14-day trial without a credit card, AI credits quoted at 3 credits per crawled page, PDF import priced flat per document, and free imports for platform connections, CSVs and Word or Markdown documents — no per-user or per-tier prices are captured at all. SAML SSO, the audit trail, the Lighthouse widget and AI drafting are each gated to unnamed plans, so I cannot compute an annual cost from these pages. We found no public information on seat minimums, storage limits, term lengths or setup and migration fees. 1 5 7 9 11 12
The Quality Manager
The only price we found published is a 14-day free trial with no credit card required; per-user tier prices, reader or guest charges, seat minimums and term lengths are absent from the captured pages, so a real annual cost cannot be computed. Add-on economics are partially visible: platform connections, CSV and Word imports are free, PDF imports are priced flat per document, and a website crawl costs 3 credits per page up to 50 pages per crawl, with credits spent at preview even if you cancel the import. Audit Trail, SAML SSO, the Lighthouse widget and AI drafting are each gated to certain plans whose prices we found no public information on. 1 5 7 9 11 12
The Skeptic
The only price I found is a 0 USD fourteen-day trial with no credit card, alongside per-unit AI charges — 3 credits per crawled page, up to 50 pages per crawl, and a flat per-document rate for PDF imports charged at preview even if you import nothing. Audit trail, SAML SSO, the widget and AI drafting are each restricted to unnamed plans; I found no public per-user tier prices, reader or guest pricing, seat minimums, terms or VAT treatment. 1 5 7 9 11 12
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?This support article describes US processing by vendors but does not state where customer data is stored by default. |
0/4 pts | 2 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?On self-serve plans HelpDocs signs only its own standard DPA (custom terms or DPAs require the Enterprise plan). |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about HelpDocs
Is HelpDocs European?
Not determined: the vendor’s pages as captured do not say where HelpDocs is based.
Where does HelpDocs store data?
HelpDocs stores customer data outside the EU by default, per the vendor’s page captured 10 Nov 2026.
Does HelpDocs have a free plan?
Yes. HelpDocs has a free plan, per the vendor’s page captured 10 Nov 2026.
What are the best alternatives to HelpDocs?
As of 18 Nov 2026, the panel rates Document360 (3.5/5), BookStack (3/5) and XWiki (3/5) highest among the other 20 Knowledge Base & Wiki products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Document360 (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: HelpDocs alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. On self-serve plans HelpDocs signs only its own standard DPA (custom terms or DPAs require the Enterprise plan).
- Weak sourcing — Hosting location. This support article describes US processing by vendors but does not state where customer data is stored by default.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 15 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.helpdocs.io Checked 10 Nov 2026 Details →
- 2 Security / trust page — found from the homepage support.helpdocs.io Checked 10 Nov 2026 Details →
- 3 Editor, structure & search — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 4 Editor, structure & search — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 5 Verification, ownership & freshness — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 6 Verification, ownership & freshness — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 7 Permissions, SSO & administration — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 8 Permissions, SSO & administration — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 9 Help-center publishing & integrations — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 10 Help-center publishing & integrations — found from sitemap www.helpdocs.io Checked 10 Nov 2026 Details →
- 11 Import, export & self-hosting — found from sitemap support.helpdocs.io Checked 10 Nov 2026 Details →
- 12 Import, export & self-hosting — found from sitemap www.helpdocs.io Checked 10 Nov 2026 Details →