Reliefpay

Release status · In preparation

Open-source release plans

We are preparing the software and operating guides for an open-source release. The current repository is private and no public-source licence is in force yet.

Planned public core

A deployable system

The intended release includes the web and server application, Android shop application, database migrations, card protocol and tooling, tests, and public operating documentation.

Provisional licence

AGPL, after review

The target is AGPL-3.0-or-later for software and CC BY 4.0 for documentation. No licence applies publicly until the reviewed repository and licence files are released.

Hosting and support

Self-host or choose support

Organisations may self-host the released core. ReliefPay can still charge fixed fees for physical cards, supported readers, managed hosting, training and support.

Planned use

Software your team can inspect.

The planned release will let organisations inspect the code, host it themselves and contribute improvements. It will include the application and operating documentation, not just a demo.

What stays private

  • No card keys, signing secrets or production credentials.
  • No beneficiary identities, PINs or transaction records.
  • No private correspondence, partner notes or business files.
  • No permission to imply ReliefPay endorsement or misuse the ReliefPay name and marks.

Before release

What remains to be done

There is no public repository link yet. We will add it here once the licensing, security and publication checks are complete.

  1. 01Prepare the release repository without private business files, generated exports, credentials or deployment secrets.
  2. 02Complete dependency, copyright and licence review, then add the software and documentation licences.
  3. 03Scan for secrets, record the software dependencies, document security risks and verify a build from a fresh copy.
  4. 04Add contribution, governance, support, security-disclosure, code-of-conduct and trademark policies.