Suki AI

integrator · United States , Redwood City · founded 2017

Employees: 201-1000 · Stage: Series D · Funding: $168,000,000

42.6

elevated

default-balanced
composite score

Ambient voice-AI assistant for clinical documentation, coding, and command-driven EHR workflows. Founded 2017 by Punit Soni (ex-Google, Motorola, Flipkart). HIPAA + SOC 2 Type II + BAA available; PHI de-identified to HIPAA Safe Harbor before LLM inference. Used by 400+ healthcare systems including FMOL Health and McLeod Health. $168M raised total, $70M Series D October 2024 (Hedosophia).

Analyst summary

Suki is the AI clinical-documentation specialist with the most mature compliance posture: HIPAA, SOC 2 Type II, BAA available, and an explicit data-flow design where PHI is de-identified to HIPAA Safe Harbor standards before any LLM provider sees it. 400+ healthcare systems on the customer roster (FMOL Health, McLeod Health) and $168M raised including a $70M Series D in October 2024 (Hedosophia-led).

Strong default pick for US health systems adopting AI clinical documentation. Compliance posture is appropriate and the Safe-Harbor de-identification architecture is a genuine design choice rather than a compliance checkbox. Watch for any product expansion that pushes Suki into clinical-decision territory — that crosses the EU AI Act high-risk line.

Rating: recommended

Compliance posture

SOC 2 Type II	Yes (report 2025-10-01)
ISO 27001	No / not disclosed
ISO 42001 (AI management system)	No / not disclosed
FedRAMP authorized	No / not disclosed
GDPR compliant	No / not disclosed
CCPA compliant	Yes
HIPAA compliant	Yes
NIST AI RMF aligned	No / not disclosed
CSA STAR certified	No / not disclosed
EU AI Act classification	high_risk

Data handling

Trains on user data	never
Outputs feed model improvement	never
Data retention period	Per HIPAA retention requirements and customer contract
Can delete user data on request	Yes (SLA 30 days)
Default data residency	US
Encryption at rest	Yes (AES-256 / TLS 1.2+)
Encryption in transit	Yes
DPA available	Yes
Public subprocessor list	Yes
HIPAA BAA available	Yes

IP profile

User owns outputs	yes
Vendor claims output rights	No / not disclosed
Input IP protection	strong
Indemnification offered	Yes
Copyright shield program	No / not disclosed
Commercial use permitted	Yes
Training data provenance	not_applicable
Known IP lawsuits	No / not disclosed

Jurisdiction

Incorporation country	US
Incorporation jurisdiction risk	low
Subject to US jurisdiction	Yes
Subject to EU jurisdiction	No / not disclosed
Subject to China jurisdiction	No / not disclosed
Subject to Russia jurisdiction	No / not disclosed
Government data access risk	moderate
Five Eyes aligned	Yes
Adequate privacy jurisdiction	No / not disclosed

Governance

Publishes model cards	No / not disclosed
Publishes transparency reports	No / not disclosed
Has AI ethics board	No / not disclosed
Safety testing disclosed	Yes
Red-teaming program	No / not disclosed
Government contracts	No / not disclosed
Terms of service	https://www.suki.ai/terms
Privacy policy	https://www.suki.ai/privacy

Incidents on record

No incidents on file.

OWASP LLM Top 10 cross-walk

TrustAtlas dimensions that materially address each OWASP risk. Use to translate this vendor's compliance posture and data-handling stance into the application-security vocabulary your security team already uses.

