Simple, Scalable Pricing

A user is considered active when they authenticate or perform a token refresh with Wristband at least once in a given month.

A tenant is considered active when there is at least one active user within that tenant in a given month.

A machine is any OAuth2 Client in Wristband that generates at least one access token using the Client Credentials grant type at least once in a given month.

A tenant is a grouping of users who have access to a common set of data, configurations, and security settings. Each tenant has its own unique set of data, configurations, and security settings, which are isolated from other tenants, but they share the underlying infrastructure and resources, such as the database and server. Typically for B2B applications, tenants are associated to organizations or companies using your application. In Wristband, multiple tenants can live under a single application, and multiple users can live under a single tenant.

Tenants are logically isolated from each other. They exist in the same database instance, but data is isolated from each other using a tenant identifier discriminator column. In addition, each tenant has their own subdomain under the application's domain, and authenticated sessions are scoped to the tenant domain.

Each machine can issue unlimited access tokens. However, we monitor usage patterns and may reach out if activity becomes unusually high.  To prevent your machines from getting flagged for excessive usage, it's important to cache the access tokens locally and reuse them until they expire rather than creating new access tokens for each request.

Wristband manages the association between users, roles, and permissions, but the actual authorization decision is handled by your application. Wristband is responsible for providing the roles and permissions of the authenticated user to your application, but your application is responsible for using those roles and permissions to enforce authorization.

Not exactly. We prioritized our hosted Onboard UI pages for our out-of-the-box offering. We also allow you to host your own UI by configuring "Custom Page URLs" that lets you take control of our workflows through API calls. As a result, we don't currently support an embedded widget, though it is possible we may add some widgets in the future.

Yes! You can checkout our list of currently supported auth SDKs. We are working on adding more SDK's for your development. We'll provide updates to our documentation as they get released.

You can use this import script to import user information from a CSV file into your Wristband tenants. You can also leverage our APIs to create users as well. For larger volumes of data, we work with our customers on a case-by-case basis. In the future, we aim to support bulk user import and export APIs. If you have more complex needs, reach out to support and we will get you sorted.

If something isn't working for you, we'll go above and beyond to make your experience with us better. That said, we understand that sometimes you may have different needs. In that event, you can use this export script to export your data as a CSV. If you have more complex needs, reach out to support and we will get you sorted.