# Nibleaf

> Nibleaf is a documentation platform with a visual Markdown editor, versioned publishing, built-in search, Arabic/RTL support, custom domains, and a free cloud beta at nibleaf.com.

Last reviewed: 2026-08-24

## Key facts

- Public AGPL-3.0 source repository with an anonymously accessible pinned GHCR container release
- Guided Docker Compose installer for the app, API, worker, database, cache, and object storage
- Notion-style WYSIWYG editor over plain Markdown/MDX - content round-trips losslessly, no proprietary format
- First-class Arabic and English authoring with full right-to-left (RTL) support, per-language page trees, and hreflang
- Versioned publishing: every publish is an immutable snapshot, rollback is atomic
- Built-in Orama full-text/fuzzy search remains the default and immediate rollback; source main adds an optional tenant-filtered Qdrant hybrid path, privacy-safe diagnostics, and opt-in grounded answers
- Usage, add-ons, integrations, themes, and MCP below are source-main-only capabilities and are absent from the pinned v0.1.2 artifact
- Provider-neutral usage events and ClickHouse rollups keep missing state unknown and limits advisory; they do not implement payments
- Audited project add-ons and integrations expose explicit availability, consent, credential ownership, and health without returning stored secrets
- Harbor, Manuscript, and Signal support validated theme exchange and runnable Git-native repositories
- Project-bound MCP uses expiring scoped keys and read-only adapters; theme import is preview-only
- Custom-domain and project-subdomain workflows are active; operators must still verify their own DNS and TLS configuration
- First-party reader analytics (page views, top pages, top searches); the hosted service also uses Cloudflare for delivery, security, and web analytics
- Works with any S3-compatible storage (AWS S3, Cloudflare R2, Backblaze B2, or the bundled storage service)
- Nibleaf Cloud (nibleaf.com) is a managed instance, free while in beta

## Pages

