Where is my data stored?

In your browser's localStorage, on your machine. There is no server component; nothing is uploaded unless you explicitly export a file.

What happens if I clear my browser storage?

Workspace state is gone, like deleting a local file. Use Settings → Snapshots to export workspace snapshots and re-import them anywhere. Retention pruning is configurable.

Is this really GDPR-compliant?

Compliance is a property of your process, not of any tool. What we guarantee architecturally: API Workbench Pro transmits none of your API data to us or anyone, which removes the processor relationship most tools force on you. Your DPO will be pleasantly bored.

How do teams collaborate without a cloud?

Today: workspace snapshot export/import and branded artefact exports (gateway bundles, diff reports). On the roadmap: end-to-end-encrypted sync where we still cannot read your data. It ships when it meets that bar.

How is this different from Postman or Bruno?

Postman is a superb client with a mandatory cloud for team features. Bruno keeps requests local but stops at requests. We keep the entire lifecycle — import, design, mock, map, validate, run, govern — local.

Offline-first · EU-built · No backend

The API integration workbench that never phones home.

Q: What is the TMF starter catalogue?

56 TM Forum Open API specifications (TMF620–TMF679 range: Product Ordering, Service Ordering, Trouble Ticket, Customer, Party and more) preloaded for import — an OSS/BSS integration project starts in minutes, not weeks.

Design, mock, map, test and govern your APIs in one keyboard-driven workbench. Every byte of workspace data lives in your browser — there is no server to leak it from.

Open the workbench View pricing

No account. No install. No data leaves the device. Loaded with a demo workspace and 56 TMF Open API specs.

api-workbench-pro — northwind workspace zero egress

Catalog

Explorer

Mappings

Mock Forge

Execution

Gateway

Audit

POST/tmf-api/productOrdering/v4/productOrder200142 ms

schema valid · auth: OAuth2 auto-detected · prevalidation 6/6

Mapping Studio — live preview

order.total→ round(2) →orderTotalPrice.valueapproved

customer.vatId→ upper() →relatedParty[0].id prod

Execution trace

prevalidation — 6 rules3 ms

POST request → staging138 ms

assertions (3)1 ms

Readiness

87%

audit: mapping.approve · a.kovacs · just now

20modules — one lifecycle

56TMF Open API specs preloaded

0bytes of API data sent to any server

devtools — networkverify it yourself

$ Open DevTools → Network.
> Requests carrying your API data: zero.

No backendSub-processors: noneData residency: your browser

The workbench

Eight modules deep, one keyboard away.

Mapped 1:1 to what ships in the app today — nothing on this grid is a mock-up of the future.

Catalog \ ImportImport that audits your specPull OpenAPI/Swagger from file, URL, SwaggerHub or Postman collections. The weakness classifier flags missing enums, absent examples and vague descriptions before they become integration bugs.Import a spec API ExplorerAn explorer that knows your schemaAuth auto-detected from the spec. Requests validated against the schema before they leave. Mock responses per status code, and spec watch that diffs upstream changes.Open Explorer Mapping Studio · ReviewsMapping is a first-class citizenMap fields across APIs with live preview and a transform engine. Reviews gate every change; production locks mean only owners touch what is live.Open Mapping Studio Mock ForgeMocks with a memoryForge mock artefacts per endpoint and status, then drive whole scenarios against them — happy paths, failures, malformed JSON and rate-limit cases included.Forge a mock Prevalidation · ExecutionTraces, not guessesRule-based prevalidation gates the call; the Execution Console records every step as a trace. When a call fails you read the trace, not the tea leaves.Run an execution Gateway SmokeGateway hand-off, smoke-testedExport gateway config as vendor-neutral JSON or Kong declarative YAML, then smoke-test it in place — before a deploy window does it for you.Export config Scheduled RunsRehearsals that keep runningRecurring scenario runs on a cron-style cadence with a notification log. The rehearsal keeps happening after you go home.Schedule a run Audit Log · Schema DiffAudit that writes your evidenceEvery governance action lands in an append-only audit log. Schema-diff impact reports export to PDF for the evidence file.Open the audit log

How it works

Spec to gateway in three moves.

Import

Drop an OpenAPI or Swagger file, or pull from URL, SwaggerHub or a Postman collection. The weakness report scores what you received before you build on it.

Rehearse

Forge mocks, author scenarios from data packs and the error library, map fields across APIs, and run everything with prevalidation and step-by-step traces.

Hand off

Export gateway config as JSON or Kong YAML, smoke-test it, schedule recurring runs and keep the audit trail as review evidence.

GDPR-friendly by architecture

We cannot read your data. That is the feature.

API Workbench Pro has no backend, no accounts and no sync service. The entire workspace — specs, endpoints, mappings, traces, audit log — persists in your browser's local storage. Open DevTools, watch the network tab: your API data generates zero outbound traffic. For GDPR, DORA and vendor-risk reviews, that is not a clause in our DPA. It is an architectural fact you can verify in two minutes.

Read the architecture proof

No backend — nothing to breach
Works offline after first load
Exports happen only when you click Export

TMF / Telco

Every TMF integration project starts two weeks late. Not any more.

56 TM Forum Open API specifications — TMF620–TMF679: Product Ordering, Service Ordering, Trouble Ticket, Customer, Party and more — ship preloaded for import. An OSS/BSS integration starts in minutes, not weeks, and the mapping studio is where the BSS spreadsheets go to retire.

Browse the catalogue

TMF621 Trouble TicketTMF622 Product OrderingTMF629 CustomerTMF632 PartyTMF641 Service Ordering+51 more

Pricing

Pricing that respects your architecture review.

Start free. Pay when your team does. Early access: every tier is free during beta.

Solo

€0forever

The full core, for one engineer.

Compare tiers

Pro

€19per user / month

Every productivity module unlocked.

Compare tiers

TeamMost teams pick this

€45per user / month

Reviews, roles, audit — governance included.

Compare tiers

Enterprise

Customfrom €12k / year

Assurance pack, named support, residency paperwork.

Compare tiers

Full pricing & feature comparison

Early access

We are onboarding five design partners across DACH, Benelux and the Nordics.

Integration consultancies and telco teams get the Team tier free for six months, direct roadmap influence, and an engineer answering the e-mail. In exchange: honest feedback and, after sixty days of real use, the right to ask for your logo.

Apply as a design partner 5 founding seats · one e-mail

FAQ

The questions reviews actually ask.

Engineering answers — the same ones we give your security and procurement teams.