← Back to Resources

Governed Integrations Datasheet

Integrations that don't leak authority. Tool-agnostic automation out of the box - Terraform, Ansible, scripts, RPC - plus shipped connectors for ITSM, GitHub, SIEM, vaults, identity and notifications, and signed content packs for AWS, Azure and PingOne Advanced Identity Cloud. Inbound signed and replay-protected, outbound credentials just-in-time, every crossing audited.

Key Highlights

  • ✓Tool-agnostic execution out of the box - Terraform, Ansible, Bash, Python, Java, CLIs and RPC connectors shipped as ready-to-use action packs
  • ✓Signed content packs - AWS, Azure and PingOne Advanced Identity Cloud as native governed actions, signed by LimePoint and unlocked by entitlement; author your own with the MintPress SDK
  • ✓Inbound events signed and replay-protected, executing as named service accounts - never an ambient admin
  • ✓Outbound credentials issued just-in-time, scoped, masked, never persisted - connection secrets write-only once stored, git credentials referenced by name and rotated once for every remote
  • ✓Every crossing audited, with resolutions written back to external systems carrying evidence links to the governed record
  • ✓Shipped connectors - ITSM (Jira Service Management), GitHub (both directions), SIEM (Splunk HEC, syslog/CEF), vaults (OpenBao, HashiCorp Vault, AWS, Azure), identity (OIDC, LDAP), notifications
  • ✓AI model providers brokered by the platform - Anthropic, OpenAI, Azure OpenAI - keys in your custody, never placed on an agent
  • ✓The signed inbound webhook - any system can start a governed run

Most platforms treat integrations as plumbing — and plumbing is where authority leaks: standing credentials in job runners, webhook endpoints that act as admin, resolution scripts nobody audits. OpsChain treats every integration crossing as a governed boundary, and now ships the clouds and the identity platform as signed content packs that run in the same lane.

This datasheet covers the tool-agnostic execution story (the out-of-the-box Terraform, Ansible, script and RPC connectors), the signed content packs — AWS, Azure, PingOne Advanced Identity Cloud and the MintPress SDK, unlocked by entitlement and self-sufficient on a fleet — the shipped connector classes, and the three rules every crossing obeys: inbound events arrive signed and act as named identities, outbound credentials are just-in-time and never persisted (git credentials referenced by name, rotated once for every remote), and every crossing lands in the tamper-evident audit lane.

What you can verify

  • opschain admin packs list shows each pack's signer, version and what references it before a delete can refuse.
  • opschain git-remotes show prints the credential reference, never a value.
  • An unsigned post to /api/hooks/<code> is refused; a signed one lands as external:webhook:received.

Download Governed Integrations Datasheet

Fill in the form below to access this resource.