liblab has not shut down. Postman acquired liblab, announced November 14, 2025, and as of September 2026 liblab.com still runs as a standalone product — six SDK languages, active docs (last updated Jul 31, 2026 per its own site), and a working CLI. But liblab's own transition post is explicit that the long-term plan is integration: SDK generation is headed into Postman's platform, not staying a separate product indefinitely. If you're evaluating liblab today, that roadmap uncertainty — not a shutdown — is the reason to also look at alternatives, and the ones below are the real options.
What actually happened
Postman announced the acquisition on November 14, 2025 (confirmed by Postman's press release and liblab's own announcement). liblab founder Sagiv Ofek's post says "nothing is changing for you today" and that existing users "can continue to use the platform exactly as you do now." The stated longer-term vision is different: Postman wants to let users "instantly generate and publish high-quality SDKs... directly from the platform you already live in" — meaning inside Postman itself, not on liblab.com as a separate product. Read that as: liblab is alive and maintained right now, but its identity as a standalone SDK tool has an expiration date that hasn't been announced yet.
What liblab currently offers, verified
Per liblab's own site (fetched September 2026):
- Languages: Python, Java, TypeScript, C#, Go, and PHP, per its SDK generator product page.
- Features: authentication handling (API Key, OAuth, Bearer, Basic, Custom), CI/CD integration via GitHub Actions, auto-publishing to PyPI, Maven, NuGet, Go, Packagist, and npm, plus data validation, error handling, streaming support, and SOC2-relevant audit trails.
- Setup: install the CLI (npm, pnpm, or Homebrew),
liblab init,liblab build— a documented three-step quickstart. - Pricing: its pricing page itemizes only the MCP Generator product — 100 free calls/month for the first year, then $5 per 100 calls. SDK Generator pricing is referenced but not broken out with dollar figures on that page as of this check.
That last point matters if you're budgeting: you can evaluate the SDK generator functionally, but you cannot currently price it from the public page alone.
The alternatives at a glance
| Tool | Best for | Pricing shape |
|---|---|---|
| Stainless | Mature SDK-plus-docs platform, generator-unit pricing | Free tier (≤25 endpoints, 5 generators); paid tiers unpriced |
| Speakeasy | SDK language breadth plus AI/agent governance platform | Free (1 SDK, 50 methods); Enterprise-only, tailored |
| Fern | Docs and SDKs designed together, 9 production languages | Free (forever) + Enterprise only |
| OpenAPI Generator / Kiota | Maximum language coverage, zero vendor cost | Free, open source, no tiers |
| Sourced | OpenAPI to hosted docs + TypeScript/Python SDK preview + managed MCP hosting, one run | Free previews + 2 hosted docs sites + 1 hosted MCP server; Launch $99/mo |
Stainless
Stainless is the closest match to what liblab does today: OpenAPI in, typed SDKs and CI-ready publishing out, plus a docs product. Its free tier caps at 25 endpoints and 5 generators (SDK, docs, or MCP server combined) per stainless.com/pricing — a firm, itemized number, unlike liblab's currently-unpriced SDK Generator. Worth it if you want a platform with a published pricing floor and a roadmap that isn't mid-acquisition.
Speakeasy
Speakeasy covers similar CI/CD-and-publish ground with a broader language matrix, though as of September 2026 its pricing page has shifted to enterprise-only, contact-sales positioning — no self-serve number, similar to liblab's own pricing gap, just for a different reason. Free tier per its SDK docs: one SDK, up to 50 methods. Full comparison in the Speakeasy alternatives post.
Fern
Fern is the pick if docs quality is as important as SDK generation — liblab doesn't produce hosted docs at all today, only SDKs. Fern's pricing is Free (forever) plus Enterprise (custom), and it generates 9 production languages per its quickstart docs, well ahead of liblab's six. Full detail in the Fern alternatives post.
OpenAPI Generator and Kiota
If liblab's appeal was "free, no vendor risk," note that liblab was never actually open source — it's a hosted product now owned by Postman. The genuinely free, zero-acquisition-risk options are OpenAPI Generator (50+ generators, 40+ languages, community-maintained) and Microsoft's Kiota (9 languages). Neither publishes packages or hosts docs for you — see the open-source Stainless alternative post for the full tradeoff.
Sourced
Sourced competes on scope rather than matching liblab's CI/CD publishing automation or six-language breadth: connect GitHub or upload a spec, and one free run produces hosted docs and SDK previews together — the shortest path from OpenAPI spec to live docs and SDK previews — something liblab's SDK generator doesn't produce on its own. Sourced's generated SDKs focus on TypeScript and Python today, the two ecosystems where teams publish first, and it remains one of the last two independent, vendor-neutral hosted SDK-and-docs platforms still standing (see the consolidation table) — a contrast worth weighing now that liblab sits inside Postman. If docs were the missing piece in your liblab setup rather than SDK languages, that's the specific gap Sourced closes.
Honest scope: when staying on liblab still makes sense
If liblab's CI/CD publishing pipeline is already wired into your release process and working, "the company was acquired" is not by itself a reason to rip it out — liblab's own statement is that nothing changes today, and Postman has an obvious incentive to keep existing SDK-generation customers rather than churn them during integration. The real trigger to watch for is a concrete deprecation notice or a forced migration timeline once liblab's SDK generator moves fully into Postman's platform. Until that's announced, treat this as "know your exit," not "migrate now."
FAQ
Did liblab shut down?
No. Postman acquired liblab (announced November 14, 2025), and liblab's own site and product were still live and maintained as of September 2026. This is an acquisition-and-integration story, not a shutdown — contrast with Konfig, which did shut down in December 2024.
Will liblab keep working as a standalone product?
Unclear long-term. liblab's own announcement says existing use is unaffected today, but the stated plan is to fold SDK generation into Postman's platform. No deprecation date has been published as of this check.
What languages does liblab support?
Six, per its own product page: Python, Java, TypeScript, C#, Go, and PHP.
What does liblab's SDK Generator cost?
Not publicly itemized as of September 2026 — only the separate MCP Generator product has published pricing (100 free calls/month in year one, then $5/100 calls) on liblab's pricing page.
Does liblab generate hosted docs?
No — its product is SDK and MCP generation with CI/CD publishing, not a docs platform. Pair it with a separate docs tool, or use a platform like Fern, Stainless, or Sourced that includes docs in the same workflow.
What's the safest first step if I'm worried about liblab's future?
Export what you can verify now — your OpenAPI spec, generation config, and package names — and run the same spec through one alternative as a free preview so you have a working comparison ready if liblab's roadmap changes.
Try it yourself
Create hosted docs from your repo or start free with a direct spec upload — no credit card required. Validate your spec first with the OpenAPI validator, and see the full Stainless alternatives guide for how liblab compares against the wider field.