The identity and trust infrastructure for autonomous AI agents. Every agent carries a cryptographic passport. Every action is signed. No verification, no trust.
Agents handle money, access databases, deploy code, and make decisions. Nobody can prove who they are or what they did.
API keys prove a human logged in. Nothing proves which agent is making the call or whether it's been tampered with.
UnsolvedAgents spending money with no identity check, no spending limits, no audit trail. One rogue agent drains an account.
UnsolvedIs this agent trustworthy? What's its success rate? No cryptographic, tamper-proof reputation system exists.
UnsolvedAgents go from dev to prod with no vetting, no testing gates, no approval chain. Software has CI/CD. Agents have nothing.
WorkaroundLogs show what happened. They don't prove it. No cryptographic chain linking input to output to agent to timestamp.
UnsolvedAgent goes rogue? Today you scramble to find and revoke API keys across services. No instant, universal revocation exists.
WorkaroundEach subsystem is independently valuable. Together they form the first complete zero trust engine for AI agents.
Every agent goes through a cryptographically sealed pipeline from intake to production. Each stage gate is signed and immutable. Tamper with the code at any stage and the hash chain breaks.
Every action -- payment, tool access, API call -- goes through the Trust Gate. Identity verified, policy enforced, transaction signed and audited. No verification, no access.
Every execution is locally signed and hash-chained. Input hash, output hash, execution hash, signature. Tamper-evident. Offline-verifiable. Your auditor's dream.
The identity layer between agents and MCP tool servers. Before any agent calls a database, file system, or API via MCP, the Trust Gate checks identity, pipeline stage, and trust score. Every interaction logged.
A self-contained, signed JSON document that the agent carries everywhere. Any system can verify it offline -- no server needed. Like SSL certificates, but for AI agents.
Deploy the engine, onboard your agents, verify everything. That's it.
Run the AgentSign engine in your cloud. One Docker image. Your keys, your KMS, your data.
Register agents programmatically. Each agent gets a cryptographic identity and goes through the trust pipeline.
Every action goes through the Trust Gate. Identity checked, policy enforced, execution signed. Full audit trail.
Whether you're governing agents, building them, or auditing them.
Let agents run autonomously. AgentSign provides the guardrails so you don't have to manually approve every action.
One Docker image, one Helm chart. Deploy to any cloud with any KMS. Same engine everywhere.
Zero runtime dependencies. npm install and go. TypeScript definitions included.
Same Docker image everywhere. The only difference is an environment variable.
Try it in 10 seconds. File-based keys, auto-generated. Perfect for development.
docker run -p 8888:8888 \ ghcr.io/razashariff/agentsign
Keys in your AWS, Azure, or GCP KMS. You own the keys. We never see them.
docker run -p 8888:8888 \ -e AGENTSIGN_SIGNER=aws-kms \ -e AWS_KMS_KEY_ID=arn:aws:kms:... \ ghcr.io/razashariff/agentsign
Production-ready Helm chart. PVC, health probes, ingress, TLS.
helm install agentsign \ ./deploy/helm/agentsign \ --set signer=vault \ --set vault.addr=https://v:8200
Zero dependencies. Node >= 18. npm install and write 5 lines of code.
SDK Methods: register · advance · advanceToActive · pay · sign · verify · verifyOutput · getPassport · revoke · cosign · verifyMCP · createWallet · fundWallet · freeze · unfreeze · stripeAction
The EU AI Act is law. NIST AI RMF is the US baseline. Regulators are coming for unverified AI systems. AgentSign was built for this.
The EU AI Act (Regulation 2024/1689) came into force in August 2024, with enforcement beginning February 2025. It is the world's first comprehensive legal framework for AI systems -- and it applies to any AI agent operating within the EU or affecting EU citizens.
Article 9 mandates risk management systems. Article 12 requires automatic logging of AI operations. Article 13 demands transparency. Article 14 requires human oversight mechanisms. Article 15 requires accuracy, robustness, and cybersecurity. High-risk AI systems face the strictest requirements -- and autonomous agents making financial, hiring, or infrastructure decisions are squarely in scope.
Traditional AI governance tools focus on model evaluation and prompt testing. They don't address the identity, provenance, and execution integrity of autonomous agents. AgentSign does.
Every pipeline stage, every execution, every trust score decision is cryptographically recorded. That's not a dashboard metric -- it's evidence.
AgentSign's identity pipeline is a risk management system. Every stage transition, security scan, and approval decision is signed and immutable. The execution ledger provides the automatic logging Article 12 demands -- not just what happened, but cryptographic proof it happened.
ISO 42001 requires documented AI lifecycle management. AgentSign's 6-stage pipeline (INTAKE through ACTIVE) maps directly to the AI lifecycle. Trust scores, execution records, and passport history provide the continuous monitoring ISO 42001 expects.
Signed execution chains, tamper detection, and hardware-backed signing (PKCS#11, CloudHSM) satisfy SOC 2 trust service criteria. On-prem deployment means your audit boundary is your infrastructure -- not a third-party SaaS.
NIST AI 600-1 (AI RMF) calls for governance, mapping, measuring, and managing AI risk. AgentSign's trust scoring (0-100) quantifies agent risk. Pipeline stages map agent maturity. Revocation provides the "manage" control when risk exceeds tolerance.
The engine is free and open source. Enterprise features and support for teams that need them.
All plans include the full AgentSign engine. Your data never leaves your infrastructure. No usage telemetry. No cloud dependency. Patent Pending.
We audited the 12 most popular agent frameworks. None have cryptographic agent identity, execution signing, or trust scoring. 91% of orgs use agents. Less than 10% secure them.
| Framework | Stars | Identity | Signing | Trust Score | MCP Verify | Revocation |
|---|---|---|---|---|---|---|
| AutoGPT | 182K | ✗ | ✗ | ✗ | ✗ | ✗ |
| LangChain / LangGraph | 100K+ | ✗ | ✗ | ✗ | ✗ | ✗ |
| MCP Ecosystem | 80.7K | ✗ | ✗ | ✗ | ✗ | ✗ |
| OpenHands | 64K | ✗ | ✗ | ✗ | ✗ | ✗ |
| Microsoft AutoGen | 50.4K | ~ | ✗ | ✗ | ✗ | ✗ |
| CrewAI | 45.6K | ✗ | ✗ | ✗ | ✗ | ✗ |
| Hugging Face smolagents | 25.5K | ✗ | ✗ | ✗ | ✗ | ✗ |
| OpenAI Agents SDK | 19.4K | ✗ | ✗ | ✗ | ✗ | ✗ |
| Google ADK / Vertex | 15.6K | ~ | ✗ | ✗ | ✗ | ~ |
| NeMo Guardrails | 5.7K | ✗ | ✗ | ✗ | ✗ | ✗ |
| Amazon Bedrock | Managed | ~ | ✗ | ✗ | ✗ | ~ |
| Devin / Cognition AI | Closed | ✗ | ✗ | ✗ | ✗ | ✗ |
| AgentSign | OSS | ✓ | ✓ | ✓ | ✓ | ✓ |
NeMo Guardrails filters what agents say. AgentSign verifies who agents are, what they did, and provides cryptographic proof.
AWS Bedrock and Google Vertex have IAM -- but it's cloud-locked. AgentSign is vendor-neutral, on-prem, and portable across any infrastructure.
A scan of 2,000 MCP servers found all lacking authentication. AgentSign's MCP Trust Layer is the missing verification gate.
✓ = native support ~ = partial (cloud-locked IAM) ✗ = not available Source: GitHub, March 2026. Okta/Strata 2025-2026 research.
The passport system for AI agents. Identity, trust, and proof of every action.
Patent Pending · CyberSecAI Ltd · Zero runtime dependencies · MIT License