Professional
For individual clinicians, attorneys, and small teams.
- Unlimited use
- Signed BAA within 24 hours
- HIPAA-compliant Claude on GovCloud
- 100,000-page File Library with OCR
Hathr.AI Enterprise gives your organization HIPAA-compliant Claude on AWS GovCloud, with Microsoft Entra ID single sign-on, SCIM 2.0 provisioning, and seat-based billing by card or invoice. Plans start at $47 per user per month with unlimited use, no seat minimum, and a signed BAA within 24 hours.
Sales hours: Monday to Friday, 9am to 5pm ET
Trusted by 3,000+ healthcare, legal, RCM, skilled nursing, hospice, and government organizations, including the Department of Health and Human Services and CMS.
Source: Hathr.AI, hathr.ai/solutions/enterprise
Each plan runs on the same GovCloud infrastructure with the same BAA. Enterprise adds single sign-on, provisioning, seat billing, and admin tools for organization-wide rollout.
For individual clinicians, attorneys, and small teams.
For health systems, payers, RCM, legal departments, and agencies.
For developers and health IT teams building PHI-safe products.
Hathr.AI is a HIPAA-compliant AI workspace that runs US government-approved Anthropic Claude models inside AWS GovCloud, a FedRAMP High environment.
Healthcare, legal, and government teams upload medical records, contracts, claims files, and spreadsheets to a private File Library. They ask questions in plain English and get formatted answers, summaries, and drafts in seconds. Each account includes a signed Business Associate Agreement, unlimited use, and storage for up to 100,000 pages.
More than 3,000 healthcare, legal, revenue cycle, skilled nursing, hospice, and government organizations use Hathr.AI, including the Department of Health and Human Services and CMS.
Teams range from solo practitioners and three-person legal teams to multi-state payers, hospitals, and federal agencies.
You upload files, ask a question, and Hathr.AI's Claude models plan the work, call the tools they need, and return an answer grounded in your documents, usually within about 30 seconds.
You can save repeatable workflows, so your team runs the same review on new files without re-uploading reference documents each time. Hathr.AI works on web, desktop, and mobile, and a HIPAA-compliant API connects it to your existing software.
Hathr.AI runs Anthropic's Claude models, approved for US government use, combined with retrieval-augmented generation (RAG) that grounds answers in your own files.
Hathr.AI uses zero data retention model deployments, so the models keep no copy of your prompts or files after they respond.
Former national security professionals who protected government systems built Hathr.AI to protect healthcare and other sensitive data.
Hathr.AI is an approved member of the Military-Civilian Defense Health Ecosystem.
Hathr.AI's Claude models use tool calling to take actions while they work on your request, such as searching your File Library, reading scanned pages with OCR, and working through spreadsheet data, before they write an answer.
A chat model without tools answers from what it learned in training. With tools, Hathr.AI goes to your documents, pulls the passages and rows that matter, and builds the answer from them. You see the result of several steps in one response.
Hathr.AI's models can search and retrieve passages from your File Library, extract text from scanned documents and images with native OCR, read and analyze spreadsheet data, and apply your saved workflows.
Tool calling makes Hathr.AI answer from your documents instead of from model memory, which reduces hallucinations and makes each answer traceable to a source file.
When a question needs a date from page 412 of a medical record or a total from a claims export, Hathr.AI retrieves that page or that column first. The model writes its answer after it has the evidence in hand.
No. Hathr.AI runs its tools inside the same AWS GovCloud environment as its models, so your files stay inside the FedRAMP High boundary while the model works.
Many commercial AI assistants call plugins and connectors hosted by other companies. Each of those calls can move your data to a new vendor. Hathr.AI keeps the full request inside one compliant environment under one BAA.
Yes. Hathr.AI analyzes unstructured data such as clinical notes, scanned faxes, contracts, and long PDFs, and structured data such as Excel spreadsheets, and can compare the two in a single request.
Most of the information in healthcare and legal work sits in documents that no database can query: notes, scans, letters, and records hundreds of pages long. Hathr.AI reads those files, pulls out the facts you ask for, and returns them as summaries, timelines, tables, or drafts. Your analysts get answers without building a data pipeline first.
| Data type | Examples | What you can ask |
|---|---|---|
| Unstructured text | Clinical notes, discharge summaries, contracts, policies, emails | "Summarize this patient's history in chronological order." |
| Scans and images | Faxed referrals, signed forms, image scans (read with native OCR) | "Find the date of the last wound assessment in these faxes." |
| Spreadsheets | Excel claims exports, invoices, rosters, utilization reports | "Which invoices exceed the coverage limits in this policy?" |
| Very long documents | Medical records and case files over 500,000 words | "List each medication change and the visit it came from." |
| Technical and proposal documents | RFPs, technical specifications, past proposals | "Draft section 3 of this proposal from our technical documents." |
Hathr.AI supports PDFs, Word documents, image scans, Excel spreadsheets, and a wide range of other file types, with native OCR for scanned pages.
Hathr.AI analyzes single documents of more than 500,000 words, about five times what commercial Claude or ChatGPT handle, and stores up to 100,000 pages per File Library.
There is no usage cap on any plan.
Yes. You can ask Hathr.AI to check rows in a spreadsheet against the terms in your documents in one request, such as matching invoices to policy coverage or claims to supporting records.
Revenue cycle teams use this to find claims with compliance issues before submission. Payers use it to check invoices against coverage details.
AWS GovCloud (US) is a pair of isolated Amazon Web Services regions, US-East and US-West, that AWS built to host sensitive and regulated data for US government agencies and vetted organizations in regulated industries. Vetted US citizens operate both regions on US soil.
AWS designed GovCloud for controlled unclassified information (CUI) in defense, law enforcement, healthcare, legal, and financial work. Hathr.AI is the only commercially available AI tool on AWS GovCloud. Hathr.AI runs its models, its tools, and all customer data inside it.
| Control | Commercial AWS regions | AWS GovCloud (US), where Hathr.AI runs |
|---|---|---|
| Who can open an account | Any business or individual with a payment method | Vetted US entities only. The root account holder must pass screening as a US person. |
| Who runs the infrastructure | AWS operations staff | Vetted US citizens only, with access controls separate from other AWS regions |
| Where it is | Regions around the world | Two US regions: US-East and US-West |
| Isolation | Standard AWS partition shared by commercial regions | Separate partition, physically and logically isolated from commercial regions |
| Sign-in | Standard AWS accounts | Separate credentials, isolated from Amazon.com authentication |
| Encryption endpoints | FIPS endpoints in some regions | FIPS 140-3 validated modules on service API endpoints |
| Compliance scope | Varies by region and service | FedRAMP High, DoD SRG IL2, IL4, and IL5, ITAR, CJIS, HIPAA |
Source: AWS GovCloud (US) User Guide and AWS GovCloud (US) overview.
Only organizations that pass AWS screening. AWS requires a US-incorporated entity based in the United States, a root account holder who is a verified US person, and the ability to handle ITAR export-controlled data.
Anyone with a credit card can open a commercial cloud account in minutes. GovCloud requires documentation, screening, and a signed region addendum, and AWS reviews each applicant. Hathr.AI completed that process. Your organization gets GovCloud protection through Hathr.AI without applying for its own account.
Hathr.AI runs entirely inside AWS GovCloud, so your PHI and proprietary data sit on infrastructure that only vetted US citizens administer, in a partition isolated from the commercial cloud where other AI tools run.
AWS limits GovCloud administration to vetted US citizens and limits accounts to vetted organizations. A smaller, screened group means a smaller attack surface.
GovCloud data remains physically in the US. Commercial AI tools can process data in regions you never chose.
GovCloud runs in its own partition with its own network and identity system, apart from the commercial regions where most AI tools run.
Service API endpoints in GovCloud use FIPS 140-3 validated cryptographic modules, the standard federal agencies require.
Your reviewers can point to the FedRAMP High authorization of the infrastructure under Hathr.AI. CMS data is compliant on day one.
The same infrastructure supports DoD Impact Level 5, ITAR, and CJIS workloads, so government contractors can use Hathr.AI for controlled data.
AWS GovCloud adds controls that commercial regions lack: US-citizen-only operations, screened account holders, a separate isolated partition, isolated authentication, and FIPS 140-3 validated endpoints.
AWS applies the same baseline security to all its regions. GovCloud layers access restrictions and isolation on top, which limits who can reach the systems that hold your data.
AWS GovCloud reduces risk by shrinking the group of people and organizations that can reach the infrastructure, keeping data in the United States, and separating it from commercial cloud networks.
For a covered entity, that means fewer paths to a reportable PHI breach. For a government contractor, it means an AI tool that fits CUI and federal data requirements.
AWS publishes the same service level agreements for GovCloud and commercial regions, such as a 99.99% monthly uptime commitment for Amazon EC2 deployed across multiple availability zones.
GovCloud's advantage over commercial cloud is isolation and access control. Hathr.AI's own uptime and support commitments for your organization are set in your enterprise agreement. Ask sales for the terms.
Hathr.AI is the only commercially available AI tool on AWS GovCloud. It runs on the same government-approved infrastructure the Department of Health and Human Services uses.
Yes. Hathr.AI is HIPAA compliant. Hathr.AI signs a Business Associate Agreement with each customer, typically within 24 hours, and runs entirely on AWS GovCloud, a FedRAMP High environment.
Hathr.AI Enterprise adds the access and audit safeguards the HIPAA Security Rule calls for: single sign-on, SCIM deprovisioning, role-based access, and authentication audit logs.
Yes. Hathr.AI signs a Business Associate Agreement with each account on each plan, typically within 24 hours.
Commercial AI vendors can take months to negotiate a BAA, and many offer one only on enterprise contracts.
Hathr.AI runs on FedRAMP High infrastructure. AWS GovCloud (US) holds a FedRAMP High authorization, and Hathr.AI hosts its models and all customer data inside it.
FedRAMP High is the most stringent FedRAMP baseline for unclassified systems.
Yes. Hathr.AI's FedRAMP High GovCloud hosting makes it compliant for CMS data on day one.
The Department of Health and Human Services and CMS use Hathr.AI.
Yes. Hathr.AI complies with 42 CFR Part 2 for substance use disorder records and 38 CFR § 7332 for protected VA health records, in addition to HIPAA.
No. Hathr.AI does not use customer data to train AI models. Hathr.AI runs zero data retention models and does not monetize customer data.
Hathr.AI stores customer data on AWS GovCloud infrastructure in the United States.
Your organization's users can access your data according to the roles your admins assign. Vetted US citizens administer the underlying AWS GovCloud infrastructure, and Hathr.AI does not access or monetize customer data.
Hathr.AI Enterprise includes SAML single sign-on with Microsoft Entra ID and Google Workspace, SCIM 2.0 provisioning, organization workspaces with enterprise roles, authentication audit logging, seat-based billing by card or invoice, seat limit alerts, an admin API, and an admin panel with a usage dashboard.
Thirteen capabilities in five areas, all running on AWS GovCloud. Each entry covers what the feature does, how it works, where teams use it, and how it compares with commercial enterprise AI tools.
Hathr.AI Enterprise supports SAML 2.0 single sign-on with Microsoft Entra ID (formerly Azure AD) and Google Workspace. Your staff sign in with the identity provider they already use, and your MFA and conditional access policies apply to Hathr.AI from the first sign-in.
/scim/v2/Users/scim/v2/GroupsHathr.AI Enterprise connects to your SAML 2.0 identity provider, including Microsoft Entra ID and Google Workspace. Hathr.AI registers, updates, and removes identity provider settings at runtime, so your organization goes live on single sign-on without waiting for a software release.
How it works. Your IT team creates a Hathr.AI enterprise application in Entra ID and sends us its federation metadata. We register it against your organization. When you rotate a signing certificate or change claim rules, we update the settings in place. If you leave Hathr.AI, we delete them.
Attackers reach PHI most often through stolen passwords. Central identity puts your MFA, conditional access, and password rules in front of Hathr.AI on day one. Your IT team changes a policy once in the directory and it applies to Hathr.AI too.
ChatGPT Enterprise and Claude Enterprise offer SAML SSO, but the session lands in a commercial cloud. With Hathr.AI, the sign-in flow and the workspace behind it both run inside AWS GovCloud under a signed BAA.
Hathr.AI sends each user to the right identity provider based on their work email domain. A clinician types name@yourhealthsystem.org and lands on your Microsoft Entra ID sign-in page, with no organization code or custom URL to remember.
How it works. Your organization claims its email domains. At sign-in, Hathr.AI matches the domain and starts the SAML flow with your identity provider. Users on domains without SSO continue to standard sign-in.
Staff create local passwords when they can't find the SSO button, and those accounts sit outside your controls. Domain routing makes SSO the default path, which cuts help desk tickets and stops shadow accounts before they start.
Hathr.AI routes users before they enter any credential, and only to identity providers registered to your organization. Your users see your sign-in page and no other organization's.
Hathr.AI maps SAML groups from Microsoft Entra ID or Google Workspace to Hathr.AI roles at sign-in. A user's directory group decides whether they are an organization admin or a member.
How it works. When a user signs in, Hathr.AI reads the group claims in the SAML assertion and assigns the matching Hathr.AI role before it issues the session token. Move a user to a different group in Entra ID and their Hathr.AI role changes at their next sign-in.
HIPAA's minimum necessary standard expects you to limit access by role. When your directory controls roles, you run one access review instead of two, and permissions can't drift between systems.
Hathr.AI resolves the role when it issues the token, so users start each session with current permissions. A nightly sync would leave a gap of hours.
Hathr.AI creates an account inside your organization the first time an authorized user signs in through your identity provider. Your IT team sends no invitations and maintains no second user list.
How it works. After a successful SAML sign-in, Hathr.AI checks for an existing account. If none exists, it creates one, attaches it to your organization, applies the mapped role, and assigns a seat. The user lands in a ready workspace.
AI rollouts stall on manual onboarding. Auto-onboarding lets adoption follow your directory, and seat limits keep it inside your contract.
Each new account belongs to your organization from its first sign-in and inherits your BAA, your GovCloud hosting, and your seat count.
Your directory stays the source of truth. When HR adds, changes, or terminates someone in Microsoft Entra ID or Google Workspace, Hathr.AI follows.
Hathr.AI provides SCIM 2.0 Users and Groups endpoints, so Microsoft Entra ID and Google Workspace can create, update, and deactivate Hathr.AI accounts. Each organization authenticates with its own bearer token.
How it works. Your IT team adds Hathr.AI as a provisioning target in Entra ID with the SCIM endpoint URL and your organization's token. Entra ID then pushes user and group changes to /scim/v2/Users and /scim/v2/Groups. The token works only for your organization's users.
The HIPAA Security Rule requires you to end access when employment ends. SCIM handles deprovisioning for you, so a former employee can't keep using a workspace that holds PHI.
Hathr.AI issues provisioning tokens per organization. If someone leaks a token, the exposure stops at one organization.
Each enterprise user, seat, and sign-in belongs to your organization. Your directory sets roles, and Hathr.AI logs authentication events for your compliance team.
Hathr.AI Enterprise groups your users, subscription, and settings into one organization. Hathr.AI scopes each enterprise record to that organization, and no organization can see another's users, usage, or audit history.
How it works. The organization holds your identity providers, email domains, roles, seats, and billing. Admins view and update organization details, and Hathr.AI checks the caller's organization on each enterprise request before it returns data.
Without an organization, each user holds a separate account and subscription. The organization gives IT and compliance one view of who uses AI with PHI.
Hathr.AI enforces organization scoping in the application on each request, on top of AWS GovCloud's infrastructure isolation.
Each Hathr.AI enterprise user belongs to an organization and holds an enterprise role. Admins manage seats, users, and audit history. Members use the workspace.
How it works. User profiles store organization membership and role. With SSO on, roles come from your identity provider's groups. Without SSO, an admin sets them.
Clear roles shorten access reviews and give auditors a direct answer when they ask who can do what.
Roles connect to your directory, so you review access where you already manage it.
Hathr.AI records authentication events for each enterprise user, including SSO sign-ins, and shows them to your organization's admins. Hathr.AI writes these logs in the background, so logging adds no delay to sign-in.
How it works. Hathr.AI queues each authentication event and writes it to your organization's audit log. Admins review the log in the admin panel or pull it from the admin API.
The HIPAA Security Rule requires audit controls that record activity in systems containing ePHI. The authentication log gives your compliance team that record for AI use.
Hathr.AI keeps the audit trail in the same FedRAMP High GovCloud environment as your data.
One contract covers your organization. You pay per seat by card or invoice, with unlimited use included and no seat minimum.
Hathr.AI Enterprise bills per seat at the organization level. You pay by card or by invoice, and each seat includes unlimited use and the BAA.
How it works. Your organization holds one enterprise subscription with a contracted seat count. Card billing renews on schedule. Invoice billing runs through your accounts payable process.
Personal subscriptions on corporate cards are hard to track and harder to cancel. One seat-based contract gives finance a predictable cost and gives IT a list of covered users.
Each seat includes unlimited use, so your cost stays flat as adoption grows. Usage-priced AI tools charge more as your team uses them more.
Hathr.AI checks your organization's subscription on each request. When a user joins your organization, the enterprise plan covers them and they need no personal subscription.
How it works. Hathr.AI resolves each user's organization and confirms the enterprise plan is active before it grants enterprise access.
When coverage follows the organization, no user falls outside the BAA or contract because of how they first signed up.
Coverage follows the organization instead of the individual.
Hathr.AI enforces the seat count in your enterprise contract and alerts admins as usage approaches it, so you can add seats before anyone gets blocked.
How it works. Each new user takes a seat, whether SCIM provisioned them or they signed in for the first time. Hathr.AI alerts admins as seats run low. At the limit, new users wait for a seat instead of exceeding the contract.
Procurement approves predictable spend. Enforcement and alerts mean no surprise invoices and no surprise lockouts.
Hathr.AI has no seat minimum. You contract for the seats you need, and limits protect that number.
Organization admins see seats, users, audit history, and usage inside the Hathr.AI app, or pull the same data from the admin API.
Hathr.AI Enterprise provides admin API endpoints for seat overview, user list, audit log, and usage, so IT and compliance teams can pull organization data into their own tools.
How it works. Admin endpoints require an enterprise admin role and return data for the caller's organization only.
Compliance teams work in their own systems. The API lets Hathr.AI data feed reports you already run.
Hathr.AI serves admin data from AWS GovCloud and scopes it to your organization.
The Hathr.AI enterprise admin panel gives organization admins a seat overview, user list, authentication audit log, and usage dashboard inside the Hathr.AI app.
How it works. Admins open the panel from the same Hathr.AI app their users sign in to. There is no separate console or login.
Admins answer their own questions in minutes instead of opening a vendor support ticket.
Administration lives in the same compliant workspace, so admin activity stays in GovCloud.
| Feature | Professional | Enterprise |
|---|---|---|
| Price | $47 / user / month | Contact sales |
| Security and compliance | ||
| Signed BAA within 24 hours | ✓ | ✓ |
| AWS GovCloud hosting (FedRAMP High) | ✓ | ✓ |
| Data never used for training | ✓ | ✓ |
| Workspace | ||
| Unlimited use | ✓ | ✓ |
| 100,000-page File Library with native OCR | ✓ | ✓ |
| 7-day free trial | ✓ | — |
| Identity and access | ||
| SAML SSO with Microsoft Entra ID and Google Workspace | — | ✓ |
| Sign-in routing by email domain | — | ✓ |
| Identity provider group-to-role mapping | — | ✓ |
| Automatic onboarding of federated users | — | ✓ |
| SCIM 2.0 user and group provisioning | — | ✓ |
| Organization workspace with enterprise roles | — | ✓ |
| Administration and billing | ||
| Enterprise admin panel with usage dashboard | — | ✓ |
| Authentication audit log | — | ✓ |
| Seat limits and consumption alerts | — | ✓ |
| Billing | Card | Card or invoice |
| Guided SSO and SCIM setup with your IT team | — | ✓ |
ChatGPT Enterprise and Claude Enterprise offer SSO and admin controls on commercial cloud infrastructure, and you negotiate the BAA case by case. Read: Is Claude HIPAA compliant?
| Capability | Hathr.AI Enterprise | Commercial enterprise AI tools |
|---|---|---|
| Hosting | AWS GovCloud, FedRAMP High | Commercial cloud regions |
| Business Associate Agreement | Every account, within 24 hours | Negotiated with sales, can take months |
| CMS and federal data | Compliant on day one | Not hosted on GovCloud |
| SSO and SCIM | Entra ID and Google Workspace | Available on enterprise tiers |
| Seat minimum | None | Often required |
| Pricing | From $47/user/month, unlimited use | Quoted by sales |
| Training on your data | Never | Off by default on enterprise tiers |
What your security, compliance, and procurement reviewers need to know.
Read our security and privacy overview →Signed for every account, typically within 24 hours.
Hosted on AWS GovCloud, a FedRAMP High environment. Compliant on day one for CMS data.
HIPAA, 42 CFR Part 2, and 38 CFR § 7332.
SAML 2.0 single sign-on and SCIM 2.0 provisioning with Microsoft Entra ID and Google Workspace.
Roles are assigned from your identity provider groups. Data is scoped to your organization.
Authentication events are logged and visible to your admins.
Zero data retention models. Your data is never used to train AI models.
Seat-based subscriptions at the organization level, paid by card or invoice.
Teams that handle PHI, PII, and proprietary data use Hathr.AI Enterprise to bring AI into their daily work while staying compliant.
Summarize patient histories and find specific records in seconds, with clinicians signing in through your existing Entra ID tenant.
Analyze claims for compliance issues and check invoices against policy coverage details.
Reduce documentation and administrative work so staff spend more time with patients.
Hathr.AI for hospice →Review large medical records and case files of more than 500,000 words in a private workspace.
Work with CMS and federal data on FedRAMP High infrastructure. Draft proposal sections from technical documents without exposing proprietary data.
Tell us about your team, your data, and your compliance requirements.
We can return a signed Business Associate Agreement within 24 hours or accomodate requests.
We walk your IT team through SAML and SCIM setup with Microsoft Entra ID or Google Workspace. Your team is compliant from day one.

