Start here

Choose your AI provider (and bring your own key)

Each org picks the one AI provider that receives its data. Optional: use your own API key.

5 min read

How it works

  • Your org uses exactly one AI provider. Only that provider receives your org’s AI requests (ticket text, logs, code snippets, transcripts, screenshots).
  • Available providers: Anthropic (Claude, the default), OpenAI (GPT), xAI (Grok), Google (Gemini), DeepSeek and Moonshot AI (Kimi).
  • There is no silent fallback. If your provider has an outage, the request fails with an error; it is never rerouted to another provider.
  • China-based providers (DeepSeek, Kimi) are off until an org admin opts in and accepts a written acknowledgement. The opt-in is recorded with who and when.
  • Local models through Ollama never leave your computer and are always allowed.
  • Every change is kept in the org’s history and audit log.

In the app

  1. Open Settings and find AI provider (also reachable from first-run setup).
  2. Pick the provider your org approved.
  3. Optional: paste your own API key. Arcus tests the key before it is saved. The key is encrypted at rest and never shown again.
  4. You can switch chat models anytime inside a case when your org allows it.
First-run welcome and role picker in Arcus
First-run setup includes AI provider before your sample investigation.

API (admins)

Org owners and admins can also call the API with an Arcus session token:

# See the current choice and the list of providers (any member)
GET  https://arcus-api-production-a4fc.up.railway.app/api/v1/ai-provider

# Switch provider (owner/admin)
PUT  /api/v1/ai-provider            {"provider": "openai"}

# China-based providers need the opt-in first, with the exact text from GET .china_ack
PUT  /api/v1/ai-provider/china-opt-in  {"enabled": true, "ack": "<china_ack text>"}

Where this is written down

The provider choice matches section 4 of the DPA and the subprocessor list. See Security, DPA and subprocessors.