01 Commercial support
Prefer professional assistance to running PegaProx yourself? The companies below provide commercial support, consulting, migration and managed hosting around PegaProx. They are independent providers, listed as part of their sponsorship of the project.
Commercial support for PegaProx — on-site across the Netherlands, Belgium and Germany, and remote across EMEA.
Managed cloud, dedicated & bare-metal servers and colocation, from their Tier IV data centre in Valencia.
Personal IT consulting, managed cloud and infrastructure projects — “we keep IT personal”.
Tailor-made IT — flexible, secure and hands-on: managed services, hosting and infrastructure operations.
Open-source specialists: professional support, consulting and full-lifecycle services around Open Source software.
Does your company offer commercial support for PegaProx? By sponsoring the project you can be listed here with your logo, description, region, languages and website — at no commission.
To be clear about what sponsorship does and does not include: sponsorship — and a sponsored commercial-support listing — provides visibility. Every release, feature and security update is made available to all users simultaneously, free of charge, under the AGPL-3.0. Sponsors and listed companies receive no early access, private builds, earlier security patches, guaranteed response times, exclusive downloads or an "enterprise edition". The build a paying sponsor runs is identical to the one every other user runs.
02 Why sponsor
PegaProx operates on a not-for-profit basis. It is fiscally hosted by the Open Source Collective, and all contributions are reinvested in the work. Sponsorship funds the following:
Sustained security maintenance
Vulnerability triage, coordinated fixes, dependency updates and regular releases require continuous effort. Sponsorship funds the time to carry them out promptly, and the results reach every user — sponsor or not — at the same time.
Cyber Resilience Act support
PegaProx itself is not in scope of the Cyber Resilience Act; many of our users are. Any organisation that incorporates PegaProx into a commercial product is considered a manufacturer and requires supplier inputs from us: SBOMs, a documented security policy, traceable vulnerability handling and clearly defined support periods. We provide these voluntarily so that you can meet your own obligations. This work is ongoing, and sponsorship sustains it.
Visibility
Your logo and name appear on the website, in the README and in the release notes — before an audience of Proxmox VE and XCP-ng operators and teams migrating from VMware. This visibility is the benefit sponsorship provides.
03 Sponsoring tiers
The following are the recurring sponsorship levels available on our Open Collective. Higher levels primarily provide more prominent placement of your logo and name.
- Premium logo placement on pegaprox.com, docs.pegaprox.com and within the software itself
- Everything included in Gold
- Large logo in the README, linked to your website
- Mention in release notes
- Logo in the "Our Sponsors" section on pegaprox.com and docs.pegaprox.com
- Social-media mention
- Prioritised consideration of feature requests
- Medium logo in the README
- Mention in major release notes (e.g. v1.0, v0.9)
- Logo in the "Our Sponsors" section on docs.pegaprox.com
- Small logo in the README, linked to your website
Become a sponsor
Support PegaProx through the Open Source Collective. Spending is fully transparent, one-off and recurring contributions are equally welcome, and company sponsors can be listed with their logo.
Contribute on Open Collective04 FAQ
Only the listing itself — no special rights, no contract and no commission. We do not vet or endorse listed companies, and we receive no share of their revenue. They provide their services independently and at their own account.
No, and this is deliberate. All users run the same build and receive the same releases and security fixes at the same time, free of charge. Sponsorship funds that openness; it does not confer priority. Providing earlier security fixes in exchange for payment would leave every other user less protected, which we will not do.
PegaProx itself is not in scope of the Cyber Resilience Act, so the notion of compliance does not apply to it. What we do provide are the artefacts that commercial users require for their own compliance: SBOMs, a documented security policy, traceable vulnerability handling and clearly defined support periods.
PegaProx is fiscally hosted by the Open Source Collective, a non-profit. The project does not generate profit; contributions fund security work, maintenance and infrastructure. Every transaction is publicly visible on our Open Collective page.
Both. Individuals and companies may support the project through Open Collective. Company sponsors may additionally be listed with their logo at the level corresponding to their contribution.