HAProxy Kubernetes Ingress Controller vs WorkOS

WorkOS shipped a dense two-week window across three fronts. On identity, Agent Registration lets agents sign into AuthKit using the auth.md protocol, treating a non-human caller as a registrable principal rather than a service account borrowed from a human. On integrations, Pipes gained API key support alongside OAuth and then a Token Proxy that calls third-party APIs on a user's behalf without the application ever handling their access token. Separately the company launched Atlas, a Slack-based AI coworker, and shipped a local WorkOS API for CI/CD testing with seeded data, signed webhooks and fault injection.

The through-line is that WorkOS is building the plumbing for software that acts on a user's behalf without inheriting the user's credentials. Agent Registration establishes who the agent is, the Pipes Token Proxy removes the need for the agent's application to hold the token it acts with, and the one-click Claude and ChatGPT plugins put those pieces in reach of the tools people are already using. Atlas points a second way: WorkOS is not only selling this infrastructure but building an end-user product on top of it. The CI/CD testing work is the unglamorous prerequisite for any of it being adopted in regulated environments.

Expect the agent principal from Agent Registration and the token custody in Pipes to converge, so that an agent's registered identity is what scopes which third-party calls the proxy will make for it. Whether WorkOS competes with its own customers via Atlas is the open question these entries do not answer.