Until now, the Google and Microsoft buttons could only sign you in to an account that already existed — they could not create one, so every account started life as an email address and a password. Now you can start from the identity you already have.
On the signup page, Sign up with Google and Sign up with Microsoft create your DevStride account without you ever setting a DevStride password. From there you carry on exactly as a password signup does: joining the organization you were invited to, requesting access to one your colleagues have already created, or naming a new one of your own.
DevStride requires a deliverable email address on every account: it is where your notifications go, and it is how your account is matched to invitations and to your organization.
So signing up with a provider goes ahead only when that provider tells us your email address. Most accounts share it automatically; some — particularly guest accounts belonging to another company's directory — do not. When yours does not, signup stops and points you at email-and-password signup instead, rather than creating an account that cannot receive anything.
Enterprise identity providers are not available on the signup page. Joining an organization that uses enterprise SSO still happens by invitation or through that organization's own provider, so a company's membership stays governed by the company.
2026-08-14
Require single sign-on for your whole organization — SSO becomes a policy you can enforce, not just a method you can offer, with guardrails that refuse to let you lock everyone out. Plus a fix for custom fields returning null through the MCP.
2026-08-17
The automated delivery loop we use with DevStride, Claude Code, Codex, and GitHub is now available to every customer as an easy-to-install Claude Code plugin.