LLM01	Prompt Injection User-supplied prompts manipulate model behaviour to bypass intended controls. SecurityTransparencyDependency chain
LLM02	Sensitive Information Disclosure Models leak PII, PHI, secrets, or proprietary data through outputs. Data handlingIP exposureJurisdiction
LLM03	Supply Chain Risk propagates from upstream models, datasets, plug-ins, and vendors. Dependency chainBusiness stabilitySecurity
LLM04	Data and Model Poisoning Adversarial training data or fine-tuning input degrades model integrity. Data handlingTransparencySecurity
LLM05	Improper Output Handling Downstream systems blindly trust model output, enabling injection downstream. IP exposureTransparency
LLM06	Excessive Agency Agents granted overbroad tool, identity, or permission scopes cause harm. Dependency chainTransparencyJurisdiction
LLM07	System Prompt Leakage System prompts containing secrets or logic are extracted via crafted input. Data handlingTransparency
LLM08	Vector and Embedding Weaknesses Vector stores and RAG pipelines leak or contaminate retrieved context. Data handlingSecurity
LLM09	Misinformation Hallucinated, biased, or fabricated outputs treated as authoritative. TransparencyRegulatory complianceBusiness stability
LLM10	Unbounded Consumption Cost, denial-of-service, and resource-exhaustion attacks against LLM endpoints. SecurityBusiness stability

Full framework reference: https://trustatlas.pages.dev/framework/owasp-llm-top-10

NIST AI RMF cross-walk

How each NIST AI RMF function is supported by the dimensions TrustAtlas scores.

GOVERN	Govern Establish AI governance structure: policies, roles, accountability. Regulatory complianceJurisdictionTransparencyBusiness stability
MAP	Map Establish AI context: intended purpose, use cases, capabilities, and risks. TransparencyDependency chainData handlingIP exposure
MEASURE	Measure Quantitative + qualitative risk assessment: testing, benchmarks, monitoring. SecurityData handlingTransparency
MANAGE	Manage Treat identified risks: mitigation, controls, incident response, lifecycle. Regulatory complianceSecurityDependency chainBusiness stability

Full framework reference: https://trustatlas.pages.dev/framework/nist-ai-rmf

Cited sources

Field	Source
data_handling.hipaa_baa_available	https://trust.suki.ai/ Verified 2026-05-18 by analyst
data_handling.third_party_sharing_details	https://www.getprosper.ai/blog/hipaa-compliant-voice-ai-providers-healthcare-guide Verified 2026-02-20 by analyst
security_compliance.hipaa_compliant	https://trust.suki.ai/ Verified 2026-05-18 by analyst
security_compliance.soc2_type2	https://trust.suki.ai/ Verified 2026-05-18 by analyst
vendors.founded_year	https://www.suki.ai/ Verified 2026-05-18 by analyst
vendors.funding_total_usd	https://www.deepcura.com/resources/suki-ai-review Verified 2026-04-10 by analyst

Questions to ask before signing

Vendor-agnostic baseline. Send these to the vendor and require written answers before contract.

01. Provide your most recent SOC 2 Type II report (with bridge letter if applicable).
02. Describe your training-data provenance and customer opt-out mechanics in writing.
03. List all sub-processors and confirm notification policy for material additions.
04. Confirm BAA availability and signed-BAA process if we process PHI.
05. Describe rate-limiting, quota, and circuit-breaker controls protecting our usage.
06. Provide your model card or equivalent disclosure documenting intended use, limitations, and known failure modes.
07. Describe your prompt-injection defences and red-team posture against OWASP LLM Top 10 risks.
08. Confirm data residency options and which sub-regions our data may touch.
09. Provide incident-response SLAs, security-event notification timelines, and the most recent pen-test report summary.
10. Confirm output ownership terms and any indemnification or copyright-shield programs available.
11. Describe acquisition-risk safeguards and what happens to our data on a change of control.
12. List foundation-model dependencies and how upstream-model risk is mitigated.

Methodology + caveats

Composite scores use the default-balanced weight profile (25% data handling, 20% IP exposure, 15% jurisdiction, 15% security, 10% regulatory compliance, 8% transparency, 5% business stability, 2% dependency chain). All facts are sourced from the vendor's own public disclosures, public regulatory filings, or reputable secondary reporting — see the cited sources table above. This pack is decision-support material, not legal advice or audit evidence.