AI regions and bring your own key

There are two reasons an organization supplies its own AI credentials, and they are worth separating because only one of them is about compliance.

The first is that it is how you pay for your AI. On the free edition this is the only way AI runs: you connect your own Anthropic key, your provider bills your account directly, and DeltaVault applies no allowance and takes no cut. Until a key is saved, AI operations fail with an error telling you to add one.

The second is data residency. If your compliance posture says AI inference must stay inside a specific country, DeltaVault can pin it there, and serving a region may require credentials for that region’s provider. Regions are a separate feature with its own availability, covered in the second half of this page.

If you are here because AI is not working on a free organization, you only need the next section.

Connect your Anthropic key

You need the editor or organization administrator role to change AI settings.

1. Open Settings, then Artificial Intelligence.
2. Find Provider keys and region, and the Anthropic card inside it.
3. Select Set key.
4. Paste your Anthropic API key. Keys begin with sk-ant-.
5. Select Save.

DeltaVault makes one live call to Anthropic to check the key before storing it, so a typo fails in the dialog rather than on your next AI run. The key is encrypted at rest and is never shown again: the card displays a fingerprint, the date it was added, and when it was last used.

Once a key is saved the card offers three actions:

• Replace key saves a new one over the old.
• Test key makes a live call and tells you whether the stored key still works, which is faster than waiting for real work to fail. It records the result as well as showing it, so a rejection here also clears or raises the failure banner.
• Remove deletes the stored key. On an organization that has no platform fallback, removing the key stops AI working until you add another.

What you are billed for

Your provider account is billed directly for what your organization spends, at your provider’s rates. There is no DeltaVault credit allowance, no buffer and no top-up packs on your own key, because there is nothing of ours to draw down. The credit figures described in AI credits apply to organizations running on DeltaVault’s platform key.

Embeddings are the exception, and they are not billed to you at all. Vector search, knowledge retrieval, recommendations and help search run on DeltaVault infrastructure whatever key you supply.

When a key stops working

A rotated or revoked key comes back as an authentication failure. The credentials card shows the failure for 24 hours after it happens, and Test key re-checks on demand. Replace the key and save; nothing else needs resetting.

If your organization has no platform fallback, a key that cannot be decrypted or that is missing entirely is a hard failure rather than a quiet degradation. The error names the remedy and points at this card.

If the Anthropic card is not there

The card appears only for organizations entitled to bring their own key. There is no separate AI credentials page and no navigation link to look for: the card is inside Settings, under Artificial Intelligence. If it is absent, ask your organization administrator to check with DeltaVault.

Choose an AI region

AI regions are not switched on for every organization. The feature is enabled per organization and also requires activation by DeltaVault, so the AI region control may not appear in your settings. It is not part of the free edition. If you need regional inference and cannot see the control, contact DeltaVault to have it enabled.

1. Open Settings, then Artificial Intelligence.
2. In the AI region dropdown, pick your region. Each option shows a one-line summary of where inference runs.
3. The change applies to your whole organization immediately: the next AI request uses the new region.

Selecting a region other than Global shows the full residency statement for that region, including exactly what stays regional and what does not.

What the region covers (and what it does not)

Your region pins Claude reasoning calls: Ask AI, skill runs, and AI suggestions all run inside the region’s boundary. For Australia, that means Amazon Bedrock in Sydney, using inference profiles that keep requests inside Australian geography.

Embeddings are the carve-out. Embeddings and the features built on them (vector search, knowledge retrieval, recommendations) remain on global infrastructure regardless of your region. The region settings state this explicitly, so there is no ambiguity about what your residency posture covers.

Set up Amazon Web Services credentials for Australia

The Australia region runs Claude through Amazon Bedrock. If DeltaVault has not provisioned platform credentials for your region, you bring your own: the readiness notice under the region dropdown tells you when that is required.

This card appears only once you have selected a region that needs it, so an organization without regions never sees it.

Before you start, you need an Amazon Web Services account with Amazon Bedrock access in Sydney (ap-southeast-2) and Claude model access enabled there, plus an access key for a user or role allowed to invoke Bedrock models.

1. In Settings, then Artificial Intelligence, find the Amazon Web Services card.
2. Select Set credentials.
3. Paste the access key identifier and the secret access key, then select Save.

DeltaVault verifies the credentials against Amazon Bedrock before saving, so a typo fails right there in the dialog. Once saved, credentials are encrypted at rest; the card shows a fingerprint, when they were added, and when they were last used. AI usage with your own credentials is billed directly to your Amazon Web Services account.

When AI calls fail

A regional organization’s AI either runs in its region or fails with one of these errors. Nothing falls back silently. Each one arrives with an ai: prefix in front of the text quoted here.

“AI region Australia requires Amazon Web Services credentials. Add them in Settings → AI”: your region has no working credentials. Add or replace them in the Amazon Web Services card, which the message calls Settings then AI and the navigation calls Settings → Artificial Intelligence.

“your Amazon Web Services credentials were rejected. Open Settings → AI to update them”: the saved credentials no longer work. The access key may have been rotated or revoked, or it lost permission to invoke Bedrock models. The card flags the failure; select Replace credentials and save a working key.

“model … is not available in AI region …”: the AI feature asked for a Claude model your region does not offer. The error lists the models the region supports. Regions gain models over time; if a feature you need is blocked on this, contact support.