> ## Documentation Index > Fetch the complete documentation index at: https://agent-observability-docs.splunk.com/llms.txt > Use this file to discover all available pages before exploring further. # Integrations overview > Configure supported model providers, understand credential scopes, and identify deployment-managed infrastructure. The **Integrations** page shows the external services available to Luna Studio. Some cards accept runtime credentials in the app, some are marked **Coming soon**, and infrastructure cards are read-only because they are managed as part of your deployment. ## What integrations are for Luna Studio works with two kinds of integrations: * **Runtime integrations** - accept personal or workspace-scoped records for LLM providers and Splunk Agent Observability. * **Deployment integrations** - connect shared infrastructure and services, including the training platform, object storage, and PostgreSQL. You need at least one supported LLM provider for synthetic generation and LLM-based labelling. ## LLM personal overrides and workspace defaults LLM provider credentials are not always shared with the entire organization: * A **personal override** is used only for your account. * A **workspace default** is used when you do not have a personal override. * Only workspace administrators can create, update, or remove workspace defaults. A non-admin can add and manage a personal override. At runtime, Luna Studio resolves each LLM provider independently: your personal credential for that provider takes precedence, followed by its workspace default. The source badge on an LLM card describes the shared `llm_provider` record returned to the UI, not the source of every provider key inside it. In a mixed-scope setup, do not use that single badge to infer the effective source for each provider. ## Runtime integration types ### LLM providers The current UI can configure four LLM providers: * [OpenAI](/luna-studio/ui/integrations/llm-providers#openai) * [Anthropic](/luna-studio/ui/integrations/llm-providers#anthropic) * [Google Gemini](/luna-studio/ui/integrations/llm-providers#google-gemini) * [Groq](/luna-studio/ui/integrations/llm-providers#groq) Other provider cards in the catalog are marked **Coming soon** and cannot accept credentials yet. See [LLM providers](/luna-studio/ui/integrations/llm-providers#coming-soon-providers) for the current list. For setup guidance, see [LLM providers](/luna-studio/ui/integrations/llm-providers). ### Splunk Agent Observability The [Splunk Agent Observability connection](/luna-studio/ui/integrations/splunk-ao) unlocks platform-level features such as importing datasets from Splunk Agent Observability and registering eligible evaluators back to Splunk Agent Observability. Although the UI accepts personal and workspace-scoped `galileo_api` records, the current dataset-import and registration consumers ignore both scopes and use the deployment-configured Splunk Agent Observability API URL and key from the backend. This is a current-release runtime limitation rather than an intended permanent integration boundary. ## Training platforms Luna Studio also supports training platform integrations for the infrastructure that runs fine-tuning jobs: * `Vertex AI Pipelines` * `AzureML Pipelines` * `SageMaker Pipelines` * `Kubernetes` These are **deployment-level integrations**, not settings users configure in the Luna Studio UI. The training platform is chosen when Luna Studio is deployed and is fixed for that deployment. The **Training platform**, **Object storage**, and `Postgres` cards therefore appear as managed, read-only integrations. See [Availability and deployment](/luna-studio/ui/availability) for how Splunk Agent Observability provisions Luna Studio into your cluster. ## Where to go next Choose the right provider setup for your team and see what credentials you'll need. Understand the current credential path for Splunk Agent Observability-backed features.