Developers

From contract to traffic, without guessing.

Validate offline, start from one file, take over an existing gateway: everything starts from the OpenAPI or AsyncAPI contract you already write.

The configuration is validated before starting: an error is refused at load time, never discovered in production.

Try it live · Your architecture, its flexway.yaml and its simulated decisions, in the browser.

Start in 5 minutes

In the folder of your flexway.yaml and OpenAPI contract - for instance those of the rest-minimal example:

These commands work from the public opening, when the image is published; until then, try Flexway in your browser. Try it in your browser

Validate the configuration, offline

docker run --rm -v "$PWD:/etc/flexway:ro" ghcr.io/flexwiz/flexway:v1.6.3 validate -v

Start the gateway

docker run --rm --name flexway -p 8080:8080 -p 9090:9090 \
  --add-host=host.docker.internal:host-gateway \
  -v "$PWD:/etc/flexway:ro" \
  ghcr.io/flexwiz/flexway:v1.6.3

Then call an operation declared in your contract: it answers. A route missing from the contract answers 404, as application/problem+json.

Commands from the guide “Serving your first API”, image of release v1.6.3.

Follow the step-by-step guide

The repository's examples

35 complete examples delivered with release v1.6.3.

All releases

Let's talk about your gateway

Flexwiz is a young company: you talk directly with the person who founds it. Tell us what you want to run through Flexway. We talk about your infrastructure and your digital sovereignty requirements.

Talk to an expert Write to Flexwiz

Online booking is coming soon; until then, an e-mail is enough.