Skip to main content

Accounts & Sign-In

Behavry uses three separate Clerk instances, one per surface:

SurfaceWhat it isAuth instance
docs.behavry.aiThis documentation siteDocs Clerk instance (its own)
demo.behavry.aiHosted demo / sandbox environmentDemo Clerk instance (its own)
Behavry commercial dashboardProduction Behavry tenant for paying customersProduct Clerk instance (its own, tenant-aware)

The three are deliberately isolated. An account on one grants no access to the others — a compromised sign-up flow, a mis-configured webhook, or a confused operator on one instance cannot leak into the others.

Signing in to the docs​

Reading docs.behavry.ai requires a docs account. Creating one takes about 30 seconds:

  1. Visit docs.behavry.ai
  2. Click Sign in on the gate screen
  3. Sign up with email, Google, or Microsoft (whatever the docs Clerk instance exposes)
  4. You land on the docs home

There are no tenants, no organizations, and no plan tiers inside the docs auth layer. A docs account grants read access to the site and nothing else. You can delete it at any time from the Clerk user menu.

One page is deliberately reachable without sign-in: /trust/public-evidence-verification. External verifiers and regulators need to be able to land on it without an account.

Signing in to the demo environment​

Visit demo.behavry.ai and sign up / sign in with that instance's Clerk. Demo accounts are fully separate from docs accounts — you'll create a second credential the first time you visit. The demo environment has its own tenants, its own seed data, and its own sign-up flow; none of it is shared with docs.

Signing in to the commercial dashboard​

The Behavry commercial dashboard uses its own tenant-aware Clerk instance — or OIDC / SAML if your organization is on the Enterprise plan. This is the only surface where Behavry's User Roles & Invites concept applies: viewers, analysts, policy authors, and admins with per-tenant scoping. See User Roles & Invites and Authentication for specifics.

If you're a paying Behavry customer, your commercial-dashboard credentials do not work on the docs or demo sites and vice versa. Sign up separately for each surface you need.

Why three instances instead of one​

Running everything through a single Clerk instance would be simpler operationally, but it ties the surfaces together in ways we deliberately want to avoid:

  • Blast radius — a compromise of one sign-up flow would give an attacker a foothold on all three
  • Sign-up UX — docs should have a frictionless email sign-up; the commercial dashboard needs tenant / org provisioning; the demo needs sandbox-only throwaway accounts. One instance can't do all three cleanly.
  • Data residency — customer accounts on the commercial dashboard fall under different compliance obligations than docs readers. Isolation keeps those obligations from bleeding into the docs Clerk instance.

Forgot password​

Clerk handles password reset natively on every instance. On any sign-in screen, click Forgot password and Clerk will email a reset link. If you're blocked, contact support@behavry.ai with the instance (docs, demo, or commercial) and the email address you used.