Open Dental · FinOps Profile

Opendental Finops

FinOps view of Open Dental API spend. Open Dental's REST API is billed per location: a Developer Key plus a per-customer Customer Key must be enabled before charges apply, and billing stops when a key is disabled. The dominant cost driver is therefore the number of active locations / enabled customer keys rather than per-request metering. Open Dental does not publish public per-location dollar amounts and negotiates pricing with high-volume developers. A free test database exists for pre-production development. The Local API / API Service option runs at the practice workstation and is not metered or throttled through Open Dental's cloud, shifting cost to on-premises infrastructure rather than a per-call cloud charge.

Opendental Finops is the FinOps profile for Open Dental on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in USD, on a monthly cycle, and pricing category subscription.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Dental, Practice Management, Healthcare, FinOps, and Cost Management.

Category: Healthcare and Practice Management Pricing: Subscription Billing: Monthly FOCUS v1.3
DentalPractice ManagementHealthcareFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchase

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Open Dental Software
PricingCategory
Subscription
ProviderName
Open Dental Software
PublisherName
Open Dental Software
ServiceCategory
Healthcare and Practice Management
ServiceName
Open Dental API

Meters

active_locations
Unit: locations
Number of locations with an enabled API Customer Key; the primary per-location billing driver.
enabled_customer_keys
Unit: keys
Count of enabled per-customer Customer Keys; billing starts on enable and stops on disable.
api_requests
Unit: requests
Volume of cloud REST API requests; not directly billed but bounded by permission-tier throttling.
local_api_usage
Unit: requests
Requests handled by the un-throttled Local API / API Service at the practice workstation (on-premises cost, no cloud charge).

Sources