Shen AI pricing models
Shen AI pricing models
Shen AI offers two subscription-based pricing models: per scan and per user. Both provide access to the same technology - the difference is only how the usage is billed.
Your subscription includes a pre-paid amount of scans or users and choosing the right pricing model depends how your application is expected to be used.
Per-scan pricing
A per-scan subscription includes a set number of measurements (scans) that can be performed during your subscription period.
Each completed measurement counts as one scan. This model is a good fit for applications where users complete measurements as part of a specific interaction or service, and the expected number of measurements per user remains relatively low. Examples may include: telehealth consultations, insurance underwriting, digital intake and onboarding, health screening programs.
If measurements support specific interactions or workflows in your product, but are not something users are expected to perform on a regular basis, a per-scan subscription is a good choice.
Per-user pricing
A per-user subscription includes a pool of active users instead of individual measurements.
An active user is identified by the User ID passed to the SDK. Once that user performs their first measurement, they count as one active user and can continue performing scans without consuming additional user capacity. Only active users count toward your limit - ones that took at least one scan in a given month. After that first scan, the user can perform unlimited measurements and that does not affect your monthly limit.
This model is designed for products that encourage regular health monitoring and repeated measurements over time, including: employee wellbeing platforms, remote patient monitoring, chronic disease management, health coaching, or consumer health & wellness applications.
Good to know: How users are identified
For per-user subscription, active users are identified with the User ID provided by your application. Each unique User ID counts as one user, regardless of how many measurements that user performs.
If your application doesn’t provide a User ID, the SDK falls back to identifying users by the current device or browser. This works well when each device is used by a single person but it’s not recommended for shared devices, where multiple people could be treated as the same user.
Using a stable User ID also enables user-specific SDK features, such as blood pressure calibration, by ensuring measurements and calibration profiles remain associated with the correct person.
Note: User-specific data, including calibration profiles, is stored locally on the device or browser. If the same user signs in on a different device, that information isn’t synchronized automatically.
