Cookies
We would like to use Microsoft Clarity to see how this site is used, so we can improve it. It only runs if you accept. Cookie policy
Not a set of integrations. Every module reads the same model of people, time, places and permissions, which is why a provider booked in Scheduling is the same person whose leave is approved in Workforce.
Where your team runs the day: the schedule, the staff, the rooms, the records and the figures that come out of them. The chat assistant lives here.
Where the people you serve will see their visits, documents and reminders, under your organisation’s branding. Not released yet.
Three decisions that shape everything else.
Every page lives under the organisation it belongs to. One person can hold access to several organisations, pick a default, and move between them without signing out — and no request can quietly read across the boundary.
Navigation, pages and actions are assembled from what the signed-in person may do. Somebody without a permission does not see a disabled button; the route is not there at all.
Each module is built, versioned and deployed on its own, then composed into the portal at run time. A fix to one ships without a coordinated release of the others.
Whichever module you are in, these behave identically.
Ask in plain words instead of hunting through menus. It is an AI assistant that works across the modules your organisation has, stays within what your role allows, and tells you what it is doing while it does it.
The platform runs on infrastructure we operate end to end, which is how we can answer questions about its behaviour with measurements instead of diagrams.
Most businesses run four or five. Tell us how your week works and we will show you the set that fits.
Request a demo