Coming 2027

Test the chain, not just the call.

Luvin turns your OpenAPI and AsyncAPI contracts into visual API workflows, writes the Arazzo for you and tests every step of the chain, against your API or in simulation.

Local-first. No account. Nothing leaves your machine.

Built on open standards

  • Arazzo 1.0 · 1.1
  • OpenAPI 3.x
  • AsyncAPI 2.x · 3.x
  • HTTP · GraphQL · gRPC · WebSocket
  • macOS · Windows · Web
  • English · Español

The problem

Stop calling A to test B.

A single screen of your app usually depends on several APIs called in order. Log in on A to get a token, call B with it to get the customer, call C with the customer’s id. To test C, you call A and B by hand and copy values between responses. Every time. And nobody can quickly say which APIs that screen depends on, or how the data moves between them.

Today you call A, copy the token, call B, copy the id and call C by hand. With Luvin the workflow runs the whole chain and passes the data.

Luvin removes those manual calls and makes your integrations visible.

How it works

From API requests to complete API workflows.

  1. 1

    Bring your contracts

    Add the OpenAPI and AsyncAPI files of the APIs involved, or import your Postman and Bruno collections.

  2. 2

    Draw the workflow

    Drag operations onto a canvas. Tokens, ids and fields are wired between steps by rules, no AI involved.

  3. 3

    Get the Arazzo

    The canvas writes a standard Arazzo file, validated against the contracts as it changes.

  4. 4

    Test the chain

    Run generated and custom cases against the real API or in simulation, with verdicts in plain words.

01

Draw it once

Each operation you drop becomes a step. A customerId connects to the id returned by “create customer”, and anything nobody feeds becomes an input of the workflow. Drag the data lines to rewire them.

02

Test the whole chain

Happy path, invalid inputs, calls without credentials and every documented error path, generated from the contracts. Choose the status each rejection must return, run them all and read the verdict in plain words.

03

The Arazzo stays yours

The canvas edits a real Arazzo file and keeps anything written by hand. The YAML validates as you type, underlines each problem on the exact value and autocompletes operations, outputs and inputs.

The Arazzo editor with live validation and autocomplete

Real chains

Built for chains as they really are.

Real integrations return lists, depend on other workflows and fail halfway. Luvin runs all of it, the way the Arazzo standard describes it.

When a step returns a list

Choose what the next call gets

The run pauses and shows what came back. Pick one item, several, or send the whole list: what you can choose follows the design, and Luvin remembers it for the next steps.

Workflows on workflows

Reuse what already works

Log in once and reuse it. A workflow can depend on another, call one as a step and use its outputs, even from another Arazzo file.

A workflow that depends on another one and uses its outputs in the diagram

The whole standard runs

Success and failure actions, retries with their wait and limit, jumps to a step or to another workflow. Arazzo 1.0 and 1.1.

No API? Simulate it

Every step answers from the contract’s examples, so you can try a chain before the API exists.

REST and events

Mix HTTP calls with AsyncAPI send and receive steps, matched by correlationId, in the same workflow.

Contract changes, caught

Edit a contract and Luvin tells you which workflows the change breaks, before you run them.

Also an API client

And for the single call, everything you expect.

When one step fails you need to look at it on its own. Requests, collections and Dev Tools sit right next to your workflows.

  • HTTP, GraphQL, gRPC and WebSocket

    Params kept in sync with the URL, automatic headers, cookies, saved examples, and timing and size for every response.

  • Bring what you have

    Import Postman and Bruno collections with their folders and environments, paste a cURL, or generate every request from an OpenAPI contract.

  • Collections with docs

    Each collection gets an overview with its workflows, last runs and contracts, plus documentation generated from them.

  • Dev Tools

    Console, Network with “Copy as cURL” (secrets masked), Performance and a terminal.

Importing a Postman collectionA request with its response, next to the collection tree

