← All speakers

Michael Grinich

Conference affiliation: Founder & CEO · WorkOS · 2026

Michael Grinich is the founder and CEO of WorkOS, which turns enterprise requirements such as single sign-on, account provisioning, permissions, and audit logging into APIs for software developers. The business grew from a problem he encountered at Nylas: enthusiastic users could not get an application adopted when it lacked the controls their employers required. His work on AI agents extends that concern to software that chooses services and acts on a person’s behalf: how does it obtain access, whose authority does it carry, and which actions require approval?

On this page

What Nylas taught him about enterprise adoption

Michael studied computer science at MIT and worked in engineering at Dropbox before co-founding Nylas. His interest in email began at MIT, where he experimented with new ways to work with his own mailbox. At Nylas, that interest became an effort to build both better email experiences and infrastructure for developers. He saw email as an enduring connection between organizations, even as tools such as Slack changed communication within them. His early account of Nylas emphasized making that existing communication system easier to build upon.

Nylas Mail exposed an omission in the team’s product thinking. Michael and his colleagues concentrated on the experience of the person using the application, while enterprise IT teams needed security controls and administrative capabilities before approving it. Individual enthusiasm could not resolve those requirements. Nylas shut down the client and shifted toward infrastructure for other software companies.

Michael called this gap the enterprise chasm. His account of founding WorkOS turned the experience into a business proposition: offer single sign-on, directory synchronization, audit logging, and other enterprise capabilities through developer APIs, so each application team would not have to build them independently. WorkOS began building in 2019 and launched publicly the following year.

The move also drew on what Michael had enjoyed at Nylas: building tools for other developers. In his discussion of product and management, he describes looking for a large market where a developer-oriented product could change how companies bought and implemented infrastructure, with Stripe as an important example. His attention to product craft survived the move away from an email client. His minimum awesome product principle asks a new product to make some part of the experience notably impressive before it is feature-complete: a developer’s first encounter may determine whether they return.

In March 2026, Michael announced WorkOS’s $100 million Series C at a $2 billion valuation, naming OpenAI, Anthropic, Cursor, and Perplexity among its customers. The announcement also outlined a focus on secure agentic software, expanding the company’s identity work beyond human users.

Agent identity, registration, and permission to act

Michael’s agent work addresses three related problems: identifying who delegated the work, letting an agent establish an account, and deciding what it may do once connected.

  • Accountable delegation. His writing on agent identity argues for distinguishing an agent from the person who authorizes it. An agent can have its own credentials and a limited subset of the user’s permissions while its actions remain traceable to that user. Handoffs to other agents or services must preserve that connection. Michael advocates verifiable delegation chains and time-limited capability tokens—for example, permission to read one person’s calendar for a bounded period. These are architectural patterns he proposes, rather than capabilities assumed to exist in every agent system.
  • Agent registration through auth.md. Michael argues that agents will increasingly select software vendors themselves, making human signup requirements an obstacle to adoption. Forms, CAPTCHAs, and manually copied credentials can interrupt otherwise autonomous work. WorkOS’s open auth.md project gives services a discoverable Markdown file describing how an agent can authenticate and register. Its reference implementation supports provider-issued identity assertions and a separate claim flow when those assertions are unavailable. In his auth.md demonstration, an agent discovers Cloudflare’s auth.md, proves its identity with ID-JAG, obtains a temporary account, and deploys an application without human signup. The project addresses registration; the service still needs rules governing subsequent access and actions.
  • Intent-based access control. Michael argues that an open-ended assignment cannot always be reduced to a fixed list of permissions before work begins. WorkOS’s Airlock evaluates requested actions at runtime against the task’s intent and applicable policies. It can permit an action, deny it, seek more information, or escalate to a person. The team’s email example makes those distinctions concrete: reading a message may be allowed, sending financial information may be blocked, and contacting an unfamiliar distribution list may require approval. Airlock brokers the underlying credentials, allowing it to mediate requests without handing broad service tokens directly to the agent.

Read the topics behind these talks

2 conference talks

Loading more talks and highlights…

References