Enterprise DNA

Instead of Postman

Stop renting Postman. Own your API workbench.

We build your version around the services your business relies on, bring the agreed Postman records across and run the review process with you. Your ownership rules and handover documents stay together.

Postman Team lists US$19 per user per month, billed annually. Enterprise pricing is quoted privately.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Pay for the workflow you actually need

Postman bundles request work with collaboration, monitoring and organisation controls. Team costs US$228 per paid user per year at its annual rate. Compare those needs with an owned inventory and review process before deciding what to replace.

paid

Paid team seats

Team is billed by paid user. Its pricing also includes unlimited workspace and collection viewers, so a viewer is not automatically another paid seat.

groups

A shared workspace

Team includes collaboration and basic access controls. Your custom version needs a clear decision about who reads records and who changes them.

description

Documentation around your requests

Postman lists branded documentation within its paid offering. The owned base produces local handover and review records in your business name.

monitoring

Monitoring alongside manual checks

Postman offers monitoring. The free workbench records individual approved service checks, while scheduled operation is scoped with your managed version.

inventory_2

Enterprise catalogue and workspaces

Postman lists an API catalogue and private and partner workspaces in Enterprise. That plan now needs a sales quote, so use your actual renewal when comparing it.

tune

Features beyond the weekly review

Decide which parts of the wider platform your team uses. The owned version starts with inventory, check evidence, accountable owners and follow-ups.

Your records, your operating rules

Make the Monday review answerable

Ownership

Know who owns each connection

Keep the request inventory beside the person responsible for reviewing it.

  • check Name an owner for each collection
  • check Set the next review date
  • check Find missing owners before handover
  • check Combine accountability with failing and untested checks

Evidence

Keep old results in their proper place

A passing check belongs to the request definition that was tested. Change the definition and it needs fresh evidence.

  • check Keep response status and elapsed time
  • check Separate failures from checks that never ran
  • check Flag results older than the weekly freshness rule
  • check Retain old results without passing a changed request

Follow-through

Give every failure a next action

Link the review to a named action and a due date, then keep the resolution.

  • check Record follow-ups against the collection
  • check Show overdue work beside service evidence
  • check Close actions with a written resolution
  • check Read the change history with its recorded operator

Handover

Leave a useful operating record

Produce branded handovers and review documents from the same database that holds the checks.

  • check Include current request coverage
  • check Bring unresolved actions into the handover
  • check Review transport and deprecated-address warnings
  • check Export the owned records for independent inspection

Make it yours

Design your own Postman replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Postman. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Postman replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Postman data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Three real outputs from fictional demo records: collection coverage, overdue work and failed checks. No customer services were contacted to produce these examples.

forum

API Workbench for Claude Code

Connected to your own database

Which connections have failed, stale or missing checks?

Order integrations

Ner ac
Mere
Tive pa
2
Ssing fa
0
Iling un
1
Tested st
0
Ale
1

Partner integrations

Tive pa
1
Ssing fa
0
Iling un
0
Tested st
1
Ale
0

Ask it anything

Ten questions your owned workbench answers

These questions are backed by the working demo. They are not claims that Postman cannot answer them.

chat_bubble Which collections have failed checks and no accountable owner?
chat_bubble Which current request definitions have never been checked?
chat_bubble Which passing results are too old for our weekly review?
chat_bubble Which requests changed after their last check?
chat_bubble Which hosts still have deprecated requests recorded?
chat_bubble What follow-ups are overdue and who owns each one?
chat_bubble Which collection reviews have missed their due date?
chat_bubble What settings changed and which operator recorded them?
chat_bubble What failed most recently for each active request?
chat_bubble What check evidence and unresolved actions belong in this handover?

Switching

How to switch from Postman

