Everything your review needs, before you ask
An ungated security page, a security pack with no form and specific, dated answers.
Security314eDR
Your identity providerAzure AD (SAML, SCIM) or Okta · MFAOn
Encrypted everywhereTLS 1.3 in transit · AES-256 at restOn
Isolated per customerOwn storage, credentials, database, computeOn
AI that stays in its laneAnswers only from your published contentOn
Trusted by teams at
Forrest Health
100K+Active clinicians
240K+How-to questions answered
330K+Tip sheet and video views
The questions every review starts with
The short answers
| Question | Answer |
|---|---|
| Does it support single sign-on? | Azure AD (SAML, SCIM), Okta and other SAML 2.0 providers |
| How is data encrypted? | TLS 1.3 in transit; AES-256 at rest |
| How is each customer's data kept separate? | Separate storage, credentials, database and compute per customer |
| Does it store patient data? | Not designed to store PHI; contracts prohibit uploading it |
| Which certifications do you hold? | SOC 2 Type II compliant: audited, certified, and continuously monitored cloud infrastructure |
Less to run
Why IT likes it
Fewer tickets
How-to questions answered inside Epic.
Fewer tools
One platform replaces several.
What we'll need from you
SSO, a user feed and an Epic launch.
More roles, more views of Jeeves
See what Jeeves means for the rest of your team.
SOC 2 Type IIEnterprise-grade
everything
Security and compliance built in from the start, not bolted on after.
Security answers before you ask.
See it for yourself.
Trusted by teams at
- LCMC Health
- Bryan Health
- Forrest Health
- John Muir Health
- Dayton Children's
Security314eDR
Your identity providerAzure AD (SAML, SCIM) or Okta · MFAOn
Encrypted everywhereTLS 1.3 in transit · AES-256 at restOn
Isolated per customerOwn storage, credentials, database, computeOn
AI that stays in its laneAnswers only from your published contentOn
3