Collection Egress Governance

Every collection carries an effective local-only, LAN, or remote policy. One shared evaluator checks serving, inference, publishing, exports, and derived evidence before any transfer, and being authenticated never overrides the collection's own boundary. Existing collections migrate fail-closed: the strictest setting wins until you relax it on purpose.

Install GNO Read the docs

Use cases: Keeping sensitive collections local while sharing others; Fail-closed remote model and publishing decisions; Auditable transport boundaries for agent workflows

What it gives you

Fail-closed local-only migration for existing collections
Conservative loopback, LAN, VPN, proxy, redirect, and remote classification
Independent authentication, authorization, and egress gates
Most-restrictive policy propagation across mixed evidence
Derived Capsules, traces, exports, and records retain source policy
Stable content-free denial reasons across CLI, REST, MCP, SDK, and Web
Bounded local redacted audit receipts with inspect and purge controls
Requests that name their collections are judged on just those, however many you configure; an unscoped request over the limit gets a clean COLLECTION_LIMIT_EXCEEDED denial

Try it yourself

Representative commands and entry points. Full reference lives in the documentation.

gno collection policy get notes

gno collection policy check --action remote_inference --destination remote --content-class passage --collection notes --explain-egress

gno collection policy set notes remote --confirm-relaxation <revision>

gno egress-audit list

Keep reading

Related features and docs.

Privacy first

/features/privacy-first

Open

Collections

/features/collections

Open

Egress configuration

/docs/configuration

Open

Collection limits

/docs/configuration#collection-limits

Open

All features

Back to the feature index

Browse all