Open Source
Last updated: April 11, 2026
soundOS uses open-source software across its website, dashboard, desktop application, and hosted service components.
This page is a practical summary of that posture for the soundOS product. It is not a full software bill of materials, and it is not a public license grant for proprietary soundOS code.
1. How soundOS uses open-source software
The current soundOS codebase depends on open-source packages, frameworks, SDKs, and libraries for areas such as:
- front-end rendering
- routing and state management
- browser and desktop terminal UI
- hosted worker and edge-service development
- WebSocket and runtime plumbing
- local desktop integration
- testing, build, and developer tooling
Open-source software is part of how soundOS is built and operated, but soundOS itself remains a separately licensed product of SemSwitch, Inc.
2. Representative components in the current codebase
Examples of open-source components visible in the current soundOS repositories include:
- React and React DOM
- React Router
- Zustand
- xterm and related terminal addons
- Wails and related desktop runtime components
- gorilla/websocket
- go-keyring
- modernc/sqlite
- Cloudflare Workers tooling and related packages
- the Deepgram SDK used in the current voice service path
These examples are representative, not exhaustive. Dependency versions and package sets may change over time as soundOS evolves.
3. How third-party licenses apply
Third-party open-source components remain governed by their own license terms.
If an open-source component used in soundOS is licensed under MIT, Apache 2.0, MPL, BSD, ISC, or another applicable license, that license continues to apply to that component according to its terms.
Nothing on this page overrides or narrows the rights or obligations that apply under a third-party open-source license.
If there is ever a conflict between a soundOS agreement and a required open-source license term as to a specific third-party component, the applicable open-source license controls for that component.
4. Proprietary soundOS code and internal orchestration layers
soundOS includes substantial proprietary code and service architecture that are not released as open source by default.
That includes product-specific materials such as:
- soundOS application code
- soundOS design, interface, and product logic
- hosted service composition and product-specific APIs
- proprietary orchestration and session behavior
- internal soundOS integrations that connect to its backend services
Some soundOS service paths also interface with internal T2P-derived session and orchestration components behind the soundOS product. Those internal components should not be read as a public open-source release of soundOS or as a separate third-party notice obligation unless and until we expressly release them under a license.
5. Notices and attribution
Where a third-party license requires attribution, notice text, or other downstream handling, those requirements apply to the relevant component under its own license.
This page is intended to explain the overall posture, not to reproduce every upstream license text inline.
6. No removal of third-party rights notices
You may not remove, obscure, or misrepresent third-party notices or license terms that apply to components distributed with or used by soundOS.
7. Contact
If you have a licensing question related to soundOS and third-party open-source components, contact:
SemSwitch, Inc.
8 The Green, Suite B
Dover, DE 19901
legal@semswitch.com