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
  • 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
  • Authentication and API key injection
  • Self-hosted deployments
Security

Security

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

API key injection

Next

Self-hosted documentation

Fern’s documentation platform is built with security as a core principle, using a client-side architecture for authentication and credential handling. User credentials and sensitive data are stored only in browser cookies and never transmitted to Fern’s servers.

Security questions

Contact support@buildwithfern.com for security reviews, additional documentation, or specific compliance requirements.

Authentication and API key injection

Fern supports multiple authentication methods to secure your documentation. All methods use a client-side fern_token cookie stored entirely in the browser:

  • Role-Based Access Control (RBAC) controls which users can access specific documentation content based on their roles (stores user roles)
  • API key injection automatically populates code examples with user-specific API keys for a personalized experience (stores authentication tokens via JWT or OAuth)
  • Single Sign-On (SSO) integrates with your existing identity provider for seamless authentication (stores identity provider tokens)

These cookies are managed entirely client-side and automatically cleared when the user logs out or the session expires. This approach ensures that sensitive credentials remain under your control and are never exposed to Fern’s infrastructure.

Self-hosted deployments

For organizations that operate in air-gapped environments or need full control over documentation servers, Fern offers self-hosted deployments.