Authorization, per API or per workflow

  • OAuth 2.0 + PKCE
  • OAuth 1.0
  • AWS Sig v4
  • API Key
  • Bearer
  • Basic
  • Digest
  • NTLM
  • WSSE
  • Akamai EdgeGrid

Compare

Keep your API client for single requests. Use Luvin for the chain.

API clients are great at single requests, and all of them can chain calls. The difference is what it takes to build the chain, see it and prove it works.

—LuvinPostmanBrunoInsomnia
Built aroundWorkflows across several APIsSingle requests and collectionsSingle requests and collectionsSingle requests and collections
Passing data between callsWired automatically from the contractsScripts or a FlowScripts (bru.setVar)Response template tags
Seeing how data flowsA diagram of every API, step and fieldRead the scripts, or build a FlowRead the scriptsOpen each request’s tags
Negative casesGenerated from the contractTest scripts you writeTest scripts you writeTest scripts you write
What you keepArazzo, an open standardA Postman collectionBruno files in gitAn Insomnia export

What about Postman Flows?

Postman Flows gives you a canvas to build a chain. Luvin reads your contracts, builds the chain and tells you if it works.

See the full comparison →

Based on each product’s public documentation as of November 2026. Postman, Postman Flows, Bruno and Insomnia are trademarks of their respective owners; Luvin is not affiliated with them.

Features

Everything the chain needs, in one place.

No more manual chains

Luvin calls every API in order, passing tokens, ids and any field from one step to the next.

See your integrations

Every workflow is a diagram: which APIs take part, in what order, and which field feeds which parameter.

Cases for free

Happy path, missing or invalid inputs, calls without credentials and one case per success or failure action.

Failures in plain words

“status is INACTIVE but ACTIVE was expected”, with the step and field highlighted.

A report to share

Export the results of a run as a self-contained HTML report that anyone can open.

Test data on tap

47 generators with the same names as in Postman, like {{$randomEmail}}, plus your own data cases.

Environments and secrets

Base URLs, variables and credentials per environment. Secrets are stored encrypted on your computer, never in the files.

Simple for everyone

A simple interface for people who only run workflows, a guided tour and ready-to-run examples.

Local and in git

No backend, no account. A workspace is a folder of plain files you review in a pull request.

Who it’s for

For teams whose apps depend on chains of APIs.

Integration and QA engineers

Who test chains of API calls by hand today and want generated negative cases and clear verdicts.

API product and partner teams

Who need to show that workflows across several APIs work end to end, with a report to share.

Product managers

Who want to try a workflow with their own data in a simple interface, without test code.

API designers

Who want to see how their APIs connect and validate workflows before anything is built.

FAQ

Questions, answered.

When can I use Luvin?

Luvin launches in 2027. Join the waitlist for early access and an invitation to the first pilots.

Do I need OpenAPI contracts?

No. Import your Postman or Bruno collections, or paste a cURL, and drag those requests onto the canvas: Luvin learns each response on the first run and suggests the wiring. With contracts you also get wiring by rules, generated negative cases and simulation.

What is Arazzo?

The OpenAPI Initiative’s open standard for describing sequences of API calls. Luvin writes it for you and runs it, versions 1.0 and 1.1. The files are yours: keep them in git and run them with any Arazzo tool.

Does my data leave my computer?

No. There is no backend and no account: requests go straight from your computer to your APIs, and secrets are stored encrypted on your machine.

Where does it run?

As a desktop app for macOS and Windows. Everything runs on your computer: there is no backend and no account.

Does it replace my CI or run integrations in production?

No. Luvin is for designing, debugging and demonstrating chains of APIs. The Arazzo files it writes are what you take to CI, with any Arazzo runner.

Does it use AI to wire the steps?

No. Wiring follows rules over your contracts, so the same contracts always give the same result, and anything uncertain is marked for you to review.

Coming 2027

Be the first to test the chain.

Luvin launches in 2027. Join the waitlist for early access and the first pilots.

We’ll only use your details to tell you about Luvin. No spam.