Selection criteria
How many active maintainers does the project have, how fast are security holes closed, is there a foundation or company behind it, how good are the docs? We score candidates on these points, not on GitHub stars.
The work spans selection, adaptation and an operating model that does not depend on us.
How many active maintainers does the project have, how fast are security holes closed, is there a foundation or company behind it, how good are the docs? We score candidates on these points, not on GitHub stars.
Some products are free only at the core, with vital features such as single sign-on or audit logs sold separately. We show upfront which parts you can really use for free.
Changes go into plugins, modules or configuration rather than core code. New versions can then be installed without rebuilding your customisations each time.
A list of each component's licence, from MIT and Apache 2.0 through EUPL to GPL and AGPL, flagging when disclosure duties kick in. The legal view is for your lawyer to give.
Automated dependency checks with tools such as Renovate and Trivy, an SBOM for every release and alerts as soon as CERT.at or the project reports a flaw.
On your own servers, with Exoscale in Vienna or another EU provider, in containers with a documented install.
Bug fixes and useful enhancements are submitted upstream. Whatever the project accepts, you never have to maintain yourself again.
From comparison to operation in four steps, with a pilot before the whole workforce moves over.
Two or three open candidates compared with your current solution, including total cost over several years.
An install for one department with real data and real work, and an honest review after a few weeks.
Extensions, sign-in via Entra ID or Active Directory, import of legacy data and training over video.
An update plan, monitoring and documentation that would let another team step in.
Free of charge is not free of maintenance. Open source needs the same security patches as anything else, except nobody turns up to install them for you. Run it without an update plan and within two years you have an outdated system no one remembers how to upgrade. Budget for upkeep from day one.
Project licences largely exclude warranty. That makes the provider who builds and supports your solution all the more important. With us, this runs under a maintenance agreement that sets out response times and responsibilities.
Only in certain cases. Under GPL, duties usually arise when you distribute the software; under AGPL, also when you run it as an online service for others. Purely internal use rarely triggers anything. Our licence list shows the specific spots.
Security depends on how a system is run, not on its licence model. Popular projects are scrutinised heavily, flaws are disclosed openly and fixed quickly. Updates, hardening and access control are what count, and we plan them in as standard.
Yes, that is the whole point. Code, configuration and documentation are in your hands, and any team experienced in the technology will know the projects involved.
Tell us which task needs solving or which product you want to replace. We will show matching open candidates and where their limits lie.
Your enquiry has arrived
Our reply reaches you within one working day. Outages that leave your staff unable to work are dealt with first.
We could not find that town. Try another spelling, or choose whichever provincial capital lies closest; as everything is handled remotely, you get the same service in all nine Austrian states.