Frequently asked questions

It reads your repositories or API descriptions, draws user journeys as flows with one lane per role, builds a mock backend from your code, and runs the flows against that mock or your own environments: by hand, on an interval, and after every deploy. The same flows drive an access audit across roles and tenants and load tests. The product

A flow starts from a catalog of your real endpoints, records and roles rather than from an empty file, and it can be drawn from a plain-language description or a role’s permissions. Each role signs in the way your users do, and the same flow runs against a mock built from your code and against every environment. The access audit and load tests reuse those flows, and monitoring and alerts are built in. When you want test code in your own repository, a flow exports as a Playwright test or a Postman collection. Exports

No. Journey Lanes reads your repositories read-only and adds nothing to them, and it calls your environments over HTTP like any client. Calling the deploy hook from your pipeline is optional, and a relay agent is only needed for environments on a private network.

Engineering and QA teams that want the journeys through their product checked against every environment, including what each role may and may not do. Product owners and testers can build and change flows by clicking, without writing test code.

OpenAPI 3.0 and 3.1, Swagger 2.0, GraphQL schemas and gRPC (.proto files or server reflection), and route code in Express, Elysia, Hono, Fastify, NestJS, Next.js, Symfony and API Platform, Laravel, FastAPI, Django, Rails, Spring Boot, ASP.NET Core and Go routers. Frontend pages are read from React Router, Vue Router, Angular and Next.js. What the scanners read

Yes, through an API description: add an OpenAPI or Swagger document (most frameworks can generate one), a GraphQL schema or .proto files. Steps whose endpoint isn’t in any scanned source are marked, so a flow can’t quietly pass against made-up endpoints.

GitHub, GitLab and Bitbucket, in the cloud or self-managed. Organization owners can connect GitHub through a read-only GitHub App and GitLab.com or Bitbucket Cloud through OAuth where this installation has set those up; every code host also works with a read-only token. Code hosts

Yes. Run the relay agent inside that network: it connects out to Journey Lanes over a WebSocket on port 443, so nothing in your firewall opens, and it only calls the hosts you list. If your firewall allows known addresses instead, allow 88.198.26.110. Relay agent

From 88.198.26.110. Calls to your environments, OpenAPI URLs and code hosts come from this address, so you can add it to an allow list.

OAuth password grant and client credentials, login requests to your own API (with cookies, CSRF tokens and refresh), login pages including single sign-on through SAML, WS-Federation and OIDC form_post, API keys, bearer tokens and HTTP Basic. Presets cover Keycloak, Auth0, Entra ID, Azure AD B2C, AWS Cognito, Supabase, Firebase, Laravel Sanctum, Django and WordPress. Two-factor codes (TOTP, email, SMS from a Twilio test number, fixed codes) and passkeys are supported. Sign-in types

Not unless you allow it. Create, update and assign steps are skipped on an environment until “Allow writes” is on, load tests need their own opt-in, tours never include deletes, and the access audit never sends delete probes to a live environment. Security

On the servers and database of Hetzner Online GmbH, Germany, the hosting provider of this installation. Database backups are encrypted and kept at most 30 days. Error reports go to Sentry in the United States. Every recipient is listed in the privacy policy. Privacy policy

No files are kept from a repository: Journey Lanes keeps what it found in them, such as endpoints, records, roles and page names. “Help me” and “Explain this failure” read the code behind one endpoint from the code host when you use them. An OpenAPI document you upload or point at is stored, so it can be read again.

Passwords, keys, client secrets and two-factor secrets are stored encrypted (AES-GCM) and never sent back to the browser. Sign-in tokens to your environments stay in server memory and are never stored. Run history masks credentials, and from live environments keeps only the shape of each reply unless an owner chooses to keep bodies.

Only what a person asks for. Drawing a flow sends the description and a summary of the scanned sources; “Help me” sends the step, the steps before it and the source files behind its endpoint; “Explain this failure” sends that run’s step result as run history keeps it and the code behind the endpoint, with anything that looks like a credential masked. Anthropic doesn’t use API data to train its models. Explain this failure

No. Platform administrators have no access to projects unless your organization invites them, and people outside a project get “not found”.

Yes. For what you bring in, such as repositories, flows and the replies of your systems, your organization is the controller and Journey Lanes the processor; the data processing agreement and its list of sub-processors are on this site. Data processing agreement

No. A rules engine draws flows from descriptions in English, Dutch and German, and “Help me” and “Explain this failure” have rule-based answers that read what the code declares. Claude handles looser descriptions and reads the code in more depth when it’s available.

Drawing a flow, “Help me” and “Explain this failure” each count as an AI request. Plans include 100 a month on Personal, 500 a month on Team and 2,000 a month on Business. Past the allowance the rules engine answers instead; nothing fails and nothing is charged extra.

Yes. A new organization has Personal free for 30 days, without a card. Choose a plan before it ends to keep running flows.

Every plan has every feature. Plans differ in projects, people, monitored flows and how often they run, and flow runs, load tests and access audits a month, and AI requests. The shortest monitor interval is every 5 minutes on Personal, every minute on Team and every 30 seconds on Business. Pricing

Owners choose a plan in the app and pay through Mollie, monthly or yearly. Every payment gets a VAT invoice by email, also downloadable as PDF. A business in another EU country with a valid VAT number is invoiced with the VAT reverse-charged.

The action is refused with a message saying what was used and when the count starts again. Nothing is charged extra.

Yes. An owner cancels under Organization → Billing and invoices; the plan runs until the end of the period that was paid for and can be resumed until then.

Yes. Prices then include VAT, and you can withdraw within 14 days of first paying for a plan and get back the price minus the days used.

Deleting a flow, project or organization deletes its history at once. Deleting your own account (account menu → Your data) waits 30 days so you can change your mind. Invoices are kept for seven years, as Dutch tax law requires.

Yes. Every flow exports as a flow file that imports again, a Playwright test or a Postman collection, and the account menu → Your data downloads your own account data.