Resources · Community

Community

The specification, schemas, SDKs, integrations, and benchmark are Apache-2.0 and developed in the open, in one monorepo. Everything below happens on GitHub or Discord.

Where things happen

Build on the contract

Add an integration

An integration is a plugin: a hook for one surface (agent, gateway, sandbox, or eBPF) built on an SDK — the SDK handles GuardEvent construction, auth, signing, and the wire; the plugin never hand-rolls HTTP. Start from the integrations directory and the closest existing example in the showcase.

Add a detector

A detector accepts a GuardEvent, returns a Verdict, and references categories from the published taxonomy — that's the whole interface. Validate against the JSON Schemas in your test suite, then run the neutral benchmark to see where you land. Detection quality is measured there, not claimed.

Self-certify conformance

Conformance is about speaking the wire, not detection quality, and is currently self-declared: state the version you target and the role you implement (detector, adapter, runtime, …), e.g. "OpenGuardrails v0 — detector + adapter conformant". The roles and their requirements are in CONFORMANCE.md.

Support the mission

Donations keep the protocol and benchmark open, neutral, and Apache-2.0 — never paywalled — and fund the research and integrations behind them.

Donate