Answers for the clinic decision in front of you.

$200 per clinic per month, flat, during pilot. SGD or USD is invoiced at parity for now. Three months of hands-on onboarding is included. There are no per-seat charges, per-feature gates, or standard clinic-setup fees. Legacy-record migration, bespoke imports, and optional connections are scoped separately before kickoff.

Multi-clinic pricing scales per clinic; group terms are reviewed after the pilot is established. Review full pricing.

There is no long-term contract during pilot; invoices are monthly. Cancellation and data-handover terms are confirmed in each pilot agreement, including which records and formats are in scope.

Pilot pricing is locked at $200 per clinic per month for the first 12 months from kickoff. After that, we will share any general-availability pricing with at least 90 days' notice; the clinic can stay or leave.

Oralstack is a small, engineering-led team. The clinic works directly with us through the guided pilot: we map the clinic day, coordinate configuration and review, train the agreed roles, and support the documented scope. The clinic owns its operating decisions and go-live approval; responsibilities and support channels are recorded in the pilot plan. See how we work.

Singapore, with an APAC-first operating context. Product decisions start with the front-desk, clinical, billing, and data-handling realities of dental clinics in this region.

The timeline depends on how the clinic starts. A new clinic, a paper-led team, a record move, and a Plato-connected clinic require different configuration, data review, and training. We scope the sequence after an initial audit rather than promising a fixed rollout window. Compare starting paths.

Not by default. A standalone pilot defines which patient, schedule, clinical, billing, and audit records Oralstack will own and which data will be imported. Bulk record moves and paper-record conversion are scoped separately and require human review. In a Plato-connected clinic, Plato remains authoritative for the reviewed connector paths named in the agreement.

Plato remains authoritative for the connected record paths. Oralstack does not swap in rich demo records when a production read fails, and a locally staged fallback is never described as a delivered writeback. Plato-backed reschedules remain staff-reviewed and are applied in Plato before they are resolved in Oralstack.

We do, directly. Training follows the roles and workflows the clinic plans to use, from reception and chairside care to checkout and manager review. The schedule and support window are agreed during pilot planning.

Both are reasonable for the right clinic. Oralstack can be configured as the clinic's primary system through a guided pilot, or work through an optional reviewed Plato connection. The right path depends on the records to retain, workflows to move, and tolerance for a staged rollout. Compare starting paths.

Not as generally available features. Current patient care supports clinical-media upload, note linking, annotations, and archiving. DICOM viewing, device ingest, measurements, and the X-ray bridge remain controlled rollouts, so we do not advertise specific sensor-vendor support. Review connection status.

Clinics with an approved Meta connection can use the staff inbox for manual two-way conversations. Recall settings, campaigns, audiences, and touch queues are available for staff review. Automated reminders, live recall dispatch, WhatsApp Flows, birthday messages, and SMS remain outside current live claims.

Export availability depends on the workflow; examples include periodontal exports, operational reports, and receipt records. Broader data-handover scope, format, timing, and operational availability are confirmed in the clinic agreement. We do not advertise one-click export for every record in the product.

Not a public API. Optional Plato connection work uses reviewed connector paths. HitPay, SmartCMS, NEHR, DICOM and sensor ingest, teleconsultation, and automated external messaging remain controlled or disabled—not public live integrations.

Core production services are configured in the Singapore region (asia-southeast1) on Google Cloud. Clinic-specific connectors and external subprocessors are reviewed as part of setup rather than implied by the core hosting statement. Review the security posture.

Product controls include Singapore-region hosting, tenant scoping with PostgreSQL row-level security, encryption requirements, origin checks, and chained audit evidence. For clinic-instructed processing, the clinic is generally the organisation/controller and Oralstack acts as data intermediary to the extent stated in the applicable data-processing terms; roles can differ by data flow. These controls support evaluation; they are not a blanket legal certification.

We account for relevant access, audit, encryption, and incident controls, but Oralstack is not a US-jurisdiction product and does not claim HIPAA certification or attestation. Clinics handling US-jurisdiction patient data should evaluate whether the documented controls fit their specific legal requirements.

Supported clinical and operations workflows create tenant-scoped audit and access records for review. See the security and audit evidence.

Each pilot agreement defines a data-handover plan for Oralstack-owned records, including scope, format, and timing. Plato remains the primary record for agreed paths in connected clinics. We do not promise that every successor system can ingest every Oralstack field without mapping work.