Access

What may act in your cloud, and what may act on your behalf. Cloud accounts are the connections Archie deploys, drift-checks and destroys through; API keys are how agents and CI reach Archie itself.

Cloud AccountsNo accounts yet

Save AWS, Azure, or GCP credentials once — devs select them from a dropdown in the deploy form. KMS-encrypted server-side storage.

API KeysNo keys yet

API keys allow CI/CD pipelines to authenticate with the Archie API using Authorization: Bearer archie_... headers.

Connecting an agent?

Point Claude Code, Claude Desktop, Copilot or any MCP client at https://3c83vxcb9g.execute-api.us-east-1.amazonaws.com/mcp and it opens a browser sign-in — no key needed (see Connected agents). Use a key here only for headless callers — CI, scripts, a bot — sent as a Bearer header to the same address. Either way the agent sees only the tools your role allows, and every call is authorised again server-side.

No API keys yet. Create one to integrate with your CI/CD pipeline.