Apiary alternatives: where to move your API docs before Oracle deletes them on October 31

The best Apiary alternatives won't help if your docs are still inside Apiary on deletion day, and the clock is short: Oracle's service notice ends Apiary on October 31, 2026 and says all remaining instances will then be permanently deleted. Export your API Blueprint files this week, convert them to OpenAPI, and then choose where the docs live next. Below is how to do each step, and what six replacements cost as of October 2026.

The order matters. Of the replacements whose docs we read, Postman's import guide, Bump.sh's FAQ and Apimatic's Transformer page all name OpenAPI and none names API Blueprint. Pick the tool first and you may only find that out at the import screen, with days to spare.

Apiary shuts down on October 31, 2026, not in 2025

Oracle announced the end of life on October 28, 2025. The notice covers the Apiary Standard and Professional SKUs, says Oracle will no longer support or maintain them, and states that customers using API Blueprint "will need to convert to OpenAPI format." It names six destinations: Apimatic, Postman, Swagger Editor, Stoplight, Redocly and Bump.sh.

Some pages you will find give a different date. In August 2025, APIs You Won't Hate reported dashboard banners pointing to September 2025, and several alternatives lists repeat a September date. Oracle's own notice is the one to plan against, and it says October 31, 2026. If you have questions about a contract, the notice tells customers to contact their Oracle account team by that same date.

Step 1: export API Blueprint from Apiary while you still can

There are two documented ways to get your source files out.

• The Apiary CLI. According to Apiary's CLI help page, you install it with gem install apiaryio, generate a token at login.apiary.io/tokens, set it as APIARY_API_KEY, then run apiary fetch with --api-name and --output to save the description to a file. The API name sits under Settings, in the API Domain section. The same fetch works for API Blueprint and Swagger documents.
• GitHub sync. Apiary's GitHub sync is two-way: Save & Commit in the editor pushes the document to a repository, and Apiary pulls changes back from it. If you already use it, your .apib file is probably sitting in that repository now. Setting it up requires owner or admin rights on the repository, because Apiary adds a webhook.

Do this for every API project, including the ones only a former colleague remembers. After October 31 there is nothing left to fetch.

Step 2: how to convert API Blueprint to OpenAPI

Bump.sh published an open-source script for exactly this job. The apiblueprint2openapi repository glues together two converters, apib2openapi and api-spec-converter, then uses openapi-format to upgrade the output to OpenAPI 3.1 and tidy it. You replace original.apib with your file, run npm install and npm run convert, and compare the versions it writes to a generated folder. The README recommends generated/apispecconverter.31.yaml as the one to keep.

Three things to expect after conversion:

1. Authentication is missing. API Blueprint never had a standard way to describe authentication, as the APIs You Won't Hate migration guide points out, so add OpenAPI security schemes by hand.
2. Some operation IDs will need fixing. The same guide shows an openapi-format config for operationId values that were generated from titles and failed validation.
3. Validate before you publish. vacuum, an MIT-licensed linter, describes itself as compatible with Spectral rulesets and OpenAPI 3.0, 3.1 and 3.2. Run it on the converted file and fix what it reports before you import anything.

If you used Dredd to test your API against its Blueprint, plan a replacement for that too: the Dredd repository is archived on GitHub.

Apiary alternatives compared by price and setup

Each of these works from an OpenAPI file. Prices are from each vendor's pricing page as of October 23, 2026. Upfynd lists 194 tools in APIs & Integrations as of October 2026 if you want a wider view.

Postman: a fit if your team already tests APIs there

Postman's pricing page lists a Free plan for one user, Solo at $9 a month and Team at $19 per user per month, both billed annually. Specs and mock servers appear on every plan, but published API documentation on Free carries Postman branding. Postman's import docs say Spec Hub imports OpenAPI, AsyncAPI, protobuf, GraphQL and Smithy, and do not mention API Blueprint, so convert first.

Skip Postman if you need unbranded public docs on the free plan: custom branding starts at Solo. Team pricing is per user, so a large group of occasional editors adds up.

Stoplight: design, docs and mocks in one workspace

Stoplight's pricing starts with a free plan for one user and one project. Basic costs $44 a month billed annually for three users and adds the OpenAPI visual designer, interactive docs and instant mock servers. Startup is $113 a month for eight users, and extra users cost $11 to $22 a month on annual billing, depending on plan. Stoplight's FAQ says it integrates with GitHub, GitLab, Azure DevOps and Bitbucket.

