Provider · Auth

WorkOS — Ashlr Stack Provider

WorkOS: Enterprise SSO + Directory Sync. API key verified via GET /organizations. Wire it into your project with one command via Ashlr Stack.

Auth · API key KEY-ONLY · v0.2 adds provisioning

WorkOS — Enterprise SSO + Directory Sync. API key verified via GET /organizations.

Dashboard ↗

One command

Add WorkOS to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add workos

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "drop-in user auth for my app"

Auth flow

Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Find your API key and client ID in the WorkOS dashboard → API Keys.

Secret slots

stack add workos writes these 2 secret slots into your Phantom vault:

WORKOS_API_KEY
WORKOS_CLIENT_ID

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

Auth0 — Identity platform. Domain + M2M client credentials stored in Phantom.
Clerk — Drop-in auth + users. Secret key stored in Phantom.

FAQ

Do I need a WorkOS account to use it with Stack?

Yes — Stack provisions WorkOS on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://dashboard.workos.com and paste it once.

Where does Stack store my WorkOS credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (WORKOS_API_KEY, WORKOS_CLIENT_ID) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove workos` to pull the WorkOS service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying WorkOS credentials in their dashboard — https://dashboard.workos.com — and Stack's next `doctor --fix` will pick up the new values.