One client view from every device, so nutritionists and trainers plan from measured data
How AnAr built a multi-tenant wellness SaaS for clinics and gyms that pulls a client's weighing scale, body-composition device, food scale, Google Fit, Apple Health, and wearables into a single timeline, on an Ionic, ASP.NET Zero, and AWS foundation.
A HealthTech platform built around the hardest part: the data
AnAr Solutions partnered with a health-technology product company to build the platform that nutritionists and fitness trainers use to run their practices. One system covers client measurements, nutrition and workout plans, day-to-day communication, and product sales, across independent clinics and gyms.
What sets the platform apart is how it handles data. A client's health numbers normally sit in a scatter of disconnected devices and apps. This platform pulls readings from the client's weighing scale, body-composition device, and food-measuring scale, along with activity data from Google Fit, Apple Health, and wearables, and brings all of it into one client timeline. The professional plans from what the client actually records, not from what they remember.
AnAr built the product in full: the device integration layer, the multi-tenant architecture, the cross-platform apps built with Ionic, and the commerce integration, on an ASP.NET Zero and AWS foundation. The platform serves as the daily working system for the practices that run on it.
One platform, many devices, many independent practices
Serving both nutritionists and fitness trainers, connecting to a range of consumer health devices, and hosting many independent practices on one product raised three distinct problems.
Fragmented client data
Weight on one scale, body composition on another device, food intake on a kitchen scale, activity in a fitness app. A professional assessing progress had to gather figures from several sources and stitch them together by hand. No single reliable picture existed, and the picture is the whole job.
Plans built on estimates
Without automatic device sync, weight and intake were entered by hand or recalled from memory. A nutrition plan resting on rough estimates is only as good as the estimate. The professional needed measured data flowing in on its own, as the client lived their week.
Multi-tenancy at scale
The platform had to host many independent clinics and gyms on one codebase, each seeing only its own clients. That isolation had to hold as practices grew, with no separate deployment per customer and no practice's data ever reaching another.
A single, measured view of each client, then planning on top of it
AnAr built the platform around one idea: give the professional a current, measured view of each client, then make planning, communication, and commerce easy on top of it.
A unified client data layer (the core of the work)
This is where most of the engineering went, and it is the part that is easy to underestimate. Every device and service speaks its own language. A weighing scale, a body-composition device, a food-measuring scale, Google Fit, Apple Health, and a range of wearables each expose data in a different shape, on a different schedule, through a different connection.
We built an integration framework that connects to all of them, normalizes their readings into one common model, and writes them to a single longitudinal timeline per client. All of them feed one view, with no manual re-entry. When a client steps on the scale, logs a meal, or finishes a tracked workout, the reading is in front of their nutritionist or trainer without anyone typing it in.
Planning and engagement
On top of that data, professionals create, track, and adjust personalized nutrition and workout plans for each client. Real-time chat keeps the professional and client in contact between visits, so a plan gets adjusted when the numbers call for it rather than at the next appointment. The data and the conversation live in the same place.
A multi-tenant foundation, built for a fast launch
We built the platform on ASP.NET Zero, a proven foundation for multi-tenant SaaS, so tenant management, authentication, and role-based permissions were in place from day one rather than rebuilt from scratch. It runs on AWS, with cross-platform apps built in Ionic covering iOS, Android, and the web from one codebase. Each clinic or gym runs as an isolated tenant, with a hard wall between every practice's data, and because that data is sensitive health information, tenant isolation and compliance were core requirements, not afterthoughts. The payoff was a full product on the market fast, with the custom engineering spent where it counted: the device integration.
In-platform commerce
The platform integrates Shopify, so professionals can sell recommended products to their clients directly in the app, a revenue path built into the work they already do.
What changed once the data was unified
What the build delivers
- Six or more data sources feed a single client timeline.
- Automatic device sync replaced manual entry of weight, body, and intake readings.
- One codebase serves many independent clinics and gyms, each with isolated data.
- One Ionic build covers iOS, Android, and the web.
What it means in practice
- A professional reviews a client's full history on one screen instead of reconciling several devices.
- Plans rest on measured data and get adjusted as the numbers move, not weeks later from memory.
- Data and client communication sit together, so advice stays tied to real behavior.
- In-platform product sales give practices a revenue path alongside consultations.
Why AnAr
AnAr built the full platform: the device integration layer, the multi-tenant architecture, the cross-platform apps, and the commerce integration. One team, one product, from the data plumbing to the screens.
The part that mattered most, connecting a scatter of consumer health devices into one reliable data flow, is the kind of integration engineering that looks simple in a demo and turns out to be the part everything else rests on in production. Getting it right is what separates a platform practices keep using from one they set aside within months.
If you are building a product in health, fitness, or any space where the data your users care about is scattered across many devices and services, the hard part is rarely the screens. It is the integration underneath, and the architecture that lets one product serve many customers cleanly. That is the work AnAr does.
Download the full case study
The page covers the story. The PDF goes deeper. Tell us where to send it and you will get the enriched version, including:
- The architecture diagram: devices, integration layer, multi-tenant backend, and apps
- A deeper look at how the device integration was built
- The multi-tenant architecture and the fast go-to-market reasoning
- The full build facts and outcomes
Download the case study
We will email you the full PDF.
After you submit: the full case study PDF lands in your inbox within a minute (check spam if it is not there). You get the case study, not a sales sequence.
Building a product where the data lives everywhere?
Tell us what you are building and where the data lives today. Our engineering team comes back with a real read on how we would approach the integration and the architecture underneath it.
Talk to our team →You will speak with engineering, not sales. A real reply within one business day.
Routed to the right engineer
Your note goes to someone who has built systems like yours, not to a sales queue.
A written reply within one business day
A real read on how we would approach your integration and architecture, not a sales sequence.
A review to go deeper
If it is a fit, we scope the work, the confidentiality terms, and what a first phase would look like.
See how we build products, from the data layer to the screens: Product Engineering →
Explore more of our work: AnAr Case Studies →