Why Open Source?

Closed, proprietary systems create dependencies that cost businesses dearly in licences, lock-in, and lost agility. Open source offers a credible alternative across every business function — and the built environment sector has some of the most compelling examples.

No Vendor Lock-in

Open standards and accessible source code mean you are never beholden to a single vendor’s pricing strategy, support policy, or product discontinuation decisions. When Autodesk changes its pricing model or Esri restructures its licence tiers, organisations running open source alternatives are simply unaffected.

Transparency and Auditability

Source code that can be inspected means security vulnerabilities are found faster, compliance requirements are easier to satisfy, and your IT team truly understands what they run. For public sector organisations with obligations around data sovereignty and procurement transparency, this matters considerably.

Total Cost of Ownership

Eliminating per-seat licences, shelfware, and forced upgrade cycles delivers measurable savings. Many organisations halve their software spend when moving to open source equivalents. The savings are not just financial — they include the management time spent on licence negotiations, compliance audits, and vendor contract renewals.

Community and Longevity

Mature open source projects like Linux, PostgreSQL, QGIS, and LibreOffice have outlasted countless proprietary competitors because communities, not shareholders, drive their development. There is no risk of the product being discontinued, sold, or sunset — the code exists independently of any single commercial entity.

Customisation and Integration

Access to source code enables bespoke adaptation and deep integration with existing workflows — something that is simply impossible with black-box proprietary systems. This is particularly valuable in the built environment, where workflows are often highly specific to an organisation’s processes and data standards.

The Public Sector Dimension

UK Government policy has long encouraged the use of open standards and open source software in public procurement. The Technology Code of Practice explicitly states that public sector organisations should consider open source solutions. Despite this, proprietary software remains dominant in many local authority technology estates — often because of procurement inertia and the perceived switching costs of migration.