Skip to content
Nibleaf
FeaturesUse casesPricingDocsSelf-hosting
العربية
GitHub9 (9 stars on GitHub)Log inStart free

For support teams

Let your help center answer first.

Customers ask in their own words and get answers from your docs, with the sections cited. You see which searches failed and fill the gaps, in English, Arabic or both.

Start freeSelf-host Nibleaf
A published docs page for a fictional notes app, with Ask AI open on a phone. The answer explains why sync stopped and cites two numbered sections of “Fix sync problems”.
Real product screenshot. Demo content: a fictional notes app.

Sound familiar?

The same questions, every day

The answer is already in your docs, but customers can’t find it, so they open a ticket instead.

You can’t see what people can’t find

Failed searches and confusing pages stay invisible until they show up in your queue.

Two languages, twice the work

Keeping English and Arabic articles in step falls behind every time the product changes.

Ask AI

Answers your customers can check.

Ask AI answers only from your published docs and links each answer to the exact sections it used, so customers and agents can verify it.

  • Replies in the customer’s language, Arabic included
  • When it isn’t confident, it says so and shows suggested articles and your support link
  • Customers rate answers, and you see which questions went unanswered

Requirements: Needs an AI provider key: your workspace’s own OpenAI or OpenRouter key, or one your instance provides. You turn it on per site, and self-hosters also run the optional Qdrant search service. Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.

The Ask AI panel answering a question about exporting notes. Numbered sources name the exact sections of “Export your notes”, with thumbs up and down buttons and two related questions below.
Real product screenshot. Demo content: a fictional notes app.

Insights

See the gaps before they become tickets.

Reports show the searches that found nothing and the pages readers marked unhelpful, so you know what to write next.

  • Each failed search has a “Write an article for this” button that opens a draft
  • Helpful and not-helpful votes for every page
  • Ask AI conversations, ratings and unanswered questions in one place

Requirements: Self-hosters need the optional ClickHouse analytics service for these reports. Search terms are kept only if you turn that on. Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.

The “Searches that failed” table in Nibleaf analytics. Each term, including one in Arabic, has a “Write an article for this” button.The “Searches that failed” table in Nibleaf analytics. Each term, including one in Arabic, has a “Write an article for this” button.
Real product screenshot from a local test site.

AI assistants (MCP)

Fix gaps from the assistant you already use.

Connect Claude, ChatGPT or Cursor to your docs project. It can pull this week’s failed searches, draft an article, translate it, and publish once you confirm the preview.

  • The Support writer preset can draft and publish, but not change settings
  • Ready-made prompts include finding content gaps and a weekly docs health report
  • Changes save as drafts; publishing needs a fresh preview and your confirmation

Requirements: Self-hosters turn it on first; it is off by default. Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.

A recorded Claude Code session connected to a Nibleaf project with a Support writer key. It finds searches with no results, drafts the missing article, previews and publishes it after the person confirms, then translates it to Arabic.
Replay of a real Claude Code session against a demo project, rendered from its transcript. The demo’s product facts, such as the Okta sign-on steps, are made up. Arabic text shows as [Arabic] in this terminal view. Press play to watch.

English and Arabic

One help center, in both languages.

Each language gets its own page tree, right-to-left layout and Arabic-aware search, so Arabic customers get the same help as everyone else.

  • Search finds Arabic words with or without diacritics
  • Ask AI handles questions that mix Arabic and English
  • Your AI assistant can draft a translation for you to review
An Arabic docs site in right-to-left layout on a phone.An Arabic docs site in right-to-left layout on a phone.
Real product screenshot. Demo content: a fictional notes app.

A weekly routine for your support team

  1. 01

    Bring your articles in

    Write in the visual editor, or import a public Mintlify repository from GitHub.

  2. 02

    Turn on Ask AI

    Connect an AI provider key, switch Ask AI on for the site, and add your support link.

  3. 03

    Review what failed

    Check failed searches, unhelpful pages and unanswered questions once a week.

  4. 04

    Draft the fixes

    Write in the editor, or let your AI assistant draft and translate the missing articles.

  5. 05

    Preview and publish

    Confirm the preview and publish. You can roll back to an earlier publish at any time.

Questions from support teams

Does Nibleaf replace our ticketing tool?

No. Nibleaf is your help center and docs site. It has no ticket inbox, live human chat or CRM. When Ask AI can’t answer, it can point customers to the support link you set.

What do customers see when the AI isn’t sure?

A plain message that it couldn’t find a reliable answer, with suggested articles and your support link if you’ve added one. Every answer also shows its sources, and the panel reminds readers that AI can make mistakes.

Can we see what customers asked?

Yes. The Ask AI reports list conversations, ratings and questions your docs couldn’t answer, plus usage and the cost your provider reports. Self-hosters need ClickHouse for these reports, and you can turn off saving conversations. Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.

Who pays for the AI?

With your workspace’s own OpenAI or OpenRouter key, your provider bills you directly. Daily limits on answers and tokens keep usage in check. An instance can also provide a key of its own. Available on Nibleaf Cloud, and when you self-host v0.2.1 or later.

Can it answer in Arabic?

Yes. Ask AI replies in the language of the question, Arabic included, and the docs site, search and editor all work right to left.

Keep reading

Building a customer support knowledge base

How to structure help content customers can find.

Nibleaf vs GitBook

Plans, AI features and hosting, with sources.

Pricing

Free cloud beta or self-hosting, compared.

Nibleaf for product teams

Visual editing, versions and translations for product docs.

Let your docs take the first question.

Start free on Nibleaf Cloud, or run it on your own servers.

Start freeSelf-host NibleafStar on GitHub9 (9 stars on GitHub)

Open source · AGPL-3.0

Documentation you can own.

Read the code, run Nibleaf on your own servers, or start on the free cloud beta.

Nibleaf

Open-source documentation and help center, with first-class Arabic.

Product

  • Features
  • Nibleaf Cloud
  • Pricing
  • Self-hosting
  • Releases

Use cases

  • Support teams
  • Product teams
  • Developers

Compare

  • vs Mintlify
  • vs GitBook
  • vs Docusaurus
  • Mintlify alternatives
  • GitBook alternatives
  • ReadMe alternatives

Resources

  • Documentation
  • Blog
  • Guides
  • Developers
  • RTL readiness checker

Company

  • About
  • Contact
  • Terms
  • Privacy

© 2026 Nibleaf. Built in the open under AGPL-3.0.

AGPL-3.0-onlySource code