Kingdom

Your accounts, and who may use them.

Everything you're doing, in one place.

Kingdom holds your accounts, AI logins and agents across every team you're in. A person or an agent reaches one of them only through a Signet you gave them, and you can take it back at once.

Working with Kingdom

Connect an account once, and decide who may use it.

Kingdom is the hosted hub. Your agents work on your machine, and anything they do in GitHub, Slack, Linear or your hosting goes through Kingdom, on a Signet the owner can take back.

  1. Connect each account once. GitHub, Slack, Linear, your hosting and your AI logins. Kingdom keeps the longest-lived credential each provider offers, encrypted, renews it on its own, and never hands it out.
  2. Pair your machines. Foundry and Archive on each computer pair with Kingdom, and you approve each one. A paired machine holds the Signets you give it, and nothing else.
  3. Hand out Signets. A Signet is a pass on your connected accounts with exactly the operations and records you choose, and an expiry or limits if you want them. Give one to a teammate, to the Foundry their agent works in, or to your own other machine.
  4. Take it back at once. Revoking or narrowing a Signet applies to the next request. Every use is recorded against the Signet that allowed it.
  5. Run command-line tools through Kingdom. A command such as gh pr list becomes a call to Kingdom, which runs the real tool with the stored credential and streams the output back, so no token sits on your machine. The client that does this is KCP, the Kingdom CLI Proxy. Signing in to Kingdom with it works today; running commands through Kingdom is in progress.

What it lets you do

  • Let an agent work in GitHub or your hosting without you logging it in, or leaving a token in a file.
  • Give a teammate, or their agent, read access to one project's issues, and end it whenever you choose.
  • Use the same accounts from every machine you own without copying keys between them.
  • Hear about GitHub review requests as they happen, with nothing set up on your machine.
Signets

A pass with exactly the operations you choose.

A Signet names the account, the operations and the records it covers, and can carry an expiry and limits on how much it is used. Revoking or narrowing it applies to the next request. Every use is recorded against the Signet that allowed it.

The holder presents it with a key enrolled on their own machine, so a copied Signet is no use to anyone else. The protocol is the MIT package Signet.

One job each

Credential, token and Signet never stand in for each other.

Credential
What you give Kingdom so it can call a provider for you. It is stored encrypted and never handed out.
Token
A key for Kingdom's own API, capped at a role. It never reaches a connected account, and it cannot create another token.
Signet
The only way a person or an agent uses one of your connected accounts. You choose the operations and records it covers, and you can revoke it at any time.
KCP

Your command-line tools, with no token on your machine.

KCP, the Kingdom CLI Proxy, turns a command such as gh pr list into a call to Kingdom. Kingdom runs the real tool with the stored credential and streams the output back. A Signet names the commands it allows, so a command that would print a token has no operation and cannot run.

Where it stands
  • Signing in to Kingdom with kcp login works today.
  • Running commands through Kingdom is in progress.
  • KCP is MIT.
Where it stands

Hosted at kingdom.inixiative.com, and closed source.

Kingdom started from the template and keeps its sign-in, organizations, permissions and jobs.

Runs today

  • People, organizations and spaces inside them, with members and roles.
  • GitHub, both an organization's app installation and a person's own account, with each repository mapped to a project.
  • Reading Slack channels and messages, and Linear issues.
  • Live GitHub, Slack and Linear events, streamed to whoever holds a Signet for them and is connected at the time. Nothing is stored for later.
  • Automatic renewal of each connected account's sign-in, with its health shown in the dashboard.
  • Claude Code and Codex logins, held for a person and released only to their own Foundry, from a pool per project.
  • Pairing Foundry, Archive and Oracle, with usage recorded against each Signet, person and project, under limits you set.

Not built yet

  • The Slack, Linear and GitHub repository connections are read-only.
  • Notion, Google Drive, Gmail, Jira, Confluence, Microsoft Teams and Discord are planned. Each has an early read-only connection with one or two operations.
  • A Signet goes to a person or to a paired app today. Signets for a whole organization or team are not built.
  • Running commands through KCP is designed and not built.
Kingdom

Where your agents reach your accounts.

Foundry and Archive on your machine pair with Kingdom, and Oracle reads your tickets, threads and pull requests through it. Each of them works on a Signet you can take back.