Open Source (OSS) Policies

All core libraries, frameworks, and specifications distributed under the Prism Suite are 100% free and open-source software, maintained by the Opensource Brewers organization. Everything is licensed under the highly permissive MIT License, ensuring that you have absolute freedom to modify, integrate, and distribute these tools in personal and commercial projects without any vendor lock-in.

🛡️ The Anti-Open-Core Philosophy

We reject the "open-core trap". Critical infrastructure utilities—such as connection proxying, Cedar policy evaluation, rate limiting, and core React streaming hooks—are committed directly to our public MIT-licensed repositories. There are no hidden subscription tiers for operational security.

Community Governance

The Opensource Brewers project is community-led and developer-focused. Technical steering decisions, security updates, and protocol expansions are discussed in public GitHub issues and community meetings. We aim to construct safe, interoperable bridges between LLM backends and user interfaces by collaborating with standard bodies like the Model Context Protocol group.

Contribution Guidelines

We welcome contributions from developers worldwide! To help expand the Prism suite (e.g., adding security transports to the MCP Gateway or building component adapters for the Generative UI framework), please follow this standard workflow:

  1. Fork the relevant project repository on the Opensource Brewers GitHub Org.
  2. Create a clean, descriptive feature branch (`git checkout -b feature/cool-enhancement`).
  3. Implement your changes, adhering to the codebase styling standards (.NET / React TypeScript).
  4. Run local unit test suites and verify compliance.
  5. Open a Pull Request against the `main` branch. Provide detailed context and verification results in the description.

Testing & Conformance

To ensure high resilience across production deployments, all pull requests submitted to Opensource Brewers repositories must pass strict automated validation testing. Any custom database adapters or transport modules must clear the conformance testing suites prior to review approval:

# Run gateway adapter compatibility suite
dotnet test tests/Mcp.Gateway.Adapters.Conformance

# Verify AG-UI protocol conformity
npm run test:conformance

Code of Conduct

Opensource Brewers is committed to providing a welcoming, inclusive, and harassment-free community space. All contributors and maintainers are required to adhere to the Contributor Covenant Code of Conduct in all interactions, issues, discussions, and chat portals. Violations can be reported to our core steering committee.