Medoteca
RORequest a demo

One core under every module.

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.

Tenancy
Isolated per organisation
Modules
4 suites, released independently
Surfaces
Portal today, client app next

Who works where.

  • Operations portal

    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.

    • B2B
    • Available
  • Client application

    Where the people you serve will see their visits, documents and reminders, under your organisation’s branding. Not released yet.

    • B2C
    • In development

How it fits together.

Three decisions that shape everything else.

  • Tenancy is in the address

    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.

  • Permission builds the interface

    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.

  • Modules release independently

    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.

The parts that are always there.

Whichever module you are in, these behave identically.

  • Access & tenancy

    • Sign-on, multi-factor and session control
    • Roles and permission groups per organisation
    • One person, several organisations, one default
    • Trusted devices, individually revocable
  • Shape & configuration

    • Every module and sub-feature enabled per organisation by our team, according to its plan
    • Company profile, logo and branding
    • Roles, users, invitations and seat quota
    • Currencies, timezones and locale
  • Figures & reporting

    • Widget tiles contributed by every module
    • Period per tile, or inherited from the dashboard
    • Custom ranges and grouped presets
    • Filters, column chooser and export
  • Content on records

    • Notes with revisions and reordering
    • Threaded comments
    • Documents attached to the record they belong to
    • Counts visible from the list, before you open anything
  • Staying current

    • Live notifications over an open connection
    • Guided walkthroughs for first-time users
    • Search across the portal, with AI answers
    • A chat assistant inside the portal
  • Comfort & access

    • Light and dark, plus accent colour
    • Text size, typeface and contrast controls
    • Enhanced focus and reduced motion
    • Language per person, not per browser
  • When the connection drops

    • Installs on a computer or phone, like any app
    • Today’s appointments, with each client’s notes, visits and recommendations, readable offline
    • Notes, visits and bookings made offline are kept, then sent when the connection is back
    • Offline access is turned on per device, behind a PIN you set

Assistant.

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.

Knows your modules
Your team and its roles, your product catalogue, your own account: it works with the modules you have, and each module you add brings more it can answer.
Does it, not explains it
Ask it to change a setting or update your profile, and it makes the change instead of telling you where to find it.
Sees only what you see
It works with your permissions, never above them. If your role cannot open something, the assistant cannot either.
No mystery box
It names each step while it works, and a monthly message counter stays on screen.
IllustrationThe assistant answering which users hold the Manager role, with suggested prompts and a monthly message counter.

We run it ourselves.

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.

  • Kubernetes, operated by us
  • Encrypted at rest
  • Audit trail on changes
  • Regular backups

Which of these do you actually need?

Most businesses run four or five. Tell us how your week works and we will show you the set that fits.

Request a demo