# Fern and Voxgig, compared

> SDKs and a documentation site from one definition. Part of Postman since January 2026. An Apache 2.0 CLI and generator set with a commercial hosted documentation platform on top. Takes OpenAPI, AsyncAPI, gRPC and OpenRPC, or its own definition format, and is the best integrated docs and SDK story in this comparison. Published by Voxgig, which makes one of the two tools. Facts checked 7 September 2026.

**Status.** Postman announced its acquisition of Fern on 8 January 2026. The team joined Postman, and Fern says the product, brand and roadmap continue unchanged. Postman had already acquired liblab, also compared on this site, in November 2025.

## What it is

Fern generates client libraries and a documentation site from one API definition. The CLI and the generators are Apache 2.0 on GitHub, so you can generate SDKs locally without an account. The commercial half is Fern Docs, a hosted documentation platform with custom domains, versioning, search and an interactive API reference wired to the same definition.

The SDK languages are TypeScript, Python, Go, Java, C# and .NET, PHP, Ruby, Swift and Rust. The generated clients carry retries with backoff, automatic pagination, idempotency headers, webhook signature verification, server URL templating and per-language dynamic authentication.

Inputs are unusually broad: OpenAPI for REST and webhooks, AsyncAPI for WebSockets, Protobuf for gRPC, and OpenRPC, alongside the Fern Definition, a definition format of Fern's own that you can author directly instead of hand-maintaining OpenAPI.

Fern says more than two hundred companies use it, and names Square, Auth0, Adobe, Twilio and ElevenLabs among them.

## Facts

- Made by: Fern, part of Postman since January 2026
- Licence: Apache 2.0 CLI and generators. Commercial docs platform
- Source: github.com/fern-api/fern (https://github.com/fern-api/fern)
- Cost: Free to generate. Docs platform paid
- Inputs: OpenAPI, AsyncAPI, gRPC, OpenRPC, Fern Definition

## What Fern does that Voxgig does not

### The documentation site is half the product

Almost every tool in this comparison generates a README and stops. Fern Docs is a real documentation platform: guides beside the API reference, versioned, searchable, on your own domain, generated from the same definition as the SDK so a new endpoint appears in both. Voxgig generates a README and a REFERENCE per SDK and has no hosted docs product. Where the problem is stale documentation rather than the SDK itself, Fern addresses it and Voxgig does not.

### Multi-protocol input

AsyncAPI for WebSocket surfaces and Protobuf for gRPC, alongside REST. Every other tool on this site, Voxgig included, is OpenAPI only. If part of what you ship is a streaming or gRPC interface, being able to generate all of it from one tool rather than two is a structural advantage, not a checkbox.

### A definition format meant to be written by a human

OpenAPI is a description format that a great many teams end up authoring by hand, which is not what it was designed for. The Fern Definition is a smaller, friendlier format you write directly, and Fern emits OpenAPI from it. This removes a class of hand-written-YAML mistakes. The cost is a second source of truth to keep in step with what the server actually serves, which is the cost every intermediate definition layer carries.

### Webhook signature verification, generated

A small feature that is worth naming, because it is the thing integrators most reliably get wrong by hand, and getting it wrong is a security bug rather than an inconvenience. Voxgig does not generate it.

### Open-source generators under a large owner

The generators being Apache 2.0 means the code survives a change of owner. The Postman acquisition adds resources behind it and moves the decision about its direction to a larger company. Which of those weighs more depends on the reader's own risk position.

## Side by side

| | Fern | Voxgig |
| --- | --- | --- |
| Licence | CLI and generators Apache 2.0. Hosted docs platform commercial | MIT throughout |
| Cost | Free to generate locally. Docs platform paid, roughly hundreds per month | Free |
| Inputs | OpenAPI, AsyncAPI, gRPC, OpenRPC, Fern Definition | OpenAPI |
| Language targets | 9 | 22 bundled language targets, more from packages |
| Documentation | A hosted documentation platform | A generated README and REFERENCE per SDK |
| MCP server | No | Yes |
| CLI and REPL over your API | No | Yes |
| Owner | Postman, since January 2026 | Voxgig Ltd, independent since 2018 |

## Choose Fern when

- You want SDKs and a documentation site from one definition and one vendor. It is the clearest reason on this page and it is a good one.
- Your API has WebSocket or gRPC surface as well as REST.
- You would rather author a compact definition format than hand-maintain OpenAPI YAML.
- Being inside Postman is a plus for you: distribution to a very large developer audience, budget behind the roadmap, and an owner that is not going anywhere.

## Choose Voxgig when

- Being inside Postman is a risk for you. Two of the SDK generators in this comparison now have the same owner, and acquisitions change roadmaps whatever the announcement says.
- You need an MCP server, a CLI or a REPL over your API. Fern does not generate them.
- You want the entire toolchain MIT, including the parts that are commercial elsewhere, and generation that runs with no account.
- You need more than the nine languages Fern targets, or you need one it does not have. Voxgig bundles 22 language targets, and adding another is a supported extension rather than a feature request.

## Limits of this comparison

- The product changed owner in January 2026. This page describes what Fern does now and makes no claim about its direction.
- Fern Docs has no Voxgig equivalent, and the comparison table cannot express that asymmetry in a row.
- No documentation site has been built with Fern for this page. The docs platform is described from Fern's own documentation rather than from use.

Corrections go to info@voxgig.com. A correction changes the page and moves its checked date.

## First-party sources

- [buildwithfern.com](https://buildwithfern.com)
- [Fern on GitHub](https://github.com/fern-api/fern)
- [Fern's own announcement of the acquisition](https://buildwithfern.com/post/postman-acquires-fern)
- [Postman's announcement](https://blog.postman.com/postman-acquires-fern/)

## The other comparisons

- [All SDK generator comparisons](https://voxgig.com/sdk/comparisons): the index, the method, and the wider field.
- [OpenAPI Generator](https://voxgig.com/sdk/comparisons/openapi-generator): The community generator most APIs have shipped an SDK from at least once.
- [Speakeasy](https://voxgig.com/sdk/comparisons/speakeasy): Commercial SDK generation with the widest non-SDK output in this comparison.
- [Stainless](https://voxgig.com/sdk/comparisons/stainless): The generator behind many of the best-known AI SDKs. Its hosted product is winding down.
- [APIMatic](https://voxgig.com/sdk/comparisons/apimatic): The longest-running commercial generator here, and the only one that converts between description formats.
- [liblab](https://voxgig.com/sdk/comparisons/liblab): SDK generation shaped as a release pipeline. Part of Postman since November 2025.
- [Kiota](https://voxgig.com/sdk/comparisons/kiota): Microsoft's client generator, built so you do not need a separate SDK per API.
- [Hey API](https://voxgig.com/sdk/comparisons/hey-api): The TypeScript ecosystem's generator. One language, done properly.
- [Voxgig SDK Generator](https://voxgig.com/sdk)