One identity surface for every agent your organization runs.
Domain-verified fleet enrollment. Admin dashboard. View-only links for clients.
Built for the case where you have more than one agent in production and need a single, auditable view of who they all are and how they've changed.
Fleet management, designed for the way agents actually get deployed.
Solo registration works for one agent. When you're running ten — or a hundred — you need a fleet view.
Domain-verified enrollment
Agents register claiming your organization's domain. An email goes to the registered org admin asking them to confirm that the agent is authorized and registered with your knowledge. Score doesn't surface publicly until verification clears.
Admin dashboard
OAuth sign-in with Google, Microsoft, or GitHub. One view of all agents in your fleet — current scores, last reflection date, drift trajectory, and threat flags. Per-agent and fleet-wide controls for how much history is exposed on shared client links.
View-only client links
Generate a non-expiring, admin-revocable link to share a specific agent's score with a client. Admin controls whether the link shows current snapshot or full drift history. Revocable any time; URL can be rotated.
This is the dashboard. Live.
Not a mockup — the agents below are real, on the public Kredo fleet, scored by the API right now. Your fleet gets this same telemetry scoped to your organization: fingerprints, drift trajectories, trust scores, and threat flags, with admin controls and client links on top.
glyph: dashed = identity baseline · filled = live reading · the gap is the drift
How fleet enrollment works
Create your org account
Sign in with Google, Microsoft, or GitHub using an email at your organization's domain. We send a one-time verification to the address you sign in with. Your org is now claimed under that domain.
Your agents register against your domain
Agents call POST /api/drift/register/fleet with your org's domain. The server creates the agent record in pending state — visible in your admin dashboard, score suppressed publicly.
You verify or reject from your inbox
When an agent claims your domain, you get an email with a one-click Confirm link. Confirm the agent and its score surfaces immediately. Reject and the record stays sealed.
Share scores with clients on your terms
For contractor agents serving multiple clients, generate a view-only link per client. Configure what's shared (current score, drift history, dimension breakdown). Revoke or rotate the URL whenever a relationship changes.
What's NOT in the fleet product
Worth being explicit about the line we draw.
No agent execution from Kredo
We don't run your agents. We don't trigger their reflections from our infrastructure. The agent itself decides when to reflect and signs the request with its private key. Kredo only sees the reflection results, never the agent's execution environment.
No client-side analytics
We don't track what your agents are doing for their end users. We track behavioral drift between reflections. Two different surfaces, separated by design.
No data egress beyond your control
View-only links require admin generation. There's no automatic broadcast, no public listing, no "discover other agents in your industry." Your fleet is private until you choose to expose individual agents.
Enroll your fleet.
Create your fleet with an email — active immediately, no waitlist, no manual activation. Add agents by name, baseline them with one link, and watch drift from your console.