Maica Healthcare is built on the Salesforce platform. That decision shapes what Maica offers on day one, and how far it can go later.

We believe every enterprise system rests on three things.
Meeting the regulatory and legal standards required to operate.
Keeping your data and your Participants' data safe.
Making sure the system is always available when you need it.
Maica is built on a platform that provides all three out of the box.
Maica inherits the platform's own capability, and it applies to every Maica record.
Reports and Dashboards are native to the platform. Build a report on any Maica record, chart it, schedule it, and send it to the people who need it. Reporting sits in the same place as the data.
Sharing rules and permission sets decide who sees what, down to individual fields. Audit Trails record what changed, when, and by whom. Participant data sits on infrastructure trusted by enterprises and governments globally.
Add fields, adjust page layouts, set validation and build automation, all without code. Maica records behave like any other Salesforce object, so custom workflows, app extensions and platform upgrades apply to them the same way.
The same platform serves small teams and large workforces. Maica runs on infrastructure built for that range, so growing is a matter of adding users.
Salesforce is a large ecosystem, and Maica sits inside it. Clouds, AI agents and thousands of applications are built on the same platform, so what a provider adds later works with what is already there.
Salesforce's AI agents, working on the same records your team works in.
Salesforce's own healthcare product set, with clinical data models and care coordination on the same platform.

Salesforce's product set for nonprofit organisations, built on the same platform and available alongside Maica.

The Salesforce ecosystem runs far wider than this. Have a look at what else lives on the platform.
Maica Forms, Maica Docs, Maica Portals and Maica Learning all work with Salesforce data. Forms write submissions straight in, Docs generate from live records, Portals draw on them, and Learning writes completions back.
A few things providers ask about Maica and the Salesforce platform.
Maica Healthcare is built on the Salesforce platform, so it runs inside a Salesforce org. Maica Forms, Maica Docs, Maica Portals and Maica Learning connect to Salesforce data, and each also works without it.
Maica Healthcare runs on the platform itself. Participant Profiles, Service Agreements, Scheduling & Rostering and billing are all Salesforce records, held in the same place as everything else in the org.
Yes. Reports and Dashboards, sharing rules, permission sets, validation and automation all apply to Maica records the same way they apply to any other Salesforce object.
Fields, page layouts, validation rules and automation can all be added without code. Because Maica records behave like any other object on the platform, the platform's own configuration tools apply to them.
Service Cloud, Nonprofit Cloud and the applications on AppExchange are all built on the same platform and can be added alongside Maica. Salesforce developers and partners can also extend the org directly.