Apache 2.0 Licensed

Built in the Open

The core runtime, SDKs, tools, and integrations that power CREW10X are open source. Audit the code, extend the platform, and build with confidence.

18.2K

GitHub Stars

2,400+

Contributors

12

Core Repositories

340K+

Lines of Code

Featured Repositories

The foundational projects that make up the CREW10X ecosystem. All actively maintained and accepting contributions.

crew10x/runtime
Rust

Core Runtime

The high-performance agent execution engine. Handles cognitive loops, memory management, tool orchestration, and multi-agent coordination. Written in Rust for maximum throughput and safety.

12.4K 486 contributors v3.2.0
crew10x/agent-sdk
TypeScript

Agent SDK

The developer toolkit for building cognitive agents. Provides type-safe APIs for agent definition, tool binding, memory systems, and deployment. First-class TypeScript support with full IntelliSense.

3.8K 312 contributors v2.8.1
crew10x/tools
TypeScript

Tool Library

120+ pre-built tool adapters for databases, APIs, file systems, browsers, and external services. Each tool includes schema validation, retry logic, and comprehensive error handling.

1.2K 189 contributors v1.14.0
crew10x/community-agents
TypeScript

Community Agents

Curated collection of production-ready agents built by the community. Research assistants, code reviewers, data analysts, and more. All tested and documented.

820 540 contributors v1.6.2

How to Contribute

Every contribution matters. From fixing a typo to building a new subsystem, here is how to get started.

1

Fork the Repo

Pick a repository, fork it, and clone it locally. Each repo includes a CONTRIBUTING.md with setup instructions.

2

Pick an Issue

Browse issues labeled good-first-issue or help-wanted. Comment to claim it and get guidance from maintainers.

3

Write Tests First

All contributions require tests. Write them before your implementation. CI enforces coverage thresholds on every PR.

4

Submit a PR

Push your branch, open a pull request, and a maintainer will review within 48 hours. Most PRs merge within a week.

Licensing and Governance

Transparent governance and permissive licensing ensure the ecosystem remains open and trustworthy.

Apache 2.0

All core repositories are licensed under Apache 2.0. Use, modify, and distribute freely in commercial and non-commercial projects.

Open Governance

Major decisions go through public RFCs. A steering committee of 7 members (4 community-elected) guides the project direction.

Security Audits

Quarterly third-party security audits with full public disclosure. Responsible disclosure program with bounties up to $10,000.

2026 Roadmap

Where the platform is headed. All roadmap items are tracked as public GitHub issues.

Shipped Q1 2026

Cognitive Mesh v2

Decentralized agent-to-agent communication layer with end-to-end encryption and automatic service discovery across clusters.

In Progress Q2 2026

Agent Marketplace SDK

Publish, discover, and monetize agents through a decentralized marketplace. Includes revenue sharing, versioning, and dependency management.

Planned Q3 2026

Formal Verification Engine

Mathematically prove agent behavior constraints before deployment. Catch safety violations at compile time instead of runtime.

Planned Q4 2026

Multi-Runtime Federation

Connect CREW10X instances across organizations for cross-company agent collaboration with zero-trust security boundaries.

Frequently Asked Questions

Can I use CREW10X open source in commercial products?
Yes. The Apache 2.0 license permits commercial use, modification, and distribution. You can build proprietary products on top of CREW10X without open-sourcing your own code. The only requirement is preserving the copyright notice and license text.
What is the difference between open source and enterprise?
The open source version includes the full runtime, SDK, and tool library. Enterprise adds managed infrastructure, SLA guarantees, custom agent training, SSO/SCIM integration, audit logging, and dedicated support. The core agent execution engine is identical in both.
How do I report a security vulnerability?
Email [email protected] with details. Do not open a public GitHub issue for security vulnerabilities. Our security team responds within 24 hours and follows a 90-day responsible disclosure timeline. Bounties range from $500 to $10,000 depending on severity.
How can my company sponsor open source development?
We accept corporate sponsorships through GitHub Sponsors and the CREW10X Foundation. Sponsors get their logo on the README, priority feature requests, and quarterly meetings with the steering committee. Contact [email protected] for details.

Start Contributing Today

Browse open issues, fork a repository, and submit your first pull request. The community is here to help you get started.

View on GitHub Read the Docs