In practice, the move involves exporting a sanitised collection, checking what carries over and validating the agreed workflow alongside Postman before you retire it.

  1. 1

    Export your collections

    Export the Postman collections you want to bring across. The importer supports Postman Collection v2.1 JSON, which carries names, folders, methods and addresses into reviewable records. If your account does not offer that export, check with Postman about the options available to you, often CSV or Excel, before proceeding. Those formats are not listed as supported by this importer.

  2. 2

    Test, then load the records

    Start with a test import and compare its results with the collections you intend to move. When the test matches, load the records into API Workbench. You do not need to make the imported requests work at this stage. The first goal is to bring over the inventory so you can review it, assign owners and decide what needs attention.

  3. 3

    Review every warning

    Check the omissions and warnings before treating an imported request as ready. Authentication, headers, bodies, variables, saved responses and scripts do not migrate as working behaviour. Sensitive query values become unresolved placeholders, and warnings block execution until you add a separately reviewed request. Decide which of these elements matter to your workflow and agree how to handle them before relying on the new records.

  4. 4

    Run both side by side

    Keep Postman available for a short period while you check that the agreed work is covered in API Workbench. The base runs only approved GET and HEAD checks against a host you explicitly name. It does not run authentication, scripts or other imported behaviour. Use the overlap to confirm owners, checks and handover records, and keep any needs outside that scope in Postman until they are addressed.

  5. 5

    Switch off Postman

    Retire Postman only after you have reviewed the flagged omissions, confirmed the workflow you agreed to move is covered and decided what happens to any remaining needs. Make sure each collection has an accountable owner and that the team knows where to review checks and follow-up actions. If authentication, automated monitoring or other testing needs are part of the move, agree their scope before switching off your existing tool.

construction

Where the real effort goes

The main work is usually mapping your own fields and review rules, then deciding which history to bring across. The collection import brings names, folders, methods and addresses, but not the original working behaviour for authentication, scripts or saved responses. Enterprise DNA maps the agreed history and fields as part of your version when you have them run it.

Not ready for a call?

Get your Postman switch plan by email

We will send you the step-by-step plan for moving your business off Postman, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and operates your version

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor
  3. 3 Dry-run a sanitised Postman v2.1 collection export, then import and reconcile
  4. 4 Set owners and expectations, then run approved checks and generate your handover
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your service fields, review rules and handover format
  • check Your Postman records mapped and reconciled
  • check A web front end or different stack when you need one
  • check Authentication, scheduling and advanced checks scoped around your approved services
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your connections and access controls agreed before cutover
  • check Backups and the weekly review kept in the operating plan
  • check A maintained system that changes with your business
Talk through your version

Questions

Instead of Postman, answered

Does this replace every part of Postman? expand_more

The free base handles request inventory, approved read checks, ownership reviews and handover records. Enterprise DNA scopes authentication, automated monitoring and other protocol or testing needs into your version before migration. We agree the full workflow before you retire an existing tool.

What comes across from our Postman export? expand_more

The supported collection export brings names, folders, methods and addresses. Sensitive query values are replaced with unresolved placeholders. Authentication, scripts and saved response examples do not become working behaviour. Omitted components are flagged for review, and Enterprise DNA maps the agreed history as part of your version.

What does Postman cost today? expand_more

Its published Team annual rate is US$19 per paid user per month, equivalent to US$228 per year. Enterprise is privately quoted. Compare your actual seat count and renewal with the work you want us to build and run.

Can a check change our production records? expand_more

The base only runs approved read methods against a host you explicitly name. It does not follow redirects or run imported scripts. Your team still needs to approve the service behaviour before checking it, and Enterprise DNA designs the operational controls for your installed version.

Who looks after the system after the switch? expand_more

Run the free version with your own operator, have us customise it, or have us operate it through Omni by Enterprise DNA. The paid routes use one setup fee, then a retainer. We agree migration, access, backups and ongoing responsibility with you.

Bring the renewal and one service workflow

Book 30 minutes with Sam. Show what you pay for, how your team checks its services and what a good handover needs to contain. We will map the version your business needs and the work involved in running it.

Book 30 minutes with Sam Get the free version

API Workbench for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Postman?

Get your version built