Stop rewriting the same backendon every new project.
Auth, Mail, Waitlist, Social and Trawl — five REST APIs behind one account, one API key and typed Node SDKs. Install the parts you keep rebuilding; build the part only you can.
Pick the one that brought you here. The other four are already in your workspace.
One workspace
One workspace. One cookie. One mental model.
Sign in once at auth.productcraft.co and every product trusts the same session. A workspace owns your apps, domains, templates, waitlists, communities, jobs and API keys, and the console shows the same workspace for all five.
restEvery product publishes its OpenAPI document; the API reference and the SDKs render from it.
api_keypcft_live_… keys carry an IAM-style policy — author once, bind to any key.
Claude, Cursor and VS Code can work in your workspace.
An MCP server at mcp.productcraft.co. You approve the connection in the browser, a policy preset caps what it may do, and every call lands in the audit log.
OAuth in the browser — no API key in a config file.
Presets: readonly, mail, support, full. Nothing that escalates privilege is ever in a preset.
Auth now supports WebAuthn passkeys: your end-users can sign in with Face ID, Touch ID, Windows Hello or a hardware key — either as a second factor or on their own, with no password at all. Turn it on per app under App settings → Passkeys.
A new MCP server at mcp.productcraft.co lets an AI client work in a ProductCraft workspace — approved in a browser with no key in a config file, filtered to the permissions you grant, and logged call by call.
End-users get first-class avatars — uploaded via the API or captured automatically from Google/GitHub sign-in — plus the ability to change their own username, all on the Consumer API.