# \[ANN\] Dyad: A New Language to Make Hardware Engineering as Fast as Software

**URL:** <https://discourse.julialang.org/t/ann-dyad-a-new-language-to-make-hardware-engineering-as-fast-as-software/129996>\
**Category:** Package Announcements\
**Tags:** package, announcement, sciml, modelingtoolkit, dyad\
**Created:** [June 18, 2025, 3:08pm UTC](https://discourse.julialang.org/t/ann-dyad-a-new-language-to-make-hardware-engineering-as-fast-as-software/129996 "2025-06-18T15:08:01Z")\
**Posts on this page:** 1\
**Showing post:** 77

<div class="post-metadata">

**Author:** ![gwr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gwr/32/33632_2.png) [@gwr](https://discourse.julialang.org/u/gwr)\
**Post date:** [July 9, 2025, 1:39pm UTC](https://discourse.julialang.org/t/ann-dyad-a-new-language-to-make-hardware-engineering-as-fast-as-software/129996/77 "2025-07-09T13:39:42Z")

</div>

Thank you @michael.tiller, @viralbshah, and @StefanKarpinski for the detailed replies so far. **Two contractual and two deployment questions remain for me.**

#### My use-case and background

I’m the author of the [Business Simulation Library](https://github.com/bslMS/BusinessSimulation) (BSL) for Modelica, which uses acausal connectors for _causal_ system dynamics models in a neat way (@Michael.tiller 's book got me started). Currently, I am working on an extended version called **Acausal System Dynamics** (AcausalSD™), which

- adopts Modelica’s **synchronous-time** framework for discrete behavior,
- offers classes for truly **acausal modeling of economic systems** grounded in a bond graph approach.

My Modelica tool of choice is Wolfram System Modeler, which currently is unique in its support of more flexible units and smart unit checking ([in economic models we need](https://github.com/modelica/ModelicaSpecification/issues/3425) years as a `displayUnit`, discrete counts like `each`, and money as a non-SI-unit.

#### The reality of FOSS monetization

Dual licensing (AGPL-3 + commercial licence) is the only viable way for indie library authors who are **not** in academia.  
I’m happy to pay for tooling the moment corporate users pay for my work, but seat prices that ignore the value a library brings back to the ecosystem feel unbalanced.

#### Vendor lock-in concerns

@StefanKarpinski kindly floated the idea of an **open-source trigger** if JuliaHub ever drops Dyad. That helps, but day-to-day risks remain:

- **Q1** : Can commercial contracts include a **price-cap** clause and block forced tier migrations?
- **Q2** : Will perpetual fallback licenses be offered so we can keep using the last paid version if future pricing becomes prohibitive?

#### Cloud independence & EU data sovereignty

Many EU customers refuse to put their data on servers subject to the US CLOUD Act (for good reason imo).

- **Q3** : Can Dyad Studio and CLI be licensed for **fully offline, air-gapped use**?
- **Q4** : Is an **EU-only JuliaHub region** (operated by an EU-incorporated entity) on the roadmap?

Answers on these four points will help me decide whether I invest in a Dyad seat now or stay on my all-FOSS Modelica → Julia workflow for the moment. Thanks again!

---

_[View the full topic](https://discourse.julialang.org/t/ann-dyad-a-new-language-to-make-hardware-engineering-as-fast-as-software/129996)._