Oralstack

FAQ

Common questions, qualified answers.

Questions clinic owners, office managers, and operators raise during evaluation. If your question isn't here, email hello@oralstack.com — we reply within one working day.

Pricing & contracts

  • What does Oralstack cost?

    $200 per clinic per month, flat, during pilot. SGD or USD invoiced at parity for now. Three months of hands-on onboarding included. No per-seat charges, no per-feature gating, no setup fees.

    Multi-clinic groups: pricing scales linearly per clinic. Group discounts on request once pilot is established. Full pricing →

  • Is there a contract or minimum term?

    No long-term contract during pilot. We invoice monthly. You can cancel any time and we hand back a full export of your data within five working days.

  • What happens after the pilot period?

    Pilot pricing is locked at $200/clinic/month for the first 12 months from kickoff. After that we'll tell you what GA pricing looks like with at least 60 days' notice; you can stay or leave.

Migration & onboarding

  • How long does migration take?

    Three weeks from kickoff to live, in the model we run. Week 1 is audit and prep; week 2 is cutover; week 3 stabilises. Read the playbook → Clinics that try to keep their old system running in parallel consistently take 6–8 weeks instead.

  • Will I lose patient data?

    No. We migrate patient records, appointment history (12 months minimum), treatment records, and outstanding A/R balances field-for-field. Most fields map 1:1 from legacy PMS schemas; the ones that don't get reviewed in the week-1 audit. The only data we don't carry across is data the clinic explicitly opts out of (typically very old recall lists).

  • Do you support a fallback during cutover?

    We deliberately don't recommend running both systems in parallel — it's the single biggest cause of stuck migrations. We do keep your old PMS read-only for historical lookups for as long as you want, but the source of truth flips to Oralstack at the cutover date.

  • Who handles training?

    We do, directly. A 30-minute walkthrough on day one, then real shift coverage with someone available on chat for questions for the first week. Front desk staff learn by doing — multi-day classroom training, in our experience, doesn't stick.

Security & compliance

  • Where is my data hosted?

    Singapore region (asia-southeast1) on Google Cloud. Your patient records do not leave the Singapore region without explicit cross-border consent. Security posture →

  • Are you PDPA-compliant?

    Yes. PDPA-compliance is built into the data model — region-hosted, tenant-isolated via Postgres row-level security, audit logs by default with full access traceability, encryption in transit and at rest. We are not the data controller; the clinic remains the controller and we operate as the data intermediary.

  • Are you HIPAA-aware?

    We design with HIPAA principles in mind (access control, audit logging, encryption, breach notification readiness) but we are not a US-jurisdiction product. Clinics with US-jurisdiction patient data should evaluate whether our model fits their specific HIPAA requirements. We'll happily walk through the mapping.

  • Can I see audit logs?

    Yes. Every read and write is logged with user, clinic, resource, and timestamp. The log is queryable per-clinic. What auditors actually look for →

Integrations & technical

  • Which sensors and imaging hardware do you support?

    DICOM viewer in the patient chart, with sensor-bridge integration across Carestream, Dexis, Sopro, and Schick. We don't sell hardware — bring your existing sensors. Full integrations →

  • What about WhatsApp recall messaging?

    We use the WhatsApp Business API with Singapore-region routing for templated recall and confirmation messages. Two-way conversations are audit-logged with delivery and read receipts.

  • Can I export my data?

    Anytime. CSV and JSON exports are first-class — patient records, appointment history, billing history, recall lists, audit logs. We'll never charge for an export.

  • Do you have an API?

    Not publicly yet. We integrate where it makes sense (sensor-bridge, WhatsApp Business, payment processors). A documented public API is on the roadmap once integration patterns stabilise across the pilot cohort.

About Oralstack

  • How big is the team?

    Small and engineering-led. The person who writes the schedule code is the person on the demo call and the person on the support channel when something breaks. About →

  • Where are you based?

    Singapore. APAC-first. Our cornerstone customer is also in Singapore (DFI Synergy, a 3-chair general + hygiene practice).

  • What if Oralstack goes out of business?

    A reasonable thing to ask of any early-stage SaaS. Two practical answers: (1) you can export your full dataset (CSV/JSON) at any time — there's no lock-in, (2) we work with clinics on a data-handover plan as part of every pilot agreement, including a field-mapping document so a successor PMS can ingest your Oralstack data without a re-keying project.

  • Why not use Plato or Open Dental?

    Both are reasonable for the right clinic. vs Plato → vs Open Dental → All comparisons →