Create an account

Enter your email, verify the one-time code, then register a passkey. Your first API key is created automatically.

If the code does not arrive within a minute, check spam or junk before requesting another one.

Passkey label (optional)

How will your end-users sign in?

This is locked when you create the tenant — switching it later would strand existing end-users whose credentials don't match. Pick carefully.

Email + password

End-users sign up and log in with an email + password. Argon2id at rest.

Email + passkey (with PRF on web)Coming soon

Passkeys replace passwords for end-users. Requires a production domain for native apps.

Tenant-bridged JWTComing soon

You mint JWTs from your own backend; Ease verifies them against your JWKS.

Phone + passwordComing soon

End-users sign up and log in with a phone number + password. Requires a Twilio config.

Phone + passkey (with PRF on web)Coming soon

End-users verify a phone number once via SMS, then register a passkey instead of a password. Requires a Twilio config.

Identity fields collected at signup

These are also locked at tenant creation. End-users will be required to enter the fields you enable.

Usernames

Each end-user picks a unique handle (3–30 chars, letters/digits/_/./-). Available for lookup.

Names

Each end-user enters their name at signup. Editable later.

Primary display

Which field do the SDKs render first in the Contacts and Chat tabs? Options are constrained by the choices above.