Sales, SSO questions, and onboarding help.

Contact Us

We’ll help you get set up with scope-friendly workflows, and if you need SSO we’ll align your identity provider with your Supabase OAuth configuration. If you're evaluating ScopeGuard for production use, include your intended signing workflow (freelancer to client vs both sides first) and any SSO provider you plan to federate.

Typically replies within 1–2 business days.

Share on X Share on LinkedIn

Email

The fastest way to reach us:

Support

support@example.com

Email support

What to include

For SSO questions:

Which identity provider you use (Google Workspace, Okta, Azure AD, etc.)
Whether you need OAuth login only or an enterprise SAML-style workflow
Your desired callback / redirect URL

Prefer a quick start? View pricing.

Create an account

ScopeGuard onboarding & production readiness

Contact us to discuss production rollout: environment variables, backend database migrations (Alembic), TLS settings for Azure PostgreSQL, and how JWT verification works server-side. ScopeGuard is built around two trusted boundaries: Supabase Auth for identity, and PostgreSQL + Alembic for business data.

For SSO/OAuth concepts (providers, redirect URL rules, and PKCE), see the Supabase Auth guide.

Signing workflow

OTP + mutual verification

Tell us whether both sides sign in the same session or at separate times; it affects how we recommend OTP exchange UX.

Audit trail

Evidence + hashes

If you want long-term traceability, we can help you align payment-proof storage (R2) and evidence exports with your process.

Environment setup

Dev to prod

We’ll map which env vars belong to the frontend vs backend and how to keep `DATABASE_URL` secrets out of git.