Self-hosted documentation
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 like auto-generated API references, interactive documentation, SDK code snippets, search, and customizable branding.
However, features requiring external connections aren’t supported, including Ask Fern (AI chat), analytics, live API key population, and SSO integrations.
Extended feature support
PDF export and offline AI chat functionality are in development for self-hosted deployments. Email us if you’re interested in these features.
Setup process
Fern provides your documentation site as a ready-to-run Docker container that you can deploy on your own infrastructure.
- Download the Docker image - Fern provides the location of the most up-to-date Docker image containing the documentation frontend
- Upload your fern folder - Add your documentation source files to the container
- Run the container - Spin up your local server using standard Docker commands
- Configure hosting - Set up your server environment and decide how to publish/share the documentation
- Receive updated Docker images - Fern releases new versions of the Docker image that your team can evaluate and deploy when ready.