Basic Configuration¶

After installation, you'll need to configure the basic settings for Pixee Enterprise Server. These settings include the domain name, protocol, and ingress configuration.

Configuration¶

Embedded ClusterHelm Deployment

Configuration is done through the admin console configuration page available after installation at:

https://<domain name or ip address>:30000

When you load the admin console page you will be prompted to enter your admin password. The first time configuring after installation you will be directed through a workflow that will step you through configuring Pixee Enterprise Server.

Basic Settings¶

The settings under the Basic Settings section all require your input. Here you will find the required settings for the Pixee Enterprise Server domain name, TLS options, and AI model provider settings. Make sure you review all of these settings for completeness and accuracy.

Domain¶

Enter the domain name you have assigned to your Pixee Enterprise Server. If you have not assigned a domain name you can enter the public IP address of your Pixee Enterprise server instead but this will limit your TLS options.

Protocol¶

Select the protocol that will be used for your Pixee Enterprise Server. If you select HTTP, ingress traffic to your Pixee Enterprise Server will be un-encrypted. The HTTP option is for quick testing configurations or when you have an external system like an App Gateway or Load Balancer that is terminating TLS instead of Pixee Enterprise Server. If you have an external system (i.e. App Gateway, Load Balancer, etc.) acting as a reverse proxy to your Pixee Enterprise Server, make sure you provide reverse proxy settings in the Advanced Settings section. If you select HTTPS, ingress traffic to your Pixee Enterprise Server will be encrypted, and you will be prompted to configure TLS.

Authentication¶

Pixee Enterprise Server currently supports the following OIDC providers:

Select the OIDC provider you want to use for authentication. If you select Embedded Provider, Pixee Enterprise Server will use its built-in OIDC provider. For other providers, you will need to provide the necessary configuration details such as client ID, client secret, and issuer URL.

See Authentication for more information on specific provider configuration.

AI Providers¶

Choose LLM provider and fill in the credentials. Pixee uses two models — a Reasoning Model for complex analysis and a Fast Model for quick tasks (they can be the same). Sensible defaults are pre-filled.

Supported providers: OpenAI, Azure AI Foundry, Anthropic, Azure Anthropic. OpenAI and Anthropic only require an API Key; the Azure variants also require an Endpoint.

For OpenAI-compatible providers such as Databricks, select OpenAI and set the Endpoint to your workspace serving URL. See Databricks AI.

See AI Providers for per-provider walkthroughs, web search models, and SCA / deep research configuration.

Create a values.yaml file and configure the following basic settings:

Domain¶

Set the URL where your Pixee Enterprise Server will be accessible (if no domain name is available, use an external IP address):

global:
  pixee:
    domain: "<your pixee enterprise server domain name>"

Protocol¶

Set the HTTP protocol (http or https) used to access your Pixee Enterprise Server:

global:
  pixee:
    protocol: "https"

Info

If you are using TLS to secure traffic to your Pixee Enterprise Server set this to https, even if you terminate TLS outside your cluster.

Ingress¶

If you are using an ingress controller, you can enable and configure the Pixee Enterprise Server ingress resource as follows:

platform:
  proxy:
    # enable proxy configuration with ingress to allow headers from the ingress controller
    enabled: true
  ingress:
    enabled: true
    className: "<your ingress controller class name (i.e. nginx, gce, etc)"
    hosts:
      - host: "<your pixee enterprise server domain name>"
        paths:
          - path: "/"
            pathType: "Prefix"
    # If you are securing your Pixee Enterprise Server with TLS via ingress, set the following
    tls:
      - hosts:
        - "<your pixee enterprise server domain name>"
        secretName: "<your tls certificate secret name>"

AI Model Provider¶

Select the AI provider you want to use and set the API key, endpoint (if required), and model names. Pixee uses two models: reasoning for complex analysis and fast for quick tasks — these can be the same model.

OpenAIAzure AI FoundryAnthropicAzure Anthropic

global:
  pixee:
    ai:
      enabled: true
      default:
        provider: "openai"
        apiKey: "<your OpenAI API key>"
      reasoning:
        model: "gpt-5.4-mini"
      fast:
        model: "gpt-5.4-mini"

Info

For OpenAI-compatible providers such as Databricks, set default.endpoint to your workspace serving URL. See Databricks AI.

global:
  pixee:
    ai:
      enabled: true
      default:
        provider: "azure"
        apiKey: "<your Azure AI Foundry API key>"
        endpoint: "<your Azure AI Foundry endpoint>"
      reasoning:
        model: "gpt-5.4-mini"
      fast:
        model: "gpt-5.4-mini"

global:
  pixee:
    ai:
      enabled: true
      default:
        provider: "anthropic"
        apiKey: "<your Anthropic API key>"
      reasoning:
        model: "claude-sonnet-4-20250514"
      fast:
        model: "claude-sonnet-4-20250514"

global:
  pixee:
    ai:
      enabled: true
      default:
        provider: "azure-anthropic"
        apiKey: "<your Azure Anthropic API key>"
        endpoint: "<your Azure Anthropic endpoint>"
      reasoning:
        model: "claude-sonnet-4-20250514"
      fast:
        model: "claude-sonnet-4-20250514"

For advanced settings (web search model, SCA / deep research models, custom headers, Responses API, using an existing secret), see AI Providers.