Skip to main content
Gitar can run every LLM call for your organization on your account instead of ours. Your provider agreement, your data boundary, your bill. Gitar still chooses the model for each task. You choose the account those calls are served from, and where they run.
Bring Your Own Model is available on the Enterprise plan. An organization admin sets it up under Settings -> Configuration -> Bring Your Own Model.

​
Choosing an option

One option serves traffic at a time. Switching keeps the credential the previous option used, so moving between them and back does not mean re-entering keys. Gitar never asks you to name a model. The three tiers it routes between are resolved per request, so a model upgrade reaches you with a Gitar deploy rather than a settings change on your side.

​
Anthropic

Paste an API key. Gitar stores it encrypted and calls api.anthropic.com with it. The key needs access to Opus, Sonnet, and Haiku. Verification tells you if a workspace restriction is in the way.

​
AWS Bedrock

Bedrock is the option to pick when a compliance requirement says where inference may run. Gitar assumes a role in your account per request through AWS STS, so no standing credential of yours is ever stored with us.
1

Pick your residency geography

Gitar routes to a geographic inference profile, so requests stay inside that geography’s regions on the AWS backbone.Your service control policies have to allow every region in the geography, since a request may land in any of them.
2

Create the role in AWS

Open Create the role in AWS in the card. It carries your external ID and both policies to copy, and it stays available afterwards for whenever you rebuild the role or audit who can assume it.The role’s name has to start with gitar-bedrock-. Gitar’s permission to assume roles is scoped to that prefix, so a role named anything else cannot be assumed however its trust policy reads.The external ID is fixed for your organization and never changes. It is not a secret, but the role must require it. That condition is what stops anyone else who learns your role ARN from asking Gitar to assume it.
3

Enable Anthropic model access

In your Bedrock console, enable Anthropic model access for the geography’s regions. Listing models is not the same as being allowed to call them, which is what verification checks.
4

Paste the role ARN and verify

Paste the ARN into the card and verify the connection.

​
Global cross-region inference

Off by default. Global inference routes worldwide, including outside your geography, so turn it on only if throughput matters more than residency. With it off, a model your geography cannot serve fails rather than leaving the geography.

​
Gateways

LiteLLM, Portkey, and OpenRouter are configured the same way: the endpoint, and a credential for it. Gitar speaks the Anthropic Messages format to all three. Nothing else is asked of you. Which header the key rides in, what path your gateway serves, and what its catalog calls each model are all Gitar’s to know.

​
LiteLLM

Enter the https:// origin your proxy serves on, no path, plus a virtual key. Gitar uses your proxy’s Anthropic passthrough route, so nothing in your config.yaml has to be named here. A proxy that is not reachable from the public internet needs network access arranged first.

​
Portkey

Enter your Portkey API key and the provider slug you want the traffic routed through. The slug is the name you gave the integration in Portkey.
A slug routes to whichever provider you wired up behind it, so the models Gitar needs have to be reachable through that provider. Verification calls each one and names any that are not.

​
OpenRouter

Enter an API key. Nothing else, since OpenRouter hosts the endpoint and Gitar knows its catalog’s name for each model. OpenRouter is a broker rather than a boundary. If you are here for a data-residency requirement, Bedrock is the option that enforces one.

​
Something else

Running a gateway that is not listed? Contact support. The endpoint is what we certify, so a gateway speaking Anthropic passthrough is usually a short conversation.

​
Verifying

Every option is verified the same way, and Save stays disabled until verification passes. Gitar sends one tiny request per model it needs, from your account, and reports what came back for each. A request is what gets verified, on purpose. Every provider has a cheaper check that passes when real traffic would not. Bedrock lists inference profiles whether or not you enabled model access. A gateway resolves a model name against a catalog rather than against your key. A key can be valid while scoped to a workspace missing a model. Editing any field after a pass clears it, so what you save is what was proven.

​
After it is live

Gitar re-checks the configuration in the background and shows a card on your dashboard when your account stops serving. Reviews are held rather than quietly routed back through Gitar’s account, so nothing leaves your boundary without you choosing it. Held work resumes on its own once the configuration serves again.

​
What Gitar stores

An Anthropic or gateway credential is encrypted in AWS Secrets Manager, and the configuration keeps only the name of that secret. A Bedrock configuration stores no credential at all: the role ARN, geography, and external ID are all non-secret, and the credential is minted per request by STS. Clear removes the configuration and every credential stored with it, and returns your organization to Gitar’s own account.