← Back to directory

Databricks / Model configuration

Foundation Model APIs · pay-per-token · ap-southeast-2

Configuration dependent

The model is listed for Databricks-hosted inference in AWS Sydney with a pay-per-token endpoint. With cross-Geo disabled, processing is bounded to the Australia and New Zealand Geo.

The important distinction:This is an Australia–New Zealand geography, not Australia-only. Cross-Geo is enabled by default outside the US and EU unless the workspace has a compliance security profile.

Source review: 09 Nov 2026 · Exact model configuration not yet verified

Model coverage

databricks-gpt-oss-20b · system.ai.gpt-oss-20b

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 still need review.

Ownership and control

Databricks hosts the model. Sydney location does not establish Australian ownership or infrastructure operator domicile.

What to check before using it

  1. Use the Databricks pay-per-token endpoint in an ap-southeast-2 workspace.
  2. Have an account admin disable cross-Geo processing; confirm any compliance security profile defaults.
  3. Assess whether Australia and New Zealand as one processing boundary is acceptable.

Still to verify

Sources and supported claims

Documentation

Supported Foundation Model API models ↗

The Databricks-supported model list identifies the service name and indicates Databricks hosting unless a third-party Hosting field is shown.

Checked 2026-11-09 · Scope: this service profile
Documentation

Databricks model availability by region ↗

The Sydney region table lists databricks-gpt-oss-20b for pay-per-token use.

Checked 2026-11-09 · Scope: this service profile
Documentation

Databricks Geos and data residency ↗

Australia and New Zealand form one Databricks Geo; cross-Geo processing is enabled by default for many non-US/EU workspaces.

Checked 2026-11-09 · Scope: this service profile

Add to comparison →Suggest a correction

made. directory guide

Ask the directory

Ask about listed providers, Australian processing, model routes, sources, API access, billing or commitments.

The directory does not store chat history. Provider processing and retention terms still apply; avoid sharing confidential or personal information.

Start with a question

Compare what providers publish, including where the evidence leaves gaps.

0 / 1,600

Directory snapshot reviewed 9 November 2026. Follow the linked sources and check your account configuration before relying on a provider claim.