My patient had a complex medical history, and I needed to be able to find a specific record quickly during our visit. Hathr AI found the visit and created a patient summary in seconds
Our team can now go through a document in seconds and start responding to sections of the proposal. It’s all private so I’m not worried that GPT will just feed all my competitors what made us win the bid.
I uploaded all the documents from my technical team and then asked Hathr to create an outline and draft sections based on the technical docs. Since it’s all private, I don’t have to worry about leaking my company’s proprietary data when I upload a document.
Hathr.AI starts at $47 per user per month with unlimited use and a signed BAA on each account. Hathr.AI Enterprise uses per-seat pricing at the organization level, billed by card or invoice, with no seat minimum. Contact Hathr.AI sales at hathr.ai/contact for an enterprise quote.
Standard ChatGPT plans don't include a Business Associate Agreement, so you shouldn't use them with PHI. OpenAI offers BAAs on some enterprise agreements, but ChatGPT runs in commercial cloud regions outside FedRAMP High. Hathr.AI signs a BAA with each customer and runs entirely in AWS GovCloud.
You can use ChatGPT Enterprise with PHI only under a BAA you negotiate with OpenAI, and it runs on commercial cloud infrastructure. Organizations that need FedRAMP High hosting, a BAA within 24 hours, and no seat minimum choose Hathr.AI Enterprise, which also supports Microsoft Entra ID SSO and SCIM provisioning.
Anthropic's consumer Claude plans don't include a BAA. Hathr.AI runs US government-approved Anthropic Claude models inside AWS GovCloud and signs a BAA with each customer, so your team can use Claude with PHI through Hathr.AI.
Anthropic offers a BAA for Claude Enterprise on negotiated terms, and Claude Enterprise runs on commercial cloud infrastructure. Hathr.AI gives your organization HIPAA-compliant Claude with a BAA signed within 24 hours, hosting on AWS GovCloud (FedRAMP High), Microsoft Entra ID SSO, SCIM provisioning, and no seat minimum.
An AI tool is HIPAA compliant for your use when the vendor signs a BAA and protects PHI with the safeguards the HIPAA Security Rule requires, including access controls and audit controls. Hathr.AI signs a BAA with each customer. Hathr.AI Enterprise adds SSO, SCIM deprovisioning, role-based access, and authentication audit logs on FedRAMP High AWS GovCloud infrastructure.
Yes. Hathr.AI Enterprise supports SAML 2.0 single sign-on with Microsoft Entra ID (formerly Azure AD). Users sign in with their work email and Hathr.AI routes them to your Entra ID tenant. Entra ID groups map to Hathr.AI roles, and Hathr.AI creates accounts for new users at their first sign-in.
Yes. Hathr.AI Enterprise supports SAML 2.0 single sign-on and SCIM 2.0 provisioning with Google Workspace as well as Microsoft Entra ID.
Yes. Hathr.AI provides SCIM 2.0 Users and Groups endpoints secured with a bearer token unique to your organization. Microsoft Entra ID and Google Workspace use them to create, update, and deactivate Hathr.AI accounts.
When you deactivate a user in Microsoft Entra ID or Google Workspace, SCIM deactivates their Hathr.AI account and SSO stops letting them in. This supports the HIPAA requirement to end access when employment ends.
At sign-in, Hathr.AI reads the group claims in the SAML assertion from Entra ID and assigns the matching Hathr.AI role, such as organization admin or member, before it issues the session token. Move a user to a different group in Entra ID and their Hathr.AI role changes at their next sign-in.
Yes. Hathr.AI Enterprise records authentication events, including SSO sign-ins, for each enterprise user. Admins review the audit log in the admin panel or pull it through the admin API.
Hathr.AI alerts organization admins as seat usage approaches the contracted limit. At the limit, new users wait for a seat instead of exceeding the contract, so admins can add seats without surprise charges.
Yes. Hathr.AI Enterprise supports invoice billing and card payments, with seats billed at the organization level.
No. Hathr.AI has no seat minimum and no usage cap. Solo practitioners, multi-state health systems, and federal agencies all use Hathr.AI.
Contact Hathr.AI sales at hathr.ai/contact. After you sign the BAA, Hathr.AI walks your IT team through SAML and SCIM setup with your identity provider. Sales is open Monday to Friday, 9am to 5pm ET.
Get seat-based enterprise pricing, a signed BAA within 24 hours, and single sign-on with Microsoft Entra ID.
Sales hours: Monday to Friday, 9am to 5pm ET.