OwnPay

OwnPay has completed its core development phase. The platform is currently undergoing bug fixing and final validation before the Public Beta v0.1.0 release.

The Public Beta v0.1.0 release is coming soon. We do not commit to a specific date — the release will happen when the quality bar is met, not when a calendar says so. Star the repository to get notified the instant it drops.

Because we refuse to release something that isn't secure. OwnPay handles real financial transactions — a rushed release with unresolved vulnerabilities would be a disservice to the community. The additional time is invested in thorough security hardening, bug fixing, and edge case validation. Quality over speed. Always.

OwnPay was architected around very specific requirements that off-the-shelf frameworks don't solve cleanly — primarily around multi-brand domain isolation, a sandboxed plugin execution model, and a domain-specific hook engine. Using a full framework would mean fighting against its conventions rather than leveraging them. The custom foundation gives us full control over the boot pipeline, zero dead code, and a security surface that we own completely. It's more work upfront, and the right call long-term.

Yes. OwnPay welcomes sponsors who align with the open-source mission. If you're interested in supporting the project and gaining visibility in the community, visit ownpay.org/donate or reach out at [email protected].

Yes. Every contribution, however small, helps keep the project moving. Donations go directly toward infrastructure costs, developer time, and security tooling.

The platform is approaching its Public Beta v0.1.0 release. For production deployments, we recommend waiting for the official beta tag, which will include installation documentation, migration tooling, and a full security disclosure report. Star the repository to get notified.