# Fern is now Postman's home for API docs and SDKs **TL;DR:** Fern is now the official Postman platform for publishing API Developer Portals and generating SDKs. Fern generates docs and SDKs from a single OpenAPI spec and is built for both developers and AI agents, so we're moving Developer Portal publishing there and putting our entire engineering team behind it. If you publish public Developer Portals from Postman today, the Postman plan for Fern is free (worth $3,000 per year), and our team will help you migrate. Your published docs stay live while you move. Today we're making Fern the official home for API Developer Portals and SDKs at Postman. If your team publishes Developer Portals or ships client libraries for your API, whether you started on Postman, Fern, or Liblab, Fern is where that work lives from now on. ## Why we brought Fern and Liblab into Postman More than 500,000 organizations, including 98% of the Fortune 500, use Postman to design, build, and test their APIs. Once an API ships, the work moves to the developers who integrate with it. They need accurate documentation and client libraries in the language they already use. I was an early investor in Fern because its team understood that problem better than anyone. When we [acquired Fern](https://blog.postman.com/postman-acquires-fern/) and Liblab, we brought the best documentation and SDK teams in the industry into Postman. Postman's built-in documentation publishing has helped teams get their docs online for years. Fern builds upon that, purpose-built to serve both human developers and modern AI agents. Rather than split our investment across two docs products, we're putting our entire engineering team behind Fern, so every improvement lands in one place. ## Why Fern Fern is built for API owners who need top-tier Developer Portals for both developer workflows and autonomous AI agents. Here's what you get when you publish with Fern. **Docs and SDKs come from the same spec.** Fern generates your API Reference and your SDKs from one OpenAPI definition. When you change an endpoint, the reference page, the code examples, and the client libraries all update together, so developers never copy a snippet that no longer works. **SDKs in nine languages that read like a person wrote them.** Fern generates idiomatic client libraries in TypeScript, Python, Java, Go, C#, PHP, Ruby, Swift, and Rust. They include typed requests and responses, pagination, retries with backoff, OAuth token refresh, and webhook signature verification. Fern publishes them to npm, PyPI, Maven, and the other package registries on every release. **Built ground-up for AI agents first, alongside developers.** Every Fern site automatically serves an `llms.txt` file and an MCP server, ensuring coding agents seamlessly read your Developer Portal and invoke your API correctly. Ask Fern intelligently answers developer questions directly inside your Developer Portal using cited sources from your content. **Docs your whole team edits.** Engineers write in Markdown and ship through pull requests. Writers and product managers edit in the browser with the visual editor. Fern Agent drafts doc updates from a prompt or a Slack thread and opens a pull request for review. Every pull request gets its own preview URL. **Enterprise controls on day one.** Fern supports SSO, role-based access control for private pages, custom domains, and a 99.9% uptime SLA, and it is SOC 2 Type II compliant. **Proven at scale.** NVIDIA, Adobe, Intuit, ElevenLabs, Twilio, Cohere, and Block publish their Developer Portals and SDKs with Fern. **Built to work with Postman.** Fern also integrates seamlessly with the Postman workflow you already rely on. [Publish your public Postman workspace to Fern](https://learning.postman.com/docs/fern/document-a-collection) in a few clicks. Fern generates a docs site from your collections, and once you [claim it](https://learning.postman.com/docs/fern/document-a-collection#claim-your-teams-fern-docs-site), you can customize and manage it in Fern. ## A Postman plan for Fern To make the move simple and seamless, Postman customers get access to a [dedicated free plan for Fern](/pricing?postman=true) worth **$3,000 per year**. The plan covers hosting your public Developer Portal on Fern, including: - A custom-branded Fern Developer Portal on your domain - An API Reference generated from your OpenAPI spec, with an interactive API Explorer - Ask Fern, `llms.txt`, and an MCP server tailored for AI agents and human developers - Dedicated migration support from the Fern team to transfer your existing Postman Developer Portals ### Payabli migrated its docs from Mintlify to Fern in 3 weeks Today a three-person team keeps docs, examples, and eight SDKs in sync from a single spec, eliminating 200+ hours a year of manual example upkeep. > What I value most about Fern is how closely they listen to their customers. They interview the > people doing the work, they understand what we need, and they ship it. It feels like a genuine > partnership, which is rare in developer tooling. > > Casey Smith, Director of Documentation, Payabli [Read the Payabli story](/customers/payabli) or other migration stories where customers migrated from: - Mintlify: [ElevenLabs](/customers/elevenlabs) - Homegrown tool: [Frame.io](/customers/frame) - Open source: [Unleash](/customers/unleash) - ReadMe: [Deepgram](/customers/deepgram) Want to see how it works first? Read how to [document a collection with Fern](https://learning.postman.com/docs/fern/document-a-collection) in the Postman Docs, see [Fern's Postman integration](https://buildwithfern.com/learn/docs/integrations/postman), and watch for Fern in the AWS Marketplace in the near future. [Book a demo](/book-demo) to get started on the Postman plan, or read the [Fern Docs quickstart](https://buildwithfern.com/learn/docs/getting-started/overview) to set up your first site today.