Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

Postman Moves Docs Publishing to Fern With a Free Plan for Customers

Postman's CEO said Nov. 16 that Fern is now its official platform for developer portals and SDKs, with a free plan for Postman customers.

3 min read

FernPostmanAPI reference

Product photo of a white mailbox on a hot pink, magenta and orange gradient

Postman is moving developer portal publishing to Fern and putting its “entire engineering team” behind the product, CEO Abhinav Asthana wrote in a Nov. 16 post on Fern’s blog. Fern is now “the official Postman platform for publishing API Developer Portals and generating SDKs,” he wrote, and Postman customers who publish public portals get a free Fern plan that Postman values at $3,000 a year.

Key takeaways

  • Postman chose Fern over funding two docs products, Asthana wrote.
  • The Postman plan for Fern is free and covers a branded portal on a custom domain, an API reference with an interactive explorer, Ask Fern, llms.txt and an MCP server.
  • Published Postman docs stay live during the move, and Fern’s team helps with migration.
  • Postman has already generated Fern sites for teams with public workspaces, according to Postman’s documentation.

Postman picked one docs product over two

Postman will stop splitting its investment between its built-in documentation publishing and Fern. “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,” Asthana wrote. He said the decision applies to teams that started on Postman, Fern or Liblab, the SDK company Postman also acquired.

Postman bought Fern on Jan. 8. In the acquisition post that day, Asthana wrote that Fern’s “product, brand, and roadmap will stay the same” and that Fern had a team of 25 and more than 200 customers. The Nov. 16 post says more than 500,000 organizations use Postman.

The free plan covers a public portal

The Postman plan for Fern covers hosting for a public developer portal. Asthana listed a custom-branded portal on the customer’s domain, an API reference generated from an OpenAPI spec with an interactive API explorer, Ask Fern with llms.txt and an MCP server, and migration support from the Fern team. Customers start the plan by booking a demo, the post said.

Postman has already built some of the sites

Postman generates a Fern site from a team’s public workspaces before anyone asks for one, according to the “Document a collection with Fern” page in Postman’s documentation, last updated Nov. 10. The site is live at <team-name>.docs.buildwithfern.com and holds a welcome page, a quickstart and an API reference built from the team’s public collections. Postman does this for teams on any plan, the page says.

Only a team admin can claim the site, and the claim link works for 15 minutes. The admin can then customize and publish it from Fern’s dashboard. The site syncs with the team’s public collections once every 24 hours, even before anyone claims it. Teams with no generated site can publish a collection to Fern from the collection’s overview tab, and Fern puts the docs in a GitHub repository the team owns.

The take

We think Postman’s size matters more than any feature in the post. Fern had more than 200 customers in January, and Postman says more than 500,000 organizations use it. A docs platform usually has to win each customer on its own. Fern now arrives inside a tool those teams already use, at no cost for a public portal.

We’d read the free plan carefully before counting on it. The post describes hosting for a public portal. It names SSO, role-based access and SDK generation as Fern features, and it does not list them under the plan. Ask what private docs or generated SDKs cost before migrating.

Check for an auto-generated site this week. Postman’s documentation says a team with public workspaces may already have a Fern site live on a docs.buildwithfern.com address. Open a public collection as a team admin, click Publish docs and look at what is there. Then decide whether to claim it, and check that nothing in those public collections is out of date, because the site copies them every 24 hours.