For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Getting started
    • Overview
    • How it works
    • Quickstart
    • Project structure
    • Customer showcase
    • Changelog
  • Configuration
    • Overview
    • Site-level settings
    • Page-level settings
  • Writing content
    • Markdown basics
    • Rich media in Markdown
    • Fern Editor
    • Reusable snippets
  • AI features
    • Overview
    • Fern Writer
    • AI-generated examples
    • Markdown access
      • Overview
      • Customize LLM output
      • Agent directives
      • Analytics and integration
    • MCP server
    • API catalog discovery
      • Overview
      • Set up self-hosted documentation
      • Authentication
      • Previews
      • Health check endpoints
      • Releases
  • Public API
    • GETJWT from Fern API key
    • GETAlgolia search credentials
    • GETCurrent user information
  • Fern Writer API
    • GETGet Fern Writer Install Link
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
On this page
  • When to use self-hosting
  • Setup process
  • Architecture diagram
  • Monitoring and health checks
Self-hosted

Self-hosted documentation

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Security

Next

Set up self-hosted documentation

Enterprise feature

This feature is available only for the Enterprise plan. To get started, reach out to support@buildwithfern.com.

Fern documentation websites are hosted on Fern’s infrastructure by default. Self-hosting allows you to deploy your documentation site on your own infrastructure to meet specific security or compliance requirements.

When to use self-hosting

Self-hosting is typically required for organizations that operate without internet access, have strict compliance requirements, or need full control over their documentation servers.

When you self-host, you’re responsible for server setup, security, maintenance, and deciding how to make the documentation accessible to your users.

Unless you have specific requirements that prevent using Fern’s default hosting, we recommend using our managed hosting solution for easier setup and maintenance.

Feature support

Self-hosted deployments include core Fern documentation website features. However, features that require external connections to Fern’s cloud services are not available in self-hosted environments.

Extended feature support

PDF export and offline AI chat functionality for self-hosted deployments are in development. Reach out if you’re interested in these features.

FeatureSupported
AI-generated examplesNo
Analytics + integrationsNo
Announcement bannerYes
API ExplorerYes
API key injectionYes
API ReferencesYes
Ask FernNo
Changelog pagesYes
Component libraryYes
Custom branding and themingYes
Custom CSS & JSYes
Custom domainYes
Custom React componentsYes
Dark / light modeYes
Embedded modeYes
Fern EditorNo
Fern WriterNo
Header and footer customizationYes
Health check endpointsYes
HTTP snippetsYes
IntercomNo
JWT-based authenticationYes
llms.txtYes
Navigation and sidebarYes
OAuthNo
On-page feedbackYes
Page-level access controlYes
Password protectionYes
RBACNo
RedirectsYes
Reusable snippetsYes
SDK code snippetsYes
SearchYes
SEO metadataYes
SSONo
TabsYes
ProductsYes
VersionsYes

Setup process

Fern provides your documentation site as a ready-to-run Docker container that you can deploy on your own infrastructure. For detailed instructions, see Set up self-hosted documentation.

  1. Authenticate with Docker Hub - Use the organization access token (OAT) provided by Fern to log in
  2. Download the Docker image - Pull the fernenterprise/fern-self-hosted image
  3. Upload your fern folder - Add your documentation source files to the container
  4. Run the container - Start your local server using standard Docker commands
  5. Deploy - Set up your server environment and publish the documentation
  6. Receive updated Docker images - Fern releases new versions of the Docker image that your team can evaluate and deploy when ready.

Architecture diagram

Monitoring and health checks

The self-hosted container includes health check endpoints on port 8081 for Kubernetes and Helm deployments.