Internal wikis and external doc portals, one platform
Docs work best where the work is. You get internal wikis for the team and public documentation portals for customers, both on the same platform as your boards, helpdesk and source code. Bringing your Confluence or GitBook content across is a faithful HTML import, not a rebuild.
One knowledge base, two audiences — and it deflects support tickets.
Standalone docs tools are read-only islands. Avoryx's knowledge base is the same store your helpdesk portal searches for self-serve deflection — so an article you write for the team is also the answer a customer finds before filing a ticket. Internal wikis and external portals (with anonymous read and invite-based private spaces) come from one source.
- Internal knowledge base: spaces, pages, rich content and attachments
- External doc portals: custom spaces, invite redemption, anonymous public read
- The same published articles power customer self-serve in the helpdesk portal
- Faithful HTML import from Confluence and GitBook (dependency-free converter)
Built with precision — every part of it.
Not a thin feature bolted onto a suite. Here's the real surface area, grouped.
Internal knowledge
- Spaces, pages, rich TipTap content and attachments
- Article CRUD, publish, view surfaces, stats and full-text search
- Pages can reference the issue and release they document, so they don't drift
External doc portals
- Custom external spaces with their own branding
- Anonymous read for public docs; invite redemption for private spaces
- The customer-facing docs portal is a separate surface from internal wikis
Support deflection
- Published articles are searchable by the customer's tenant in the helpdesk portal
- View-count tracking on customer knowledge articles
- One source of truth serves the team internally and customers in the portal
Clean migration
- Faithful HTML → TipTap import from Confluence and GitBook
- Dependency-free sanitizer/converter (no jsdom) — robust on the server
- Attachments migrate through a pluggable storage seam with scan/quarantine
Everything GitBook does — plus what only one platform can.
Avoryx is licensed at the platform level — every module is included in one seat, not billed per module. See pricing. Competitor capabilities vary by plan; verified June 2026. Avoryx's Merchant-of-Record and payouts are on the roadmap; SOC 2 Type II is in progress, not certified.
Why one platform wins here.
Docs next to the code
A page can reference the issue and release it documents — so it doesn't quietly go stale the way a doc in a separate tool does.
Public docs, anonymous read
External portals support anonymous read for public docs and invite-based access for private spaces — no seat required to read.
One source, two audiences
The same knowledge base serves your team internally and your customers in the helpdesk portal, so answers don't fork.
Common questions
Yes — it provides internal wikis and external documentation portals with faithful HTML import from Confluence and GitBook, on the same platform as your boards, source and helpdesk.
The rest of the platform
See it on your real numbers.
15 minutes, your stack, your per-seat math, the revenue back-office live.
