Databricks / Model configuration
Foundation Model APIs · pay-per-token · ap-southeast-2
Configuration dependentDatabricks lists a hosted Gemma endpoint in AWS Sydney for pay-per-token use. When cross-Geo is disabled, the processing boundary is Australia and New Zealand together.
Source review: 09 Nov 2026 · Exact model configuration not yet verified
Model coverage
databricks-gemma-3-12b · system.ai.gemma-3-12b
API access
Databricks workspace in supported region and API token
Billing
Pay-per-token; no capacity commitment; per-model price not publicly specified
Capacity commitment
No reserved capacity required for this service category.
Storage
Databricks data processing follows the workspace Geo for designated services when cross-Geo is disabled. Australia and New Zealand form one Geo.
Retention and training
Model-specific retention and workspace logging settings require review.
Ownership and control
Databricks hosts the model. Australian infrastructure location does not establish Australian corporate ownership.
What to check before using it
- Use the Databricks pay-per-token endpoint in an ap-southeast-2 workspace.
- Have an account admin disable cross-Geo processing.
- Check current quota, features and whether the AU/NZ boundary is acceptable.
Still to verify
- No public model-specific input/output rates found
- Strict Australia-only processing is not established by this Geo
- Workspace-tier quota and retention details
Sources and supported claims
Supported Foundation Model API models ↗
The supported model list gives the Databricks endpoint and model service name.
Checked 2026-11-09 · Scope: this service profileDatabricks model availability by region ↗
The Sydney region table lists databricks-gemma-3-12b for pay-per-token use.
Checked 2026-11-09 · Scope: this service profileDatabricks Geos and data residency ↗
Cross-Geo disabled bounds designated-service processing to the workspace Geo, which groups Australia and New Zealand.
Checked 2026-11-09 · Scope: this service profile