Why everything open source?

The AEC sector is one of the last major industries still running entirely on closed, proprietary software. That brings high licensing costs, vendor lock-in and dependence on a handful of suppliers.

Open source changes that fundamentally:

  • Transparency — anyone can inspect, review and improve the code
  • No licensing costs — professional tools become accessible to any company, large or small
  • No vendor lock-in — your data stays yours, in open formats
  • Faster innovation — the whole community builds along, not a single company
  • Future-proof — software doesn't disappear when a company stops
The gamechanger: agentic coding. With AI-driven software development, intellectual property (IP) in software is no longer a viable revenue model. Code can be written faster and cheaper than ever. The value no longer sits in the code itself, but in the ecosystem, the community and the services around it. Open source is the logical choice for the future.
Will the tools stay free forever?

Yes — all OpenAEC tools stay free and open source, forever. That's not a marketing promise, it's a licensing matter: all tools are licensed under LGPL-3.0. We cannot unilaterally revoke that license. Even if the foundation stops tomorrow or pivots, the current code remains freely available to everyone.

What if development of one of our tools stops?

That can happen — not every tool stays under our active development. But because everything is open source, anyone can take over the project, fork it, or integrate its ideas into their own tool. A nice example is CalcPAD: the open-source variant of that calculation tool was discontinued, and we have integrated a significant part of its ideas into Open Calculations Studio. Open source guarantees that good ideas don't disappear with a company.

No freemium, no surprise paywall, no vendor lock-in. What is free today is free tomorrow. Our revenue comes from services around the ecosystem (see our revenue model) — not from selling licenses.

Isn't AI-written software of poor quality?

We see it differently. We develop all software within OpenAEC using AI coding — not as an experiment, but as a deliberate way of working. That deserves explanation, because it's a new way of developing that still takes some getting used to.

Our position: quality depends on how you check it, not on who writes it. We have a programming background ourselves, but the bulk of what the AI produces we don't understand line-by-line. And that's fine. What matters is whether the result is correct. We steer for that through:

  • Verification calculations — calculation tools (Open Calculations Studio, Open Heatloss Studio) are calibrated against reference examples from standards and handbooks. If something deviates, it's wrong.
  • Visual tests — viewers and graphical tools are compared against screenshots of validated outcomes.
  • Open source as peer review — all our code is public on GitHub. Anyone can read along, find bugs, and submit pull requests.
  • Classical software engineering — tests, builds, deploys, semver versions. Nothing different from a good traditional team.

Traditionally developed software is also dependent on humans, and human errors have been the largest cause of bugs for decades. AI errors are not more dangerous — they're distributed differently. The safety nets above catch both kinds.

"But humans can't maintain the generated code" — today (May 2026) there's still a kernel of truth in that. AI code is not always as readable as hand-written code. But consider where we've come from: at the beginning of 2026 the output was significantly worse than now. Half a year from now we'll see another big step forward, and maintenance will increasingly be done by AI as well — under our direction.

More important than the current level is the direction of the movement. Our position — and it is still debatable today (May 2026) for some — is that within six months to a year AI coding will be not just faster and cheaper, but qualitatively better than what most human developers write today. The direction is unmistakable; only the exact pace varies between estimates.

"What if the AI vendor stops or triples its prices?" — no problem. We are vendor-independent. Anthropic Claude is our current primary choice, but OpenAI, xAI Grok, Google Gemini, Mistral, DeepSeek and Qwen are directly interchangeable. And local models (Llama, Qwen open-weights) run on an ordinary GPU. Even at tripled token prices, AI coding remains more economically attractive than a team of full-time traditional developers.

The conclusion: AI coding is no longer an experiment. Twenty tools, five thousand downloads, supporters using them in production — all built this way. We don't pretend AI coding works without discipline, but discipline is no reason to reject the technique. It's reason to embrace it, with the right safety nets in place.

How do you make money?

For now we are investing heavily to get the full ecosystem working this year. Everything is and will remain open source. You can download it all via our GitHub.

As a foundation we provide services around the ecosystem:

  • Consultancy — advice on implementation, integration and optimization of the tools within your organization
  • Hosting & SLA — managed hosting of the tools with guaranteed uptime and support. Request a quote for example the BIM Validator
  • Extensions & custom development — building extensions to the software for specific client needs. The base stays open source; the extension becomes property of the client or is contributed back to the ecosystem
  • AI assistance on top of the tools (future) — premium AI assistants embedded in the tools: automatic reporting, smart suggestions during calculations, IFC extraction via natural language, batch validation of hundreds of models at once. The tools themselves stay free; the AI layer is an optional paid service for those who want it.
  • Donations — companies and individuals supporting the mission
  • Subsidies — government innovation and digitalization grants for the construction sector
Our prices are typically ~20% below market because no intellectual property (IP) costs are charged. You only pay for the service, not for the software.
Can I host the tools myself?

Absolutely. All tools are open source and can be installed independently on your own server. Most tools offer Docker images for easy deployment. You have full control over your data and infrastructure.

If you'd rather not manage it yourself, we offer managed hosting with an SLA.

What technology are the tools built on?

All tools in the ecosystem are built on the same stack: Tauri 2.0 (Rust backend) with a web frontend. This means every tool runs as a desktop application (Windows, macOS, Linux), as a web app and as a mobile app — from the same codebase.

Read more on our architecture page.

How can I contribute?

There are several ways to contribute:

  • Contribute code — fork a repo on GitHub and submit a pull request
  • Testing & feedback — use the tools and report bugs or suggestions
  • Become a supporter — support the foundation financially via the supporters page
  • Community — join our WhatsApp group