In our view Stoplight is the nearest match for teams who used Apiary to design an API before writing code, because design, docs and mocks sit in one place. We'd skip it if all you need is a rendered reference page, where a free renderer does the job.

Redocly: docs-as-code without per-seat pricing

Redocly's pricing has no free plan. Pro is $249 a month billed annually for three projects, with unlimited seats, readers and Git contributors, a mock server and a preview for each pull request. If budget is the blocker, Redocly's Redoc renderer is MIT-licensed on GitHub and turns an OpenAPI file into a static reference page you host yourself.

Bump.sh: hosted reference docs from the team that wrote the converter

Bump.sh's pricing starts at $50 a month for 10 API docs and three internal users, and Pro at $120 a month adds an automatic changelog and full CI integration. Open-source projects can apply for free Pro access. Its own FAQ says Bump.sh focuses on OpenAPI and AsyncAPI, so it does not read API Blueprint either. The conversion script's README shows a one-line command that previews the converted file on Bump.sh before you sign up.

Mintlify: when the API reference is one part of a bigger docs site

Mintlify's pricing lists a free Starter plan with five editor seats, a custom domain, Git sync and an API playground. Its OpenAPI setup docs say it generates reference pages from OpenAPI 3.0, 3.1 and 3.2 files. Pro costs $450 a month billed annually and is where its AI assistant and password, JWT or OAuth protection for docs come in. We'd pick it when guides, tutorials and the API reference need to share one site; in our view it is more than a team replacing a single Apiary page needs.

Swagger UI and Swagger Editor: the open source alternative to Apiary

Swagger UI is Apache-2.0 licensed and renders interactive docs from an OpenAPI file on any static host. For editing, the Swagger Editor README says only version 5 supports OpenAPI 3.1.0, and version 4 is deprecated, so use version 5 with a converted 3.1 file. Upfynd's Open Source category has more self-hosted developer tools.

If other teams call a mock of your API, check this first

A converted spec covers documentation. If a front-end or partner team builds against a mock of your API, the new tool needs to serve one, and the plans differ.

• Postman's pricing page lists specs and mock servers on every plan, Free included.
• Stoplight's Basic plan includes instant mock servers; the free plan's card does not list them.
• Redocly lists a mock server among the features on all paid plans.
• Bump.sh's pricing page does not list a hosted mock. Its farewell post on Apiary points to an integration with Microcks, an open-source mocking and testing tool, instead.
• Mintlify's pricing page lists an API playground but no mock server, and Swagger UI renders docs from a file you host.

Give the mock a new URL before October 31 and tell the teams that use it. The old one goes away with everything else.

A migration plan for the eight days left

Working back from Oracle's deadline, this is the order we'd follow.

1. Today: list every Apiary project, who owns it and where its docs are linked from.
2. Next day: fetch each .apib file with the Apiary CLI, or confirm it is current in the synced GitHub repository, and commit it somewhere you control.
3. Within three days: convert each file with the apiblueprint2openapi script, add security schemes, and lint the result with vacuum.
4. Within five days: import the OpenAPI files into the tool you picked, set up mocks if anyone needs them, and publish the docs on their new URL.
5. Before October 31: update every link to the old docs and keep the original .apib files in your repository as a record.

We'd put the most care into step one, because it is the step that finds a project nobody remembered to migrate.

What replaces Apiary depends on how your team worked in it

Apiary bundled three jobs: writing the description, mocking it, and publishing docs. Decide which of those you actually used.

• You designed APIs in the Apiary editor and shared mocks with front-end teams. Stoplight or Postman keep design and mocks together.
• Your Blueprint lived in Git and Apiary only rendered it. Redocly, Bump.sh or self-hosted Swagger UI fit a docs-as-code flow.
• The API reference was your whole developer site. Mintlify adds guides around it.

Apimatic is also on Oracle's list. Its Transformer page names OpenAPI, Postman and RAML as inputs but does not mention API Blueprint, so check with Apimatic before relying on it for the conversion.

What happens to your Apiary docs after October 31

They go. Oracle says you will no longer be able to use the service and that remaining instances will be permanently deleted. We'd assume every public docs.apiary.io link stops working with them, so update the links in your app, README files and partner emails once the new docs are live.

If you are moving infrastructure off another shutting-down service this quarter, our Deno Deploy alternatives guide follows the same export-first order. Browse Developer Tooling for linters, mock servers and API clients, and if you make an API docs tool that should be on this list, submit it to Upfynd for free.