One open product.
We commit to keeping every product capability open source. No proprietary enterprise edition and no paid feature tiers.
About / A different starting point
Enterprise capability.
Without exclusion.
OpenSoft was born from a simple conviction: the size of an organisation’s software budget should not decide what it can achieve.
We’re building free and open-source replacements for modern enterprise software, with the ambition to make complete capabilities available to everyone—from a small team starting out to an established enterprise.
Openness makes more than the price accessible. It gives people the ability to inspect, adapt, learn from and improve the systems they depend on.
The OpenSoft commitment
All features. Always open.
Freedom under Apache 2.0.
Use, inspect, modify and redistribute our products under the Apache 2.0 licence. Keep control of how and where you run them.
Revenue from expertise.
We earn revenue through optional consulting, custom engineering and support services. Access to product features is not our business model.
Independence as an outcome.
We aim to make installation, operation and contribution straightforward, so your team can succeed without depending on us.
This is our product and business commitment. Current feature availability and release readiness are documented separately for every project.
Independent implementation
Familiar problems.
Our own foundations.
Our projects implement selected, publicly documented enterprise-software capabilities. We publish the source, compatibility boundaries and development roadmaps so you can evaluate the implementation directly.
OpenSoft is independent of the vendors used for comparison. Our products are developing alternatives; we do not present their current foundations as complete, drop-in equivalents.
Explore the collectionEngineering & security
Trust should have
something behind it.
We separate evidence available today from the controls still being developed. Security is continuous work, not an absolute guarantee.
Automated quality gates.
Product suites exercise real application behavior, persistence and access controls. Exact Java coverage gates and validation records make the scope of testing visible. OpenService also documents browser journeys and a disposable database restore drill.
Read validation evidenceHardening that keeps improving.
Our direction is agent-assisted hardening, repeatable vulnerability reviews and automated penetration testing as release controls. Broader security assessment remains on the roadmap; we do not present planned checks as completed audits.
Read the adoption roadmapBuilt in the open
Your contribution
can move it forward.
Great software improves when more people can participate. Code, tests, documentation, accessibility improvements and precise bug reports are all welcome.
- Find your project.Review the README, implemented scope and roadmap.
- Choose a useful change.Discuss substantial work in an issue before starting.
- Build, test and share.Follow the contribution guide and open a pull request.
A straightforward website.
This website uses no analytics, tracking cookies, external fonts or contact forms. Email links open your email application. Following a GitHub link takes you to a separate service with its own privacy practices. Hosting providers process network requests to deliver and protect the site.
Make it yours
Your software. Your next step.
Explore the code, try a foundation locally, or talk to us about your requirements.