Open Source
at Harch.

Sovereign infrastructure demands transparent software.

All our SDKs, tooling, and integrations are open source under Apache 2.0. Audit every line, contribute features, and build with confidence on code you can verify.

Built in the
Open.

Six active open source projects powering the HarchOS ecosystem. Every repository is maintained by our core team with community contributions welcome.

How to
Contribute.

We welcome contributions from developers of all experience levels. Every pull request is reviewed, every issue is triaged, and every contributor is valued.

STEP 01

Find an Issue

Browse issues labeled "good first issue" or "help wanted" across our repositories. We maintain a curated list of beginner-friendly contributions.

STEP 02

Fork & Branch

Fork the repository, create a feature branch from main, and write your code. Follow our code style guide and include tests for new functionality.

STEP 03

Submit a PR

Open a pull request with a clear description of changes. Our maintainers review PRs within 48 hours. All contributions require a CLA signature.

STEP 04

Ship It

After review and approval, your code ships. Contributors are credited in release notes and our annual contributors report. Welcome to the team.

Code of Conduct

We follow the Contributor Covenant Code of Conduct. Harassment, discrimination, and toxic behavior are not tolerated. Be respectful, be constructive, be inclusive.

CLA Agreement

All contributions require a Contributor License Agreement. This protects both contributors and users by ensuring code can be distributed under the Apache 2.0 license.

Style Guide

Each repository includes a style guide and linter configuration. Run make lint before submitting PRs. Automated CI checks enforce consistency.

Our Principles.

Sovereign infrastructure cannot be built behind closed doors. Our open source philosophy is a commitment, not a marketing strategy.

Open by Default

Every feature, bug fix, and architectural decision is discussed in the open. Our roadmap is public. Our issue tracker is public. No hidden priorities — transparency is the default.

Transparent Development

All development happens on GitHub. No internal forks, no private branches. Every commit is visible. RFCs and design docs are published before implementation begins.

Community-First

Community feedback shapes our priorities. Feature requests with strong community support get fast-tracked. Our developer advocates are active daily in Discord and GitHub Discussions.

Star. Fork.
Contribute.

Join 5,000+ developers building the future of sovereign AI infrastructure. Every contribution makes a difference.