LoopgraphPaper
Preview mode — rich sample data is shown here so you can see the Hermes Brain flow before connecting your own project.
Enterprise security

Provider integrations

Connect company systems through the Hermes Connector Broker without exposing provider credentials to Loopgraph, chat, browser storage, logs, or traces.

Connect a provider

Consent happens at the provider. Tokens go directly to your configured vault; Loopgraph stores only the provider, scopes, health, and an opaque credential reference.

Broker not configured

Provider access

Review consent, granted scopes, health, rotation, and deletion. Every change is written to the tenant audit chain.

No provider credentials are connected to this organization.

Workload identities

Authorize a short-lived Hermes runtime identity separately from provider consent. Each grant is bound to one tenant, environment, capability, and optional connection.

No workload identities are registered.

Emergency policy controls

Stop organization, environment, provider, connection, capability, loop, or agent access locally. Active switches are checked before any vault lookup.

No active kill switches.