1 of the 17 capabilities tracked on both differs. GitBook starts at Free, then $65/seat/mo, Helpjuice at $249/mo.
| Measure | GitBook | Helpjuice |
|---|---|---|
| Starts at | Free, then $65/seat/mo | $249/mo |
| Charged per | Each agent seat | The workspace |
| AI billed at | $12 per seat | $0.00 per credit |
| Included, where the other says no | 1 capability | 0 capabilities |
1 of the 17 capabilities tracked on both products differs.
| Capability | GitBook | Helpjuice |
|---|---|---|
| Shared inbox | NoThere is no inbox. The nearest thing is Channels on Ultimate, which put the Assistant and the writing Agent into Slack, GitHub and Linear, and comments on content blocks. Neither routes customer email. | Not published |
| Ticket queues | NoNo queues, no assignment, no statuses. Change requests are a content review workflow, not a work queue: they branch, collect review and merge. | Not published |
| Capability | GitBook | Helpjuice |
|---|---|---|
| Autonomous resolution agent | NoNo ticket object exists in GitBook, so nothing can be autonomously resolved. The Assistant has no handoff path to a human queue and no case to leave behind. A support team running GitBook keeps its help desk for anything the docs do not answer. | Not published |
| Resolution over knowledge base | IncludedUltimate, metered at 500 successful answers a month. The Assistant answers readers on the docs site or inside an embed, and connections extend it to GitHub, YouTube and other sources. It answers a person; it does not close a ticket, because there is no ticket. | Not published |
| Guardrails & citations | Not published | Included$449 and above, with the chatbot. Swifty answers from the customer's own articles, respects reader permissions ("If a user is not signed in, they will receive responses based on public articles"), returns a customisable no-results message when it cannot answer, and cites what it used when Show Sources in Responses is enabled. Training is ruled out in writing: "We do not train our AI on your data. Your data is not stored within the AI." Custom instructions shape presentation only: "Custom instructions don't affect what search results are retrieved." |
| Multilingual AI | Not published | IncludedAll plans for article translation, which is the metered part at $0.00015 per character. Swifty itself "supports over 50 languages" for reader conversations and arrives with the AI Suite at $449. |
| Capability | GitBook | Helpjuice |
|---|---|---|
| Public help center | IncludedAll plans, including Free. Unlimited basic sites are free and page views are uncapped on every tier. A custom domain requires Premium. | IncludedAll plans. Four accessibility levels per article or category: Public ("anyone can access it. No login is required"), Internal for logged-in users, URL Only for sharing internal content externally by secret token, and Private restricted to named users or groups. Nesting rules are enforced downward, so an Internal category cannot contain Public content. |
| Custom domain | IncludedPremium and above. A custom subdirectory such as example.com/docs, set up through Cloudflare or Vercel, needs Ultimate. | IncludedAll plans. CNAME mapping with step-by-step setup docs, listed on the feature page as "CNAME branding and custom domain mapping" and backed by SSL certificate encryption. No custom certificate charge is published. |
| Multi-brand | IncludedTwo mechanisms with different gates. Publishing several sites works on any plan and each site carries its own fee. Consolidating several products into one site with sections and groups requires Ultimate. | NoOne subscription runs one knowledge base. The documented route to a second is a second account with its own subdomain, created through a fresh signup: "To add a new Helpjuice account you need to first sign up for a new account. If you receive the issue that the email is already in use just add a new email or '+1' to your existing email." Account linking then lets people switch between them from one login. Whether the second account is billed as a second subscription is not published, but nothing in the pricing page bundles more than one. |
| Versioning | IncludedAll plans. Version history covers viewing, sharing and rolling back to any previous version, alongside change requests and preview deployments. This is the strongest part of the product and it is not gated at all. | IncludedAll plans. Version history, compare versions, restore previous versions, scheduled publishing, publish approval and expiration dates are all listed under the shared Powerful Editor block. The gap is on the way out rather than in the product: version history is absent from the backup zip enumeration. |
| Localization | IncludedSite variants publish multiple spaces on one site for localization on every plan, so manual translations are free. Machine translation that stays in sync is the paid Translations add-on, $25 a month for 50,000 words on Premium and included on Ultimate. | IncludedAll plans, and one of the stronger implementations in this category. Language variants live inside one knowledge base with a front-end language switcher, per-language article versions, translation reports and manual review. The marketing site claims 300+ languages while the pricing card says 40+ for one-click AI translation, so the ceiling depends on whether a human or the model does the work. Content can be copied between languages in an all-or-nothing operation. |
| Article analytics | IncludedPage view analytics on all plans. Search analytics and page ratings require Premium. AI insights, which show how the Assistant answered and where the docs fall short, require Ultimate. | IncludedAll plans, with no retention ceiling published, which is unusual in this category. Five dashboard tabs cover Overview, Searches, Articles, Categories and Users/Groups, tracking views, readings, seconds spent, likes and dislikes, dead-end searches that returned nothing, and a spam checker for search logs. Swifty conversations get their own tracking view. Everything is reachable through the Analytics API with date filters. |
| In-product widget | IncludedUltimate. Docs Embed puts the Assistant, scoped search and a docs browser into your own product through a script tag, an npm package or React components. Not available on Free or Premium. | Included$449 and above. The Swifty chatbot and Helpbar embed inside the knowledge base with a toggle or on any external site with a copied snippet. One documented limitation: on an embedded knowledge base "only public articles will be used", and changing settings requires re-embedding the snippet. |
| SEO controls | IncludedMeta information, sitemap and responsive design are handled on all plans. Opting out of search indexing and private share links require Premium. LLM optimizations (llms.txt, llms-full.txt and .md versions of every page) and an auto-generated MCP server ship on every plan including Free. | Not publishedClaimed in marketing and undocumented in the help centre. The features page lists "SEO-FRIENDLY STRUCTURE", "METADATA MANAGEMENT", "INTERNAL LINKING STRATEGY" and "SEO optimized", and the pricing comparison table has no SEO row at all. No article anywhere in the help centre covers sitemap generation, robots.txt, canonical tags, per-article meta descriptions or an llms.txt for AI crawlers. Full Liquid control over the page templates means a team could add most of this itself, which is a different answer from the product providing it. |
| AI answers over KB | IncludedTwo tiers of it. AI search, which returns a short answer in the search box, starts at Premium. GitBook Assistant, the full chat sidebar with agentic retrieval over the current page and prior conversations, is Ultimate-only. | Included$449 AI-Knowledge Base and above. The $249 card lists AI Writer, AI Search, AI Chatbot, the Chrome extension and the tutorial builder under "AI Suite Not included". Above that line the suite is bundled with no usage allowance published at all. |
| Capability | GitBook | Helpjuice |
|---|---|---|
| Raw data export | Not published | IncludedAll plans, gated by role rather than price. The Backup & Restore zip is Super Administrator only; Settings > Export Data produces Answers, Questions, Categories, Users, Searches and Activities as XLS or CSV for administrators, delivered by email with recent exports also downloadable in-app. A published data dictionary names every column in every report, which is rarer than the export itself. |
| Capability | GitBook | Helpjuice |
|---|---|---|
| Approvals | IncludedPremium and above. "Review & approve edits" and merge rules, which set requirements a change request must meet before it can merge, both start at Premium. Editors can create change requests on any plan but cannot merge them; reviewers can. | Not published |
| Capability | GitBook | Helpjuice |
|---|---|---|
| SAML SSO | IncludedEnterprise only, and priced by quote. SAML 2.0 against any compliant IdP, with JIT provisioning on first login. Google and email-domain SSO, which admits anyone with a matching verified domain as a guest, is on every plan including Free. Admins can always sign in by non-SSO methods even with Enforce SSO on, deliberately, to prevent lockout. | Included$449 and above. SSO is one of the four things the vendor says separates the tiers and it is absent from the $249 card. SAML is the main path with documented setups for Okta, Azure AD and ADFS, plus JWT, LDAP and Active Directory, and Google Sign In. Auto-Create Users provisions accounts on first login and group names map from a SAML attribute. Two caveats the docs state plainly: SSO users can still sign in with a Helpjuice password ("It's not possible to do prevent them from using their Helpjuice credentials at this time"), and auto-provisioned accounts count against the plan's user cap. |
| Role-based access control | IncludedBasic roles (admin, creator, editor, reader) on all plans. Reviewer and commenter require Premium, which also unlocks teams. Team owners, meaning delegated management of a team, is Enterprise-only. Permissions cascade from organization to collection to space. | IncludedAll plans, on two axes. Roles set what a person can do; groups plus the Public, Internal, URL Only and Private levels set what they can see, with passes stored per category and article. Private categories inherit downward ("subcategories or articles must have the same or fewer users/groups than the parent category") and Super Administrators are deliberately exempt: "to avoid losing content, Super Administrators will always have access to private articles/categories, even if they are not in the allowed users list." |
| Custom roles | NoThe seven roles are fixed: guest, reader, commenter, editor, reviewer, creator, admin. No documentation describes defining a role or editing a permission set, and each role's capabilities are enumerated by the vendor rather than configured. | NoFive fixed roles, no role builder and no per-permission editing documented: Super Administrator, Administrator, Collaborator, Draft Writer and Internal Viewer. Granularity comes from groups and content accessibility levels instead of from custom roles. The features page confirms the ceiling: "Four levels of user roles". |
| Audit logs | IncludedEnterprise only, and API only. List organization audit events and Get an organization audit event require an organization admin and an active Enterprise plan. No audit log UI or export file is documented for any published price. | IncludedAll plans. The Activities section logs added, updated, published, reordered, read, opened and removed events across articles, categories, uploads, users, keywords and files, plus sign-ins, filterable by user and exportable to XLSX. It is also the undo mechanism for deleted content, and the two functions share a 90 day window. |
| IP allowlist | IncludedEnterprise, and narrower than the name suggests. It allowlists GitBook's five outbound Git Sync IPs so a locked-down GitHub, GitLab or internal network will accept them. It does not restrict which IPs may reach the GitBook app or a published site. | IncludedAll plans, under Settings > Accessibility & Privacy. Addresses are entered one per line and the failure mode is documented: "If a user tries to access your knowledge base from an IP that is not whitelisted, they will be redirected to a 404 error page." No CIDR or subnet range syntax is documented, so a large office network means listing addresses individually. |
| HIPAA / BAA | NoNo HIPAA claim and no Business Associate Agreement is mentioned on the healthcare industry page, the security industry page, the pricing page or the privacy statement. The healthcare page answers the compliance question with SOC 2, SSO and granular permissions. | Not publishedNo Business Associate Agreement, HIPAA page or healthcare compliance claim appears anywhere on the vendor's site. The compliance vocabulary Helpjuice uses is GDPR and nothing else. Unknown rather than No, because the vendor never addresses the question in either direction, but a healthcare buyer has nothing to work from. |
| SOC 2 | IncludedAll plans. The pricing comparison lists "ISO 27001 & SOC 2 certified" as included on Free, Premium, Ultimate and Enterprise. SOC 2 Type II specifically. The reports themselves are sales-gated: "see the full ISO 27001 or SOC 2 reports? ... please reach out to our sales team". | Not publishedNot claimed anywhere. There is no security page (helpjuice.com/security returns the vendor's 404), no trust centre, no compliance portal and no mention of an audit, a report or a Type II in the help centre, the terms or the privacy policy. The privacy policy commits only to "commercially reasonable technical and organizational measures". |
| ISO 27001 | IncludedAll plans. ISO/IEC 27001 certified, announced alongside the SOC 2 Type II attestation. | Not publishedNot claimed anywhere on the marketing site, in the help centre or in the terms. |
| GDPR | IncludedNo gate. "If you're visiting us from the EU, please see our global privacy practices: we are compliant with the General Data Protection Regulation (GDPR)." Data is nonetheless processed in the United States. | IncludedAll plans. A GDPR compliance statement covers the information audit, DPIA procedures, consent mechanisms and subject access rights, and names Eldin Hajric as Data Protection Officer. A DPA is available rather than published: "If you would like a GDPR Data Processor DPA, please contact us via email at support@helpjuice.com." Contact form emails are relayed through SendGrid and not stored by Helpjuice. |
| Data residency | No"We store and process the information that we collect in the United States." No EU region, no region picker and no residency commitment appears on any plan, Enterprise included. Subprocessors may store and process outside the United States and are not enumerated on the pages read. | NoSingle region, no choice, no enterprise tier to negotiate one on. "Data Stored Securely in the USA" is the only hosting statement the vendor makes, and the privacy policy confirms transfers into the United States for everyone else. No EU, UK or APAC region is offered at any price. |
| Data retention policy | Not published | IncludedFixed windows with one configurable dial. Automated backups run every 12 hours by default and "are stored for 7 days", and the frequency can be set to every 12 hours, daily, weekly or monthly. Deleted articles sit in Activities for 90 days. AI prompts and responses are "generally deleted from our AI interaction logs after 24 hours". None of these is adjustable by the customer beyond backup frequency, and no post-cancellation retention period is published at all. |
| Right-to-erasure tooling | IncludedNo gate. Account deletion is self-serve from the user profile, "barring legal requirements, we will delete your full profile (within reason) within 90 days", and consent-based data erasure can be requested from support within 30 days. Inactive accounts are never auto-deleted. | Not published |
| Capability | GitBook | Helpjuice |
|---|---|---|
| REST API | IncludedNo gate stated. A large OAuth-scoped REST API at api.gitbook.com covering organizations, members, spaces, page content and revisions, sites, site customization, redirects, permissions, search, insights and Ask AI questions. Audit events are the one Enterprise-gated family. | IncludedAll plans. REST and JSON over an account-specific base URL, authenticated by an API key in a header or query parameter, with a documented user impersonation header so a proxy can serve permission-scoped content. V2 endpoints still ship alongside v3. A first-party MCP server at helpjuice.com/mcp exposes "around 53 tools organized across 10 categories" over the same key, which is further than most vendors in this directory have gone. |
| Webhooks | IncludedNo gate stated. Delivered through the integrations platform rather than as a settings-page feature: an integration receives webhook notifications and can handle arbitrary HTTP requests. A generic webhook integration is also listed in the directory. | IncludedAll plans, with thirteen enumerated events across users, articles, comments and categories, including question_archive and question_publish. Each payload carries the activity id, action, actor and an automatic flag for scheduled publishing or expiry. Webhooks are managed entirely through the API, including a test endpoint and a toggle, and last_response_code is returned for debugging. |
| SDKs | IncludedNo gate. An official Node.js client library, a GitBook CLI for driving docs workflows from scripts or coding agents, and a published SKILL.md so AI coding assistants understand GitBook blocks. | Not published |
| App framework | IncludedNo gate stated. A React-inspired platform (ContentKit) for building custom blocks and integrations that run inside GitBook, with OAuth flows, event handling, a manifest file, local development and public or private publishing. | Not published |
| Published rate limits | Not publishedThe rate-limiting page documents the mechanism and not the ceiling. X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers are defined and described as "the authoritative source", with the note that "Different types of API methods are subject to different rate limits". No figure is published, and the 60 in the 429 sample response is an illustration rather than a stated limit. | Included"We limit our API requests to 100 requests per minute." A hard published number rather than a soft threshold. No burst allowance, per-endpoint variation or 429 handling is documented. Collections return 25 records by default and the analytics endpoints accept up to 1,000 per page with results cached for an hour. |
Both entries last checked Sep 9, 2026.
4 of 9 not published by GitBook, checked
3 of 9 not published by Helpjuice, checked