Platform Architecture

Multi-Provider SaaS Architecture

True Care System is designed as a multi-provider SaaS platform connecting the Web Portal, Mobile Application, API services, PostgreSQL database, security controls, and external EVV interfaces into one operational ecosystem.

Multi-Provider SaaS Architecture technical overview

Cloud SaaS

Built for multiple provider organizations with scalable cloud deployment.

🔐

Provider Isolation

Provider data is separated by authenticated context and role access.

📱

Mobile + Web

Supports office teams, supervisors, DSPs, and administrators.

🔗

Integration Ready

Designed for Alternate EVV and external data exchange.

How This Supports Providers

This section explains the operational value behind the diagram and how the workflow supports real provider use cases, EVV readiness, billing accuracy, and long-term SaaS scalability.

Connected Platform Layers

The architecture organizes operational functions into clear layers from user devices to API services and database storage.

  • Web Portal for administrative workflows
  • Mobile App for field care teams
  • NestJS API layer for business logic
  • PostgreSQL database with Prisma ORM

Provider Isolation by Design

True Care System supports multiple providers while keeping each organization’s data separated and protected.

  • Provider scope is derived from authenticated users
  • Frontend provider IDs are not trusted
  • Role-based permissions control visibility
  • Audit logs support accountability

Modern Technology Stack

The platform uses modern web, mobile, backend, ORM, and database technologies suitable for SaaS growth.

  • Next.js + TypeScript for the Web Portal
  • React Native + Expo for iOS and Android
  • NestJS + TypeScript for backend APIs
  • PostgreSQL for structured data

Scalable Operational Foundation

The system is built to support scheduling, EVV, billing, claims, payroll, reports, KPI, and compliance workflows.

  • Cloud deployment model
  • Secure HTTPS communication
  • Operational modules share one data foundation
  • Designed for future integrations

Technical Solution Overview

The diagram below can be shared with provider leadership, compliance teams, billing teams, IT reviewers, and EVV integration stakeholders.

Multi-Provider SaaS Architecture diagram

Key Workflow Sequence

Provider UsersOffice, supervisors, DSPs and admins.
Web + MobileBrowser portal and mobile app.
API LayerBusiness rules and security.
DatabaseProvider-scoped records.
IntegrationsSandata Open EVV readiness.

Common Questions

Can multiple providers use the same SaaS platform?

Yes. The platform is designed for a multi-provider model while keeping provider data separated by authenticated provider scope and role-based access.

What technologies power the platform?

The Web Portal uses Next.js and TypeScript, the Mobile App uses React Native and Expo, the API layer uses NestJS, and structured data is stored in PostgreSQL.

Continue Exploring

Ready to review the full technical overview?

Download the five-page Pennsylvania Alternate EVV Technical Solution Overview PDF.

Download PDF