Open Source

Apache 2.0 forever for the authorization control point

IntentGate runs on an open core. The components required to operate it as a security control stay Apache 2.0 in perpetuity. The Pro tier adds enterprise operator experience, not capability gates. Below is the commitment, in writing.

Apache 2.0 · forever
  • intentgate-gateway The authorization control point. Four-check pipeline, capability tokens, multi-tenant scoping, audit chain, webhook emitter, SIEM forwarders.
  • intentgate-extractor Intent classifier (stub + Anthropic Haiku backends).
  • intentgate-sdk-python Agent-side SDK with capability attenuation.
  • intentgate-sdk-typescript Node 18+ SDK, byte-compatible attenuation with the Python SDK.
  • intentgate-helm Kubernetes packaging for the gateway + extractor.
  • intentgate-console Basic operator UI. Full token lifecycle: mint, use, revoke.
Commercial · NetGnarus
  • OIDC SSO + viewer / operator / admin RBAC Sign-in against any OIDC provider with role-based access.
  • SCIM 2.0 provisioning Push from your IdP. Off-boarding flows automatically.
  • TOTP step-up authentication Destructive operations gate behind a fresh code.
  • Per-tenant notification channels Slack, Teams, PagerDuty fan-out from gateway webhooks.
  • JIT admin elevation lifecycle Time-bounded admin with reason, approval, and auto-expiry.
  • /audit/verify dashboard + CSV/NDJSON export One-click chain verification and evidence export.
  • Approvals queue with step-up gating Operator triage of high-risk tool calls.
  • AI-assisted Rego authoring Draft, dry-run, promote, rollback — all in-product.
The rule that will never be broken: anything required to operate IntentGate as an authorization control point stays Apache 2.0. The commercial tier adds enterprise operator experience, not capability gates.

Why this matters

The OSS community is watching where the line gets drawn. So are prospective customers and prospective hires. When a company moves a capability that small deployments depend on into a paid tier — GitLab Premium taking CI/CD, HashiCorp's BSL relicense — they lose the community trust that took years to build.

Our commitment is encoded as a principle, not a list. Six months from now we'll ship a new feature and the question will be "OSS or Pro?" The principle answers it: if a small deployment can't operate without this capability, it's OSS. If it's an operator-experience layer on top, it's Pro.

We'll never relicense the Apache 2.0 components. The commitment lives in GOVERNANCE.md on the gateway repo (publishing soon). Fork freely. Run it in air-gapped environments. Use it as a security control for your own product. The license never changes under you.

Repositories

Core

  • intentgate-gateway

    The authorization service. Go binary. Apache 2.0. ghcr.io/netgnarus/intentgate-gateway:1.6.0

  • intentgate-extractor

    Intent classifier microservice. Python / FastAPI. Apache 2.0.

SDKs & packaging