Browser
The authorized user begins and reviews the workflow.
Security designed to be understood and verified
Trust should be inspectable.
Molaris creates clinical drafts, keeps the clinician in control, and can send approved content to Open Dental. This page maps the current boundaries plainly.
This is an explanatory system map, not a certification, audit report, or promise that a particular agreement is automatically included.
The shortest accurate view of the system, from practice browser to approved destination.
Where information moves.
Vercel serverless
Server-side requests proxy connected services.
Supabase
Application rows use practice-scoped access policies.
Configured models
OpenAI handles transcription; OpenAI or Anthropic can draft notes.
Open Dental
Only the relevant user action can initiate writeback.
Generation, approval, and filing are deliberately separate states.
The model drafts. The clinician decides.
Once approved, the record locks. A later correction creates a separate pending amendment; the signed original remains unchanged.
If Open Dental writeback does not complete, the signed content remains available in Molaris and the failure is reported instead of being presented as success.
These application controls complement, not replace, practice device, workforce, consent, and access policies.
Current control points.
- Practice scoping
- Supabase row-level security limits application records to the signed-in practice context.
- Session and recovery data
- Open Dental launch links carry only the minimum identifiers needed to open the right chart (PatNum and appointment number) over HTTPS; the patient name is resolved after sign-in, never in the URL. Browser authentication and periodontal recovery state are tab-scoped and cleared at sign-out.
- Provider credentials
- Molaris service secrets (model provider, email, SMS, billing, and the Open Dental developer key) live in server-side environment variables. Your practice's own Open Dental customer key is stored in your practice record, scoped to your signed-in team by row-level security.
- Signed-note integrity
- Approved sections are database-guarded against mutation. Approval and amendment events are append-only audit entries after the included migration is applied.
- Referral acknowledgment
- Opening an email link is read-only. A human must press Confirm receipt, preventing mail scanners from acknowledging a referral.
- Open Dental outcome
- The interface distinguishes the preferred destination, an explicit fallback, and a failed request.
The exact provider set depends on the features and model configuration a practice uses.
Connected providers, by job.
VercelHosting and serverless request handling.
SupabaseAuthentication, application records, storage, and row-level access controls.
OpenAITranscription and, when configured, note drafting.
AnthropicNote drafting when selected.
ResendReferral and application email.
TwilioOptional patient-form SMS and AI phone answering (voicemail transcription).
StripeCheckout and billing status.
Open Dental APIDestination for user-approved clinical workflows.
Before sending protected health information, confirm the provider configuration, retention terms, contractual requirements, and any business associate agreements required for your practice. Review the Privacy Policy and Terms; executed agreements control over this page.
These are deployment questions, not fine print to defer until after launch.
Confirm before clinical use.
- Retention
- Ask for the periods that apply to audio, transcripts, drafts, operational logs, and backups in your configuration.
- Deletion
- Confirm what can be deleted, timing, backup limitations, and the separate status of content already written to Open Dental or another system.
- BAA scope
- A signed BAA is required and included as part of onboarding for every production account. Confirm covered services, parties, subprocessors, and effective date at signing.
- Incident process
- Ask for the current reporting route, response process, and contractual notification terms.
Inspect the approval boundary yourself.
The demo uses fictional data and exposes draft, review, approval, locked-note, amendment, destination, and failure states.
Open the live demo →Visit audio
Recordings exist to produce your documentation. Audio is encrypted in transit and at rest, kept attached to its note so the provider can replay it during review, and is never used to train shared or third-party models. Practices can request deletion of any recording — or all of them — at hello@getmolaris.com; deletion is confirmed in writing.
Subprocessors
Molaris uses a small set of vendors to run the service: Supabase (database and authentication), Vercel (hosting), a HIPAA-eligible transcription provider under BAA, Stripe (billing — never receives patient data), and Resend (transactional email — patient emails carry links, not clinical content). Business Associate Agreements are maintained with every vendor that touches protected health information.
Data export & deletion
Email hello@getmolaris.com from your account address to request an export or deletion. We verify the request with the practice owner, complete it within 30 days, and confirm in writing. Signed clinical records may be retained where law or your own record-keeping obligations require it.
Reporting a vulnerability
Found something? Email hello@getmolaris.com with SECURITY in the subject — we read those first.