> For a complete documentation index, see /llms.txt. To read any public page as Markdown, append .md to the URL.

CamelMind is an open-source, self-hostable documentation platform for teams that need modern developer documentation without the costs or limitations of hosted documentation SaaS.

Compared with today's documentation platforms, CamelMind combines:

- Open-source ownership
- API documentation
- Private documentation
- Offline documentation
- LLM-ready documentation

Unlike managed SaaS platforms, you own your documentation stack and can deploy it anywhere. Compared with traditional static site generators, CamelMind includes many developer portal capabilities out of the box.

---

## Pricing comparison

Here is a side-by-side breakdown comparing CamelMind’s pricing and deployment model with other popular documentation platforms:

| Platform | Open Source | Self-host | Free Tier | Paid Plans |
| --- | --- | --- | --- | --- |
| CamelMind | ✅ MIT | ✅ | Unlimited | None |
| MkDocs | ✅ | ✅ | Unlimited | None |
| Docusaurus | ✅ | ✅ | Unlimited | None |
| Astro / Starlight | ✅ | ✅ | Unlimited | None |
| Fern | Partial | Enterprise | Hobby | Team / Enterprise |
| Mintlify | No | No | Starter | Pro / Enterprise |
| Zensical | ✅ | ✅ | Unlimited | Optional support |

---

## Feature comparison

Below is a detailed breakdown comparing the key developer portal, access control, and content management capabilities of CamelMind against other popular documentation platforms:

<div className="overflow-x-auto">

| Feature | CamelMind | MkDocs | Docusaurus  | Fern | Mintlify | Zensical |
| --- | --- | --- | --- | --- | --- | --- |
| Markdown | ✅ | ✅ | ✅  | ✅ | ✅ | ✅ |
| MDX | ✅ | No | ✅  | ✅ | ✅ | <abbr title="Zensical cannot run JavaScript/React components embedded directly in .mdx files natively out of the box.">Limited</abbr> |
| OpenAPI Reference | ✅ | <abbr title="Third-party extension">Plugin</abbr> | <abbr title="Third-party extension">Plugin</abbr>  | ✅ | ✅ | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| Multiple API References | ✅ | No | No | Paid Plan | Paid Plan | No |
| OIDC Authentication | ✅ | No | No  | Paid Plan | Paid Plan | No |
| RBAC | ✅ | No | No  | Paid Plan | Paid Plan | No |
| Versioning | ✅ | No | ✅  | ✅ | ✅ | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| Full-text Search | ✅ | <abbr title="Third-party extension">Plugin</abbr> | <abbr title="Third-party extension">Plugin</abbr> | ✅ | ✅ | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| Offline ZIP | ✅ | <abbr title="You can configure the solution to run in your CI/CD pipeline.">Custom</abbr> | <abbr title="Third-party extension">Plugin</abbr>  | Paid Plan | Paid Plan | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| Master PDF | ✅ | <abbr title="Third-party extension">Plugin</abbr> | <abbr title="Third-party extension">Plugin</abbr> | ✅ | ✅ | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| llms.txt | ✅ | <abbr title="Third-party extension">Plugin</abbr> |  <abbr title="Third-party extension">Plugin</abbr> | ✅ | ✅ | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| Per-page Markdown Export | ✅ | No | No  | ✅ | ✅ | <abbr title="The company plans to release this feature in a future release.">Planned</abbr> |
| [AI View](/features/ai-view) | ✅ | — | — | — | — | — |
| [Run RAG Check](/features/run-rag-check) | ✅ | — | — | — | — | — |

</div>

---

## When CamelMind is the right choice

CamelMind is built for teams that want the flexibility of docs-as-code without giving up the capabilities of a modern documentation platform.

Choose CamelMind if your team wants to:

- Own and self-host your documentation instead of relying on a hosted SaaS.
- Publish both public and private documentation from the same platform.
- Render multiple API references from different OpenAPI specifications in a single documentation site.
- Export documentation as offline ZIP packages or a complete PDF for customers in restricted environments.
- Control access with built-in OIDC authentication and page-level RBAC. See how this compares to [Fern's RBAC](/comparisons/fern-vs-camelmind-rbac) or [Mintlify's RBAC](/comparisons/mintlify-vs-camelmind-rbac).
- Write documentation optimized for both humans and AI assistants with built-in [llms.txt](/features/llms-txt), Markdown exports, and AI-ready features such as [AI View](/features/ai-view) and [Run RAG Check](/features/run-rag-check).

{/*

<Callout type="tip" title="CamelMind may not be the best fit if...">

Every documentation platform has a different focus. CamelMind may not be the best choice if:

- Your primary requirement is automatic SDK generation, where tools like Fern specialize.
- You prefer a fully managed SaaS platform and don't want to host your own documentation.
</Callout>

*/}

---

## Why teams choose CamelMind

Choosing a documentation platform often means making a trade-off.

Open-source tools give you complete ownership and flexibility, but advanced capabilities like API references, authentication, offline exports, and AI-ready documentation typically require a collection of plugins and custom integrations.

Hosted documentation platforms offer a polished, all-in-one experience, but they come with subscription costs, limited deployment options, and less control over your documentation stack.

CamelMind is designed to bridge that gap.

It combines the ownership and flexibility of an open-source, self-hostable platform with many of the capabilities expected from modern documentation platforms—including API documentation, private documentation, offline deliverables, and AI-native documentation workflows.

Instead of stitching together plugins or upgrading to expensive SaaS plans, you get a unified platform built for creating documentation that serves both human readers and AI systems.

---

## Missing a feature?

We're building CamelMind in the open, and your feedback directly shapes what comes next.

If CamelMind doesn't support a feature you need, let us know. We'd love to hear how you're using your documentation, and we'll prioritize features that help the community the most.

Many of CamelMind's capabilities started as real-world requests from documentation teams—and yours could be next.