Contract flow testing for API teams

See the exact request path before your deploy breaks it.

Flowguard turns a branch, endpoint, and consumer contract into a readable release flow. Senior engineers get a fast answer: safe to ship, needs review, or blocked.

42 ms local diffGitHub check outputSOC 2 audit trail

flowguard trace --branch billing-tax

Selected: OpenAPI diffready

+ POST /v1/invoices accepts tax_region
~ tax_code is now required for export worker
= No response shape drift for mobile clients

Purpose

The homepage starts with the primary job: validate an API change before merge. The command input is the first action, not a decorative signup funnel.

Audience

Platform and product engineers who own public or internal APIs and need credible release checks in pull requests.

Layout

One focused hero with an inspectable flow artifact, followed by proof and implementation guidance. No sidebar dashboard or generic card grid.

Visual system

White working surface, graphite text, quiet borders, and a single teal accent used only for active paths and primary actions.

Proof modules

Credibility comes from concrete interface details: latency, replay count, blocked gate, and check output.

SignalBeforeAfter

Contract regression foundmanual QAin PR

Owner routingSlack guessCODEOWNERS

Release decisionmeetingcheck status

“Flowguard made our API review smaller. We talk about the one broken consumer, not the entire release.”

Marin Valdez, Staff Engineer at Northline

Implementation

The prototype includes selected, hover, disabled, loading, empty, success, and error states. Mobile keeps the trace preview first and stacks the command without hiding the action.

Interaction states

Selected node updates the terminal result.
Run button disables during loading.
Empty endpoint shows dashed empty nodes.
Blocked contract returns an error state.

Responsive behavior

Desktop uses a two-part editorial/product composition.
Tablet stacks preview above copy.
Mobile removes the curve and uses one node per row.

Constraints

No external assets required.
Accessible buttons and form labels.
Static HTML with internal CSS and JavaScript.

Source prompt