- [Home](https://nibleaf.com/): overview and features
- [Arabic home](https://nibleaf.com/ar): Arabic product overview and RTL-first workflow
- [Documentation platforms for Arabic teams](https://nibleaf.com/ar/documentation-platforms): source-backed Arabic buyer guide
- [Nibleaf Cloud](https://nibleaf.com/cloud): hosted documentation sites, free during beta
- [Pricing](https://nibleaf.com/pricing): free cloud beta and self-hosting requirements
- [Self-hosting](https://nibleaf.com/self-hosting): guided installer and deployment architecture
- [About](https://nibleaf.com/about): mission and stack
- [Contact](https://nibleaf.com/contact): product support, privacy, security, abuse, and editorial corrections
- [Nibleaf developer resources](https://nibleaf.com/developers): public API contract, agent access, authentication boundaries, and CLI status
- [RTL documentation readiness grader](https://nibleaf.com/tools/rtl-documentation-readiness): browser-only static HTML checks with transparent unknowns
- [Nibleaf vs Mintlify](https://nibleaf.com/compare/nibleaf-vs-mintlify)
- [Nibleaf vs GitBook](https://nibleaf.com/compare/nibleaf-vs-gitbook)
- [Nibleaf vs Docusaurus](https://nibleaf.com/compare/nibleaf-vs-docusaurus)
- [Mintlify alternatives](https://nibleaf.com/alternatives/mintlify)
- [GitBook alternatives](https://nibleaf.com/alternatives/gitbook)
- [ReadMe alternatives](https://nibleaf.com/alternatives/readme)
- [Terms of Service](https://nibleaf.com/terms)
- [Privacy Policy](https://nibleaf.com/privacy)

## Product truth and source

- [Public source repository](https://github.com/lord007tn/nibleaf): AGPL-3.0 code, issues, releases, and implementation details
- [Product documentation](https://docs.nibleaf.com): current public user and operator documentation
- [Machine-readable pricing](https://nibleaf.com/pricing.md): current plans, limits, and operational responsibilities
- [Nibleaf public OpenAPI specification](https://nibleaf.com/openapi.json): typed public reader endpoints with unique operation IDs
- [Security contact](https://nibleaf.com/.well-known/security.txt): supported disclosure channel

## When to use Nibleaf

Use Nibleaf when a team needs to author, publish, search, or self-host versioned Markdown documentation, especially for bilingual English/Arabic sites, right-to-left interfaces, portable MDX content, or immutable release snapshots. Do not use Nibleaf as a general-purpose CMS, transactional database, or hosted write API: the supported developer contract currently covers public read access only.

## How agents should call Nibleaf

1. Read this file for product routing, then use [llms-full.txt](https://nibleaf.com/llms-full.txt) when the complete product description is needed.
2. Request a human-facing Nibleaf URL with `Accept: text/markdown` for its clean Markdown representation.
3. Read [openapi.json](https://nibleaf.com/openapi.json) before calling public reader endpoints. Use the `siteId` from a published site's URL and do not assume dashboard session endpoints are a supported write API.
4. For a published documentation site, prefer its own `/llms.txt`, `/llms-full.txt`, `/sitemap.xml`, and, when configured by that site owner, `/openapi.json`.
5. If a path returns 404, follow the sitemap or llms index instead of guessing paths.

## Current limitations

- No paid Nibleaf Cloud plan is offered while the service is in beta.
- Live multi-user co-editing is not currently available.
- SAML/SCIM is not currently available.
- Adaptive content is not currently available.
- Grounded answers require optional operator-configured providers and explicit project opt-in; they are not part of the v0.1.2 self-hosted artifact.
- GitHub has a two-way authoring workflow; public GitLab and generic Git imports are currently one-way.

## Blog

- [كيف تختار قالب التوثيق: مرجعي أم تحريري أم موجه للشيفرة؟](https://nibleaf.com/blog/choosing-documentation-template-ar): إطار عملي لاختيار Harbor أو Manuscript أو Signal وفق مهمة القارئ وشكل المحتوى وعمق التنقل وكثافة الشيفرة، لا وفق لقطة شاشة.
- [تقديم Harbor وManuscript وSignal: ثلاثة قوالب لثلاثة أنماط من التوثيق](https://nibleaf.com/blog/documentation-templates-harbor-manuscript-signal-ar): يقدّم Nibleaf ثلاثة قوالب بنيوية لأدلة المنتجات، وقواعد المعرفة الطويلة، ومراجع API كثيفة الشيفرة، مع دعم كامل للعربية وRTL.
- [Nibleaf’s August 2026 source release: six capabilities, one migration path](https://nibleaf.com/blog/nibleaf-august-2026-source-release): A technical launch note for the capabilities merged into Nibleaf main: hybrid search, usage, add-ons, integrations, portable themes, and read-only MCP.
- [إصدار مصدر Nibleaf في أغسطس 2026: ست قدرات ومسار ترحيل واحد](https://nibleaf.com/blog/nibleaf-august-2026-source-release-ar): إعلان تقني عن القدرات المدمجة في فرع Nibleaf الرئيسي: البحث الهجين والاستخدام والإضافات والتكاملات والسمات المحمولة وMCP للقراءة فقط.
- [How to choose a documentation template: reference, editorial, or code-first](https://nibleaf.com/blog/choosing-documentation-template): A practical framework for choosing Harbor, Manuscript, or Signal based on reader intent, content shape, navigation depth, and code density.
- [Introducing Harbor, Manuscript, and Signal: three layouts for three kinds of documentation](https://nibleaf.com/blog/documentation-templates-harbor-manuscript-signal): Nibleaf now includes three structural documentation templates for product guides, editorial knowledge, and code-first API references.
- [كيف تنشر وثائق منتج بالعربية من دون أن تكسر RTL والبحث](https://nibleaf.com/blog/arabic-technical-documentation-rtl-checklist): قائمة فحص عملية لنشر وثائق منتج بالعربية: اتجاه الصفحة، الشيفرة داخل النص، البحث، الخطوط، شجرة الصفحات، ووسوم hreflang قبل النشر.
- [GitBook vs Mintlify in 2026: editor, Git workflow, pricing, and ownership](https://nibleaf.com/blog/gitbook-vs-mintlify): A source-backed GitBook and Mintlify comparison covering editors, Git workflows, API docs, pricing, multilingual content, and self-hosting.
- [Arabic documentation and RTL: a practical implementation guide](https://nibleaf.com/blog/arabic-documentation-rtl): A practical guide to RTL layout, bidirectional code, Arabic search, language trees, hreflang, and typography for product documentation.
- [Your Docs Should Live in Plain Markdown (Even With a Visual Editor)](https://nibleaf.com/blog/docs-should-live-in-plain-markdown): Why plain Markdown is the portability contract for documentation: greppable, diffable, AI-ready, and compatible with a visual editor.
- [Why we built Nibleaf for teams that want to own their docs](https://nibleaf.com/blog/introducing-nibleaf-open-source-mintlify-alternative): Why Nibleaf combines a visual Markdown editor, versioned publishing, built-in search, and Arabic support in one documentation platform.
- [Open-source documentation tools in 2026: how to choose](https://nibleaf.com/blog/open-source-documentation-tools): Compare Docusaurus, MkDocs Material, Starlight, Fumadocs, BookStack, Wiki.js, and Nibleaf by authoring model, search, i18n, and hosting.
- [Self-Host a Documentation Site with Docker Compose](https://nibleaf.com/blog/self-host-documentation-site-docker-compose): A practical walkthrough for self-hosting a documentation site with Docker Compose: server sizing, secrets, custom domains, backups, and upgrades.

## Full details

- [llms-full.txt](https://nibleaf.com/llms-full.txt): complete plain-text product description