Auxilison is a single backend with three application surfaces — one for each role in the program-delivery relationship. The creator authors and oversees. The practitioner delivers. The client engages with the program. This documentation maps every navigation area, feature, and capability across all three surfaces, plus the cross-cutting capabilities that show up everywhere.
The architectural choice to ship three distinct applications — instead of one application with role-switching — is deliberate. Each role has different needs, different cadence, and different attention. Each surface is built around what that role actually does, not around what the database happens to contain.
Where the program creator authors the methodology, manages who's authorized to deliver it, and sees how the network is performing.
Where the certified practitioner delivers programs to clients with quality and care. Built around their daily clinical workflow.
Where the end client engages with their assigned program. Mobile-first because that's where daily engagement happens.
Reading the architecture as a flat feature list makes it hard to see who uses what. This map orients each capability domain to the surface (or surfaces) where it lives, and which user role interacts with it.
| Capability domain | Where it lives | Surface |
|---|---|---|
| Practice management | Today, Clients, Schedule, Messages | Practitioner |
| Clinical charting | Clients › Notes (AI-assisted) | Practitioner |
| Programs & courses | Programs, Library | Creator |
| Telehealth | Schedule › video launch | Practitioner |
| Client portal | Entire Client App | Client |
| Messaging | Messages tab everywhere | Creator Practitioner Client |
| Mobile app | Practitioner companion + Client App | Practitioner Client |
| Storage / content delivery | Library, Programs › content | Creator Practitioner |
| Program authoring | Programs (Studio) | Creator |
| Network management | Network | Creator |
| Outcome aggregation | Outcomes | Creator |
| Credential management | Network › credentials | Creator |
| AI session notes | Cross-cutting | Practitioner |
| Hearing-profile awareness | More › Hearing profile | Client |
| Compliance (HIPAA) | Cross-cutting | All |
| Reporting & analytics | Outcomes (creator), Today / Clients (practitioner) | Creator Practitioner |
| Specialty integrations | Settings › Integrations (limited) | Creator Practitioner |
| Insurance billing | Out of scope | — |
These pages can be read in any order, but each has a natural audience. If you're evaluating Auxilison, start with the surface that matches your role.
Start with Creator Studio. This is your surface — program authoring, practitioner network management, outcome aggregation. Then read Cross-cutting capabilities for compliance and integrations.
Start with Practitioner Workspace. This is your daily tool — client management, scheduling, telehealth, messaging, AI session notes. Then read the Client App documentation so you understand what your clients see.
The Client App documentation walks you through the experience. Most clients never need to read it — the app is built to be used, not learned. But if you want to understand what's available, it's here.
Read all four pages in order: Creator Studio, Practitioner Workspace, Client App, and Cross-cutting capabilities. The full picture takes about 25–30 minutes to absorb.
Auxilison is a program-delivery platform, not a generic practice-management EHR. Several capabilities common in adjacent tools are explicitly out of scope. We say so plainly so you can plan accordingly.
Practitioners with insurance needs use a separate tool alongside Auxilison.
We are not a medical platform. Prescribing belongs in your EHR.
Custom-tier add-on (Rupa, Evexia) for functional medicine programs that need it. Not in core.
Custom-tier add-on for programs that need direct dispenser integration. Not in core.
Light wearable import is included. Food databases at the depth of TCL or Cronometer are out of scope.
We serve programs, not clinic operations. Room booking and walk-in workflows are not modeled.
Our notes are program-context notes. A practitioner who needs SOAP charting uses a separate EHR.
Explicitly excluded. We will not build it.
The shape of your network, the methodology you've built, and what you're trying to accomplish. We'll match you to the right tier — and if your situation is unusual, we'll work out commercial terms that fit. There's no script and no pressure.