QuantCDN and QuantGov

Quant runs on two platforms: QuantCDN and QuantGov. Both platforms have the same products. Some cache, purge and domain behaviour differs; see What differs on QuantGov. Use the platform that your organisation signed up to.

QuantGov adds restrictions for Australian Government use and is IRAP assessed. For example:

• AI features use Australian-resident models only.
• Domain and certificate setup shows a DNS-validation step.

Which platform is my project on?

Your project is on the platform whose dashboard you sign in to.

The dashboard is the only reliable way to tell. Do not decide the platform from response headers, DNS records or IP addresses.

	QuantCDN	QuantGov
Dashboard	https://dashboard.quantcdn.io	https://dash.quantgov.cloud
Content API	https://api.quantcdn.io/v1	https://api.quantgov.cloud/v1
Platform API (Quant Cloud, qc, GitHub actions)	https://dashboard.quantcdn.io/api/v3	https://dash.quantgov.cloud/api/v3

API keys and tokens belong to one platform. A key from one dashboard does not work on the other platform.

Which host does each tool use?

Tool	Setting	QuantCDN value	QuantGov value
Content CLI (quant)	endpoint (quant init, quant info -e)	https://api.quantcdn.io/v1	https://api.quantgov.cloud/v1
Content CLI quant rules	QUANT_BASE_URL (with an API token in QUANT_API_TOKEN)	https://dashboard.quantcdn.io/api/v2	https://dash.quantgov.cloud/api/v2
Cloud CLI (qc)	qc login (choose the platform), then qc platform switch	quantcdn	quantgov
Quant Cloud GitHub actions	base_url	https://dashboard.quantcdn.io (default)	https://dash.quantgov.cloud
Deploy action	api-base-url	https://dashboard.quantcdn.io/api/v2	https://dash.quantgov.cloud/api/v2
Terraform and Pulumi	base_url / baseUrl	https://dashboard.quantcdn.io	https://dash.quantgov.cloud

The Terraform and Pulumi providers add the API path themselves. Set only the dashboard host.

Cloud CLI

The qc login command does not take a platform flag. To sign in, run qc login and choose QuantGov Cloud or Quant Cloud when the CLI asks. The CLI uses https://dash.quantgov.cloud for QuantGov and https://dashboard.quantcdn.io for QuantCDN.

To skip the question, pass the dashboard host:

qc login --endpoint https://dash.quantgov.cloud

Note

A login with --endpoint is saved as a platform named custom, not as quantgov. To get the standard quantgov platform name, choose it from the list.

The CLI keeps one login for each platform. Only one platform is active at a time, and every command uses the active platform. Manage the platforms with these commands:

qc platform list       # list the platforms you signed in to
qc platform current    # show the active platform
qc platform switch     # change the active platform

Run qc platform current before you act, to confirm that the CLI points at the correct platform. See Cloud CLI platform commands.

GitHub actions

The Quant Cloud actions use the QuantCDN platform when you do not set base_url. For a QuantGov project, set base_url on each action to the bare dashboard host, https://dash.quantgov.cloud. The bare host works for every Quant Cloud action. The v4 actions also accept the /api/v3 form:

- uses: quantcdn/quant-cloud-environment-state-action@v4
  with:
    api_key: ${{ secrets.QUANT_API_KEY }}
    organization: my-org
    application: my-app
    environment: production
    base_url: https://dash.quantgov.cloud

For the static-site deploy action, set api-base-url to https://dash.quantgov.cloud/api/v2.

What differs on QuantGov

The restrictions exist to meet Australian Government requirements. The products are the same, but some behaviour differs.

• AI: only Australian-resident models are available.
• Domains and certificates: domain setup shows a DNS-validation step. Create the DNS records it shows before the certificate becomes active.
• Cache and purge: some purge and cache behaviour differs. For example, on QuantGov a trailing * in a purge path works as a prefix (/blog/* purges every path under /blog/).