Our infrastructure. Our model. Your patients’ data never leaves either.
Patient data is PHI the moment it touches an agent. We built the compliance story around that fact first — before we built a single agent.
StackFloss runs on infrastructure we own and operate end-to-end — not a shared multi-tenant cloud service layered with third-party BAAs. Patient data never leaves an environment we control. Full HIPAA compliance is a property of the system, not a contract we’re hoping a vendor honors.
This isn’t a general-purpose AI repurposed for dentistry. StackFloss runs its own model, trained specifically for dental practice operations — denial patterns, insurance workflows, patient communications. Patient data never reaches an outside AI vendor’s servers, and a model built for this one job outperforms a generalist at it.
General-purpose AI, someone else’s cloud
Patient data leaves your systems and the practice’s environment entirely, processed by an AI built for everything and everyone, run by an outside vendor, governed by a BAA you have to trust them to honor.
StackFloss
Patient data is processed by our model, on our infrastructure, purpose-built for dental practice operations — nothing handed off to a third-party AI vendor, ever.
What always routes to a human
Every agent ships with guardrails. These are illustrative of the kind of thing that stays human-reviewed regardless of which autonomy setting you choose: