Open Source
Some parts of what we build belong to everyone.
We open-source the components of ORYN where shared infrastructure benefits the ecosystem more than proprietary advantage would benefit us.
We open-source what we would want open-sourced if we were building on top of ORYN.
There is a category of software where openness creates more value than closure. Developer tooling sits firmly in that category. When the SDK is open, developers can understand exactly what's happening when they call it, contribute fixes rather than filing tickets, and fork it if their needs diverge. Everyone who builds on ORYN benefits.
There is also a category where openness creates less value. The systems that make ORYN reliable — moderation engines, fraud detection, dispatch routing — are valuable partly because they're maintained by a team with full context. Open-sourcing them would distribute responsibility without distributing the context required to exercise it well.
We draw the line accordingly: infrastructure that developers build on is open. Infrastructure that we operate is not.
What's open
Contributing
We maintain these projects and we welcome contributions.
Each repository has a CONTRIBUTING.md that describes the contribution process. The short version: open an issue before writing significant code. This avoids the situation where a well-intentioned pull request arrives after we've already solved the problem a different way.
We review pull requests on a regular cadence — generally within a week for straightforward changes, longer for architectural proposals. We'll tell you if a proposal isn't something we can accept and why, rather than leaving it open indefinitely.
We follow the Contributor Covenant. Contributions are expected to be in good faith. We reserve the right to decline contributions that conflict with our product direction, regardless of technical quality.
Licensing
All open-source components use the MIT License.
MIT is permissive, widely understood, and compatible with most projects. It asks only that you preserve the copyright notice. You can use our open-source components in commercial products, modify them, and redistribute them — with or without changes — without restriction.
We chose MIT over copyleft licenses because we want developers to be able to build commercial tools on ORYN's foundations without legal uncertainty. The benefit of a larger ecosystem outweighs any concern about attribution.