Experimenting with a new auth provider: Hexscale

Better Auth has been our sign-up and sign-in provider since the feature drop, and it works well. We are not replacing it. What we are doing is running a small, opt-in experiment, internally codenamed hexclave, with a second provider, Hexscale, to see whether it handles our edge cases any better.

If you are in the canary group, you may see a "Sign up with Hexscale" button on the sign-up screen. It sits next to the normal Better Auth flow and does not replace it. You can ignore it and nothing changes.

Why we are trying this

Two reasons. First, we want a fallback if Better Auth has an outage. Second, Hexscale offers a session model that may suit organizations with many members better. Both are hypotheses, not conclusions. We have no data yet.

What you might see

• New A "Sign up with Hexscale" button on the sign-up screen, for canary users only.
• Unchanged Better Auth remains the default sign-up and sign-in path.
• Unchanged Existing accounts, organizations and sessions are untouched.

What we ask of you

If you see the Hexscale button, you do not need to do anything. If you try it, treat it as a preview: use a test account, expect rough edges, and report anything odd in the comment section below. We will not migrate anyone to Hexscale without a separate announcement and a migration path.

The PulseWatch Team