CONTRIBUTE

Contribute to AiKey

AiKey is an open-source AI governance workbench. Three ways to join — pick the path that fits your interest and bandwidth.

PATH C · ECOSYSTEM

Ecosystem

Build provider adapters, third-party agent templates, IDE integrations. Extend AiKey, let more tools benefit.

Learn more
PATH B · CODE

Code

Improve AiKey's own code: fix bugs, optimize performance, add features. Rust, Go, or TypeScript.

Learn more
PATH A · USERS

User Community

Use AiKey, report bugs, answer questions, share workflows. Zero barrier — everyone welcome.

Learn more
PATH C · ECOSYSTEM

Ecosystem

AiKey core focuses on credential + usage governance; surrounding capabilities come from the ecosystem. If you want to build plugins, adapters, or integration templates, this is the highest-impact entry point — pre-1.0 contract is still evolving, so early contributors shape the spec.

Good fit for
  • • Building new provider adapters (beyond OpenAI / Anthropic compatible)
  • • Third-party agent onboarding templates (Claude Memory, OpenCode, your own agent)
  • • IDE / editor integrations (VS Code, JetBrains plugins)
  • • New detection capabilities (compliance check, security scanner)
How to start
  1. 1. Read the Third-Party Integration Guide to understand the Vault + Proxy data flow
  2. 2. Open an RFC in Discussions describing what you want to build
  3. 3. Align on contract with maintainers (avoid future breaking changes)
  4. 4. Implement in your repo → apply to be listed in the AiKey ecosystem directory

Impact promise: early ecosystem contributors' design input directly shapes the 1.0 contract. Your plugin gets featured in the main site's "ecosystem" section.

PATH B · CODE

Code

Improve AiKey's own code — fix bugs, optimize, add features. Each repo has a CONTRIBUTING.md with local dev + test instructions.

Repo map

aikey-cli
Rust · CLI + local Vault · main entry repo, recommended for newcomers
aikey-proxy
Go · local API proxy · routing, virtual keys, event capture
aikey-control
Go + React · web console · credential management, usage dashboard
degrade-detector
Python · local daemon for confidence detection
Workflow
  1. 1. Look for good first issue labels (or find your own bug)
  2. 2. Fork → local dev (steps in CONTRIBUTING.md)
  3. 3. Write tests (regression + unit)
  4. 4. Open PR → maintainer reviews within 1 week
SLA commitment
  • • Issue response: within 24h
  • • First PR review: within 1 week
  • • Merged contributions get listed on the site's contributor wall
PATH A · USERS

User Community

Just using AiKey is participation. Report bugs, ask questions, answer others, share workflows — zero barrier, anyone can do it.

How to start
Conversation starters
  • • "Is my usage right? Best-practice question"
  • • "I want to combine X with AiKey, feasibility?"
  • • "Sharing my aikey config / workflow"
  • • "Feature ask: I'd love it if AiKey could do X"

Where to find us

All conversations happen on GitHub Discussions; issues and PRs live in each repo.

GitHub Discussions
Proposals · Q&A · workflows
GitHub Issues
Bug reports · feature requests
Discord
Coming Soon

By contributing you agree to our

Code of Conduct Security Policy CONTRIBUTING