Two ways to pay · every feature

£8 per seat per month, or £50 per seat per year.

Pay yearly and a seat works out at £4.17 a month; pay monthly and cancel whenever. Either way it is everything ReqForge does: requests, collections, environments, scripting, the collection runner, load testing, security scanning and the headless CLI. There is no cheaper tier missing the useful half.

Sold to organisations, in pounds sterling, from one seat upwards. No VAT is charged: we are not VAT registered.

ReqForge for teams

£50 per seat / year

£8 per seat / month

  • Every feature, on macOS, Windows and Linux
  • Seats reassigned as people join and leave, at no charge
  • The same collections in the app and in reqforge-cli
  • Integrations with open-source tools such as k6 for load testing and ZAP for security scanning
  • Collections as plain files in your own git repository
  • Email support, answered by the person who wrote the thing
  • Three weeks of working offline before it has to reach us

No card for the trial. Five seats for fourteen days, then the app goes read-only unless you buy: your collections stay open and exportable, and nothing renews by surprise because nothing was ever charged.

What a seat is

A seat is one named person. It is not a machine, not a login, and not a concurrent-use pool.

One person at a time

A seat belongs to one email address. That person runs ReqForge on one machine at a time, and moving to a new laptop is one press of Deactivate this machine in Defaults → Licence on the old one. If the old machine has already gone, ask us and we release the seat.

Seats come back

When somebody leaves, their seat is released and given to somebody else. You buy the size of your team, not the list of everyone who has ever worked here.

Nothing else is metered

No cap on collections, requests, environments, collection runs, load tests or scans, and no per-project or per-API pricing. The only limit a seat carries is one machine at a time.

The questions that decide it

How do we actually buy it?

In the console. Sign in with your work email (a six-digit code arrives, there is no password), say how many seats you want, and pay on Stripe's own page. The seats are yours as soon as Stripe confirms the payment, and you hand them out from the same console. There is still no card form on this site: card details go to Stripe and never to us. If you would rather have an invoice, ask: ten seats or more, by bank transfer, annually.

How does billing work?

Monthly or yearly, in advance, through Stripe. Card details go to Stripe and never to us, and the subscription renews on the same date each period until you cancel. Add seats at any time and Stripe charges the pro-rated remainder of the current period. Remove seats and the reduction takes effect straight away: unassigned seats go first, and Stripe credits the unused part against your next invoice. Cancelling stops the renewal; what you have paid for runs to the end of its period.

What happens if we cancel?

ReqForge keeps working until the end of the year you have paid for. Cancelling in March does not stop the app in March. After that it goes read-only: collections, environments, history and saved examples all stay open, editable and exportable, and what stops is the six things that put traffic on the wire: sending a request, running a collection, opening a WebSocket or SSE stream, starting the mock server, running a load test, and running a security scan. See refunds and cancellation.

Does it phone home?

For the licence, yes, and for nothing else. Activating a machine sends your email address, a one-way hash identifying that machine, a label for it (the hostname and the operating system), so an administrator can tell one laptop from another, and the app version. After that the app checks in once a day, sending the signed licence it already holds and the app version. It sends no requests you have made, no collections, no URLs and no response data: those never leave your machine. It is all written down in the privacy policy.

What if we work offline?

The licence the app holds is good for seven days, and when it runs out a fourteen-day grace period starts, counted down on a banner in the app. That is three weeks from the last successful check before ReqForge goes read-only, and one moment of network at any point in it resets the whole thing. The fourteen days are set per organisation: if your work is air-gapped for longer than that, say so and we will raise it for you.

Can we run it on a build agent?

Not yet. reqforge-cli runs the same collections headlessly, and list, logs and doctor need no licence at all, but run and diagnose need a licence token bound to the machine they run on, and nothing issues one for a build agent today. It is being built. Say so if CI is the thing that would decide it for you; it changes the order this gets done in.

Can we pay by invoice?

For ten seats or more, yes: bank transfer against an invoice, annually. Ask and you will get a real answer the same day.

Is there a discount for open source or education?

Yes. Free seats for registered charities and for maintainers of open-source projects, and half price for accredited education. Ask, briefly, with a link. You will get a code to enter on the Stripe checkout page; if it covers the whole cost, no card is asked for.

What about a single developer?

One seat is £50 a year, or £8 a month, and buys the same software. There is no free tier: ReqForge is a paid product, and pretending otherwise would mean funding it some other way.