Integrations — HARP
Where HARP plugs in
A protocol layer between AI agents and execution — integrate at the desktop agent, the mobile approver, or the gateway.
AI agent integration points
Section titled “AI agent integration points”IDE extensions
VS Code, JetBrains, or any editor with agent support. The desktop enforcer wraps every agent action as a HARP artifact.
Agent frameworks
Agents that emit plans, patches, commands, or checkpoints. HARP becomes the last-mile authorization gate.
Mobile approver apps
Custom or white-label mobile apps that decrypt, display, and sign HARP decisions. Your phone becomes the signing authority.
Gateway infrastructure
Zero-knowledge relay services that route encrypted artifacts and decisions without seeing plaintext.
Enterprise integration scenarios
Section titled “Enterprise integration scenarios”Team-level governance
Require senior approval for production deployments. Enforce multi-person review for high-risk operations.
Autonomous operations
AI agents running infrastructure changes, data migrations, or cloud operations — each action requires human sign-off.
Compliance & audit
Every approval is cryptographically verifiable. Audit trails are tamper-evident. Meet regulatory requirements.
DevOps pipelines
Gate deployment steps with HARP approvals. Approve from your phone while the pipeline waits.
Deployment patterns
Section titled “Deployment patterns”Desktop enforcer
On the developer machine, integrated into the IDE. The primary trust boundary.
Sidecar / gateway
In a server context for autonomous agents. Enforces decisions before actions reach production.
Managed relay
Cloud-hosted gateway with device management, push notifications, and tenant isolation.