The RFPlex.ai source code is currently available for review on request — email [email protected] with your organisation name and intended use. A public release under the Business Source License 1.1 (BSL 1.1) is planned. Under that licence, anyone will be able to read, modify, self-host and redistribute the source code for non-production use — development, testing, evaluation, security audit, academic research and personal study — without paying anything.
Production use of any kind will require a commercial licence. "Production use" covers any use of RFPlex.ai whose outcome affects a real commercial transaction or business relationship — including running it internally inside your own organisation to respond to RFPs you have received.
The source-available model keeps the code transparent and auditable (so your security team, procurement and regulators can read and verify it) while giving the project a sustainable revenue stream from the companies that derive commercial value from it.
Each released version of RFPlex.ai automatically converts to the Apache License
2.0 four years after release (Change Date 2030-05-13 for the current
version). After that date, the version in question becomes fully permissive open-source
software with no commercial restrictions whatsoever — so commercial licensees are protected
against vendor lock-in long-term.
You need one if you intend to use RFPlex.ai (or any derivative work) for any of the following:
You do not need a commercial licence to:
Email [email protected] with:
You will receive a quote and a draft commercial licence agreement, typically within 2–3 working days.
We aim to keep pricing transparent and aligned with the value RFPlex.ai delivers (every successful RFP win is worth orders of magnitude more than the licence fee). Final pricing depends on scale, deployment, and support requirements.
| Tier | Use case | From |
|---|---|---|
| Single team | One sales/presales/bid team, ≤10 seats, internal use | €1,200/yr |
| Department | Multiple teams within one organisation, ≤50 seats | €4,800/yr |
| Enterprise | Org-wide deployment, unlimited seats, SLA-backed support | from €18k/yr |
| OEM / embed | Embedding RFPlex.ai source or binaries in your own product | bespoke |
| Hosted re-sale | Offering RFPlex.ai as a service to your own customers | bespoke |
The above are indicative — every commercial licence is bespoke. Public-sector, academic and registered-charity rates are available on request.
Yes — non-production evaluation is unrestricted under the BSL 1.1 itself. Read the source, run it on your own hardware, point it at sample RFPs, get your security team to audit it. No commercial licence required during evaluation.
The version in question converts automatically to Apache License 2.0 — fully permissive open source, no commercial restrictions. You get a guaranteed escape hatch even if RFPlex.ai as a company ceases to exist. New versions released after the Change Date will have their own four-year BSL 1.1 window.
Welcome and encouraged. Contributors sign off via the Developer Certificate of Origin (DCO) and grant the project the right to relicense their contributions, which means contributing to RFPlex.ai does not itself require a commercial licence.
Often yes — if you can use the hosted service at rfplex.ai under the published Terms of Service, you do not need a code licence at all. The code licence is for organisations that need to self-host the source code.
Email [email protected] — there is no penalty for coming forward and regularising. We would much rather have you as a paying customer than a defendant.
This page is informational and does not itself constitute a commercial licence. The legally binding commercial licence agreement is a separate document countersigned by both parties.