On-premises setup
Polytomic also offers an on-premises (self-hosted) deployment that runs in your private cloud, wholly self-contained. Contact us through our website to learn more: https://www.polytomic.com/contact.
We recommend deploying Polytomic to Kubernetes with our Helm chart. We also support Amazon ECS. See Deploying on Amazon ECS.
Environment requirements
- A Kubernetes cluster, PostgreSQL, Redis, an object storage bucket, and a shared volume. See Sizing and infrastructure requirements for details and starting sizes.
- An ingress controller that can expose Polytomic to your users with TLS termination.
- A way for your users to sign in: a Google OAuth client, or an OpenID Connect provider (see SSO).
Before you get started
Complete the following before you deploy:
- Request access to the Polytomic container registry by emailing [email protected]. We support AWS ECR and Google Cloud Artifact Registry.
- Receive your deployment name and deployment key from Polytomic.
- Provision PostgreSQL, Redis, and an object storage bucket according to our recommendations.
- Create a Google OAuth client or configure your OIDC provider.
Deploying
Add the Polytomic chart repository:
helm repo add polytomic https://charts.polytomic.com
helm repo updateDownload the default values file and edit it for your deployment:
curl https://raw.githubusercontent.com/polytomic/on-premises/master/helm/charts/polytomic/values.yaml -o values.yamlThen install the chart:
helm install polytomic polytomic/polytomic --namespace polytomic --create-namespace -f values.yamlTo upgrade, change image.tag in your values file to the new release and run helm upgrade with the same arguments.
The chart documentation describes every value, including logging, metrics, and network policy options.
We also provide Terraform modules for EKS and GKE. These modules create a cluster and its supporting infrastructure, then install the chart. Contact us if you want to deploy another way.
Deploying on Amazon ECS
To deploy on ECS, use our ECS Terraform module. Its examples include complete deployments. The module uses its own polytomic_* variables rather than the Helm values on this page, and extra_environment sets any other environment variable.
Deploying the MCP server
The Helm chart and the ECS module can also run the Polytomic MCP server. It's off by default. See MCP server.
Configuration
The following values are required:
-
image.tagThe Polytomic release to deploy, for examplerel2026.10.21. Always use a specific release rather thanlatest. -
polytomic.deployment.nameA unique identifier for your on-premises deployment, provided by Polytomic. -
polytomic.deployment.keyThe license key for your deployment, provided by Polytomic. -
polytomic.auth.urlBase URL for accessing Polytomic; for example,https://polytomic.mycompany.com. Polytomic uses this URL to redirect back from Google and other integrations after OAuth authentication. Set the host iningress.hoststo match. -
polytomic.auth.root_userThe email address of the first user. On first start, Polytomic creates an Organization with this user as its administrator. The administrator can then invite other users and configure Polytomic. -
polytomic.s3.operational_bucketandpolytomic.s3.regionThe bucket used for storing artifacts (logs, query results, job payloads), for examples3://acmeinc-polytomic. Polytomic must be able to read and write the bucket. On EKS, grant access with an IAM role for the service account (serviceAccount.annotationsandpolytomic.vector.daemonset.serviceAccount.roleArn). On GKE, setpolytomic.s3.gcstotrue, use ags://bucket, and grant access with Workload Identity. We recommend setting a bucket lifecycle rule to expire objects automatically.
Polytomic requires sign-in by default. For evaluation only, you can set polytomic.auth.single_player to true to turn sign-in off.
To use Google sign-in, set polytomic.auth.google_client_id and polytomic.auth.google_client_secret to the ID and secret of a Google OAuth 2.0 client.
Leave polytomic.auth.methods empty unless you want to restrict sign-in. By default, Polytomic allows Google and SSO. If you set it, list every method you use, for example ["google", "sso"].
Google redirect URLYour Google OAuth client's valid redirect URLs must include your
polytomic.auth.urlvalue followed by/auth. For example,https://polytomic.mycompany.com/auth.
To use an OIDC provider instead, see SSO.
Database and Redis
By default, the chart runs PostgreSQL and Redis inside the cluster. In-cluster instances are suitable for evaluation. For production, point Polytomic at your own instances:
postgresql:
enabled: false
externalPostgresql:
host: polytomic.abc123.us-west-2.rds.amazonaws.com
username: polytomic
database: polytomic
ssl: true
sslMode: require
existingSecret:
name: polytomic-database
key: password
redis:
enabled: false
externalRedis:
host: polytomic.abc123.cache.amazonaws.com
ssl: true
existingSecret:
name: polytomic-redis
key: passwordYou can set passwords directly with externalPostgresql.password and externalRedis.password, or read them from existing Kubernetes secrets as shown above.
Shared volume
Polytomic uses a ReadWriteMany volume shared between its pods. By default, the chart provisions one with an in-cluster NFS server. To use a managed file system such as Amazon EFS instead, set:
polytomic.sharedVolume.modetostatic.polytomic.sharedVolume.static.volumeHandleto your file system ID.nfs-server-provisioner.enabledtofalse.
Additional settings
Use polytomic.extraEnv to pass other settings to Polytomic as environment variables:
polytomic:
extraEnv:
LONGSYNC_THRESHOLD: "120"DEPLOYMENT_LINKSAdds deployment-specific links to the Polytomic navigation bar. The value is a JSON-encoded array of objects. For example:
DEPLOYMENT_LINKS='[{"url":"https://polytomic.com", "name":"Polytomic Homepage"}]'-
GA_MEASUREMENT_IDA value of the formatG-XXXXXXXthat denotes a Google Analytics instance. Setting this turns on Google Analytics session tracking for your Polytomic users, with their email addresses as the Google Analytics user ID. -
LONGSYNC_THRESHOLDControls how many minutes a sync may run for before a long-running-sync alert email is sent. Email recipients are those on the Sync Error notification list. Default is 0 (disabled). -
OAUTH_DCR_DISABLED,OAUTH_CIMD_CLIENT_IDS,OAUTH_CIMD_DISABLEDRestrict which MCP clients may sign in with OAuth. See MCP OAuth clients. -
VALID_ORIGINSA comma delimited list of valid HTTP origins. Polytomic automatically adds yourpolytomic.auth.urlvalue to this list.
Set the log level with polytomic.log_level. Valid values are debug, info, warn, and error. The default is info.
Set credentials for integrations that need them on premises, such as OAuth client IDs and secrets, with polytomic.integrations. See Integrations and connections.
Health and version checks
Polytomic exposes a health and version-check endpoint at /status.txt. Use it to verify that Polytomic is running and to check its release version.
First run
Polytomic runs database migrations on startup, so the database user must have permission to create and alter the schema.
Once Polytomic starts, sign in as the user set in polytomic.auth.root_user.
Data we record
Polytomic On Premises makes the following outbound requests:
- Periodic requests to
ping.polytomic.comto verify your license is valid and to record usage telemetry. Telemetry does not include any personally identifiable information. - If you enable the Datadog agent (
polytomic.datadog.daemonset.enabled), Polytomic sends application traces to Datadog. These traces may include executed queries but do not contain variables used while processing the pipeline. These traces help us understand how Polytomic is performing. - Polytomic sends errors to Sentry.io to help us debug them. Error payloads do not contain values used to trigger the sync.
Integrations and connections
Some integrations require additional configuration when running on premises. See Integration-specific setup.
Updated 12 days ago