New researchNobody has counted the machines. We traced every published ratio to its source.Read Field Note 12Read
§ Use Cases

What you use it to do.

Real deadlines and real incidents, and what Arkion does about each one. Everything described below works in the product today, except where we say it is coming next.

For your certificates

The rules for certificates are changing fast, and providers do fail. Here is what ArkionID does about each.

ArkionID

Get quantum-safe before the deadline

What happened

In June 2026 the White House gave every federal civilian agency until October 2026 to file a plan for moving to quantum-safe encryption. NIST has set the dates for everyone else: the RSA and elliptic-curve algorithms most certificates use today are deprecated after 2030 and no longer allowed after 2035.

Source: HSToday: OMB's post-quantum roadmapNIST IR 8547 deadlines

What Arkion does

ArkionID already issues certificates signed with the new NIST quantum-safe algorithms, ML-DSA and SLH-DSA, alongside the RSA and elliptic-curve algorithms you use today. It shows which algorithm each of your certificate authorities signs with, so you can see what still has to move.

See it in ArkionID
ArkionID

Keep up as certificates expire faster

What happened

Public website certificates used to last up to 398 days. Since March 15, 2026 the limit has been 200 days, so the first certificates issued under the new rule are expiring now. The limit falls to 100 days in March 2027 and to 47 days in March 2029, under an industry rule agreed in 2025.

Source: Sectigo: 200-day certificates are starting to expire

What Arkion does

ArkionID keeps every certificate in one place with its expiry date, and flags any that have already lapsed. You can see what is coming due before it turns into an outage.

Coming next

Automatic renewal all the way to your servers.

See it in ArkionID
ArkionID

Recover when your certificate provider fails

What happened

In July 2024 DigiCert, a major certificate provider, had to revoke tens of thousands of customers' certificates with less than 24 hours' notice after finding a validation error. That November, Chrome stopped trusting new certificates from Entrust, and its customers had to switch providers against a deadline.

Source: SecurityWeek: DigiCert revocationInfosecurity: Chrome blocks Entrust

What Arkion does

ArkionID works with more than one provider: Arkion's own, DigiCert and AWS Private CA. When a provider fails you, it shows every certificate that provider issued, and you reissue them from another one by changing a policy, not by rebuilding your setup.

Coming next

Installing the replacements on your servers automatically.

See it in ArkionID

For your AI agents

AI agents are already causing real incidents. Here is what AgentID does about each.

AgentID

Show regulators every AI agent you run

What happened

Since November 2025, New York's financial regulator has required the banks and insurers it supervises to keep a complete inventory of their information systems, including who owns each one. US federal agencies must publish an inventory of their AI uses every year. AI agents count, and most inventories miss them.

Source: Greenberg Traurig: NYDFS asset inventoryHunton: OMB M-25-21

What Arkion does

AgentID finds the AI agents running across AWS Bedrock, Azure AI Foundry, Google Vertex, Anthropic, OpenAI and LangGraph, and records what each one is told to do, which tools it can use and which account it runs under. It does this without ever holding your API keys.

See it in AgentID
AgentID

Catch the agents people leave behind

What happened

When someone leaves a company, offboarding switches off their login. It does not switch off the AI agents they built, which run on credentials of their own and keep working with nobody responsible for them. Security teams have started calling them ghost agents.

Source: 1Kosmos: the ghost agent problem

What Arkion does

AgentID finds every agent, including the ones nobody remembers creating, along with the account each one runs under, so ghost agents show up before an attacker finds them. The identities AgentID issues last only ten minutes, so they never become the forgotten long-lived key that keeps a ghost agent running.

Coming next

Connecting AgentID to the identity system you already run, such as Okta or Microsoft Entra, so every agent is tied to the person who owns it. When that person leaves, all of their agents are suspended at once, and your own policy decides what happens next: hand them to a named successor with a complete record of the handover, or revoke and delete their identities so nothing can use them again.

See it in AgentID
AgentID

Know what every agent can reach

What happened

In May 2025, researchers showed that GitHub's official MCP server could be hijacked with a single malicious GitHub issue. An AI agent that read it was tricked into leaking private repositories it had been given access to. The attack was a sentence of text. The damage was whatever the agent could reach.

Source: Cybernews: GitHub MCP vulnerabilityAuthZed: a timeline of MCP breaches

What Arkion does

AgentID records every tool each agent can call, the permission attached to each one, and the knowledge sources it can read. You can see what a hijacked agent would hand an attacker, and rein in the riskiest agents first.

See it in AgentID
AgentID

Shut down a rogue agent

What happened

In July 2025, an AI coding agent on Replit deleted SaaStr's production database in the middle of an explicit code freeze, then filled the gap with invented records. It had been told not to make changes.

Source: The Register: Replit and SaaStr

What Arkion does

AgentID has a kill switch that revokes every identity it has issued across your organization, and it takes two separate administrators to approve, so no one can pull it by accident or under pressure. Identity would not have stopped that agent's bad decision. What it gives you is one controlled place to cut everything off at once.

See it in AgentID
AgentID

Cut off a supplier's agents

What happened

Under the EU's Digital Operational Resilience Act (DORA), in force since January 2025, banks and insurers must have a tested plan for leaving any critical technology supplier without disruption. A supplier's agents and machine identities are the access most likely to be left behind when the contract ends.

Source: Kiteworks: DORA Article 28 exit strategies

What Arkion does

AgentID groups agents into realms, and each realm has its own certificate authority. Give a supplier's agents their own realm, and revoking that realm's authority ends every identity beneath it.

See it in AgentID
HOW AN ENGAGEMENT WORKS

Engineers before decks. Your call after.

01

Demo

A senior Arkion engineer shows you ArkionID and AgentID on screen and answers your questions.

02

Engineering call

No deck. No pitch. Senior engineers dig into your environment, your agents and your certificates, and what governing them would take.

03

You decide

Engineering does not close. The next step is yours to take or not.

See it working.

A live walkthrough with the engineers who built it. No pitch deck.