How Rhazes Enterprise is deployed
Rhazes Enterprise is a separate deployment of the whole application for your organisation, not a tier on the shared service.
Updated
It is your own deployment
Rhazes Enterprise is not a plan you upgrade to. It is the whole application, deployed separately for your organisation.
Your clinicians sign in to your instance. Your data lives in your instance. Your configuration is yours. Nothing is shared with other organisations using Rhazes, because there is no shared thing to be part of.
Why it works this way
Because the things enterprise customers actually need are deployment decisions, not account settings.
Connecting an EHR means pointing at a specific endpoint with a specific client registration approved by a specific trust. Where the data sits is a governance question with a legal answer. Which sign-in provider clinicians use is set by your identity estate. None of those can be a toggle on a shared service that ten other organisations are also using.
Once you accept that, a separate deployment is the honest answer rather than a premium one.
What is configured for you
Set up as part of your deployment rather than by each clinician:
- Your EHR connection. Which system, which endpoint, which FHIR resources. See EHR integration with Rhazes.
- How clinicians sign in, including signing in with their EHR account.
- Clinical audit, on for everyone rather than granted account by account. See Audits.
- Any custom work built for your organisation. See Custom integrations.
No plans, no limits, no cards
This is the part clinicians notice first, and it is worth stating plainly.
On an enterprise deployment there is no subscription, no free tier and no usage caps. Nobody hits a daily message limit, nobody runs out of transcriptions, and no clinician is ever asked for a card or drops into view only mode because of a billing state.
Everything documented under Plans, limits & billing applies to the public service and simply does not exist on your instance. Your Limits page reads unlimited across the board.
Everyone gets everything
There is no feature tier inside your deployment. Every clinician on it has chat, dictation and transcription, documents and templates, workflows, tasks, patients, spaces, coding, clinical audit and whatever EHR access your organisation has approved.
Getting one
Enterprise starts with a conversation rather than a checkout. Email support@rhazes.ai with what you are trying to do, which EHR you run, and roughly how many clinicians are involved.
Hosting, data residency and the specifics of where your deployment runs are agreed with you as part of that, because the right answer depends on your organisation rather than on us.