SSO / SAML

SAML SSO for signing into Proyecta itself is on the roadmap. For SSO inside the apps you build, ask the AI to integrate any provider.

There are two distinct “SSO” stories that often get conflated. This page covers both.

1. Logging into the Proyecta builder itself

For signing into Proyecta — the builder, the dashboard, your account — Proyecta currently supports:

• Email and password — traditional credential login
• Google OAuth — sign in with a Google account

Email verification, password reset, and the standard account flows are wired up.

SAML / OIDC SSO for Proyecta platform login is planned but not yet available. When it ships, it will cover the standard enterprise providers — Okta, Microsoft Entra ID (Azure AD), Google Workspace, OneLogin, and any SAML 2.0 / OIDC IdP. If your organization needs Proyecta SSO today, contact sales — there may be an early-access path.

2. SSO inside the apps you build

This is a different problem. If you want your end users to sign in via SSO when they use the app you’ve built in Proyecta, you have two options:

Option A: Use Proyecta Auth — built-in authentication with Google and Email OTP out of the box. Microsoft OAuth and SAML/SSO for built-app users are on the roadmap.

Option B: Enterprise SSO (coming soon) — signing your end users in through your own identity provider — SAML 2.0 / OIDC, with SCIM provisioning — is on the roadmap for the platform’s auth. Until it ships, generated apps use Proyecta Auth above; wiring an arbitrary third-party auth SDK into an app isn’t supported, because the build manages auth as a platform capability. If enterprise SSO is a requirement for you, contact us.

Coming soon for Proyecta platform login

• Microsoft OAuth — sign in with a Microsoft account
• SAML 2.0 SSO — bring your own IdP
• OIDC SSO — modern alternative to SAML for newer IdPs
• SCIM provisioning — auto-create and deprovision Proyecta accounts when employees join or leave
• Domain capture — automatically route users from your verified domain into your org’s SSO
• Per-org enforcement — require SSO for everyone in your organization