Self-hosted

Versioned chart releases for organizations running Intric on their own Kubernetes cluster: which chart carries which platform release, and whether the upgrade needs anything beyond helm upgrade.

Everything a user can see is in the main change log and is not repeated here.

Nov 4, 2026

intric-helm 5.21.4, which also carries the changes from 5.21.3 · intric-services 3.2.6

Backend 2.34.0 · Backend-go 1.3.0 · Frontend 1.193.0, the same as Intric’s cloud.

The chart defaults to ZITADEL v4.20.0, alpine/kubectl:1.37.2, hashicorp/terraform:1.16.7 and curlimages/curl:8.23.0, which clears the critical CVEs scanners report in the previous defaults.

The ZITADEL bootstrap turns self-registration off, so nobody can create an account on ZITADEL’s own login page. Accounts come from invitations, administrators and SSO. Invited users can still sign up with a password, which needs the frontend in this chart.

Backend logs and traces no longer contain upstream error text, MCP server URL paths or client IP addresses.

intric-services 3.2.6 updates the document ingestion, PDF pre-processing, audio transcription and artefact export images.

Note

Action required: before the upgrade.

With bundled ZITADEL and zitadelActionWebhook.enabled on a cluster whose Service CIDR is not 10.96.0.0/12 (k3s uses 10.43.0.0/16), set zitadel.serviceCIDR to your cluster’s Service CIDR, so ZITADEL can reach the webhook.

If an SMTP server, external identity provider or Actions target that ZITADEL calls presents a certificate chain through an eMudhra intermediate CA, replace that certificate.

Contact support@intric.ai if you need help with this upgrade.

Oct 30, 2026

intric-helm 5.21.2, which also carries the changes from 5.21.0 and 5.21.1 · intric-services 3.2.5

Backend 2.31.1 · Backend-go 1.2.0 · Frontend 1.190.1, the same as Intric’s cloud. The chart also brings the Oct 28 platform release — the Kimi K3 changes, faster answers with many knowledge files and Skill templates — to self-hosted installations.

Where the LLM sandbox is configured, Word, PowerPoint and Excel artefacts render on it instead of the sandboxed script runner, which gives heavy documents a longer time budget.

Backend security events cover every request except health checks, with the user, the IP address the backend sees, the action and the IDs of the objects in the request path. The Go backend sends the same events for the requests it answers, reading SECURITY_LOG_OTLP_URL from the API server’s environment.

ZITADEL starts again on an external Postgres where the postgres database is protected or the admin can’t alter the ZITADEL role, such as CloudNativePG, which 5.20.0 broke. Set ZITADEL_DATABASE_POSTGRES_ADMIN_EXISTINGDATABASE in zitadel.extraEnv to the database the admin connects to. The password check uses ZITADEL_DATABASE_POSTGRES_USER_SSL_ROOTCERT, so it also works where only the user connection verifies the server.

Installations that use the bundled RustFS object store can download files by signed URL, which the sandbox, transcription and PDF extraction need. Signed URLs now use signature version 4, which signs a region: if your object store checks it, set AWS_DEFAULT_REGION.

In intric-services 3.2.5, consumers scale on queued and in-progress jobs, so a lane adds replicas while all of its consumers are busy. The PDF pre-processing image no longer includes CUDA libraries, so it is several GB smaller and always runs on CPU. The sandboxed Python runner no longer leaves ConfigMaps behind when the Kubernetes API server fails during a run.

Note

Action required: before the upgrade.

Upgrade intric-services to 3.2.5 before intric-helm. If you run the LLM sandbox, its image must already include LibreOffice (intric-services 3.2.4 or later).

If rabbitmq.auth.existingSecret names a RabbitMQ user without the management or administrator tag, give it one first, or KEDA can’t read queue lengths and consumers stop scaling.

Contact support@intric.ai if you need help with this upgrade.

Oct 28, 2026

intric-helm 5.20.3, which also carries the changes from 5.20.1 and 5.20.2 · intric-services 3.2.4

Backend 2.29.0 · Backend-go 1.1.0 · Frontend 1.188.0 in the platform chart. Intric’s cloud already runs Backend 2.30.0 · Frontend 1.189.0: the Kimi K3 changes, faster answers with many knowledge files and Skill templates reach self-hosted installations with the next chart.

The backend names the queue service as the audience of the enqueue tokens it issues.

The LLM sandbox image includes LibreOffice, office fonts and the office Python packages, and its root filesystem is 4 GiB instead of 2 GiB.

The backend can send security events — failed authentication, denials, privileged API use, rejected WebSocket connections and a heartbeat — as OTLP logs to a separate endpoint set by SECURITY_LOG_OTLP_URL. Unset, it sends none. The chart README documents the variable.

The ZITADEL PAT-publisher sidecar runs under its own ServiceAccount, which can read or change only the init PAT Secret instead of every Secret in the namespace.

The chart READMEs explain which datastores need backups, how to rebuild Weaviate from Postgres, and how to size and grow a RabbitMQ cluster.

The PDF pre-processing consumer ships setuptools 84.2.1, which fixes GHSA-xmj3-9gf7-h52w.

Note

Action required: before the upgrade.

Upgrade intric-services to 3.2.4 before intric-helm. The backend in this chart puts an audience on its enqueue tokens, and the queue service must be one that checks it (queue-service 1.137.4 or later; intric-services 3.2.4 carries 1.137.5).

If you run the LLM sandbox, check that the sandbox host’s machines volume has room for MAX_MACHINE_COUNT × 4 GiB, since every cold boot copies the larger root filesystem.

Contact support@intric.ai if you need help with this upgrade.

Oct 23, 2026

intric-helm 5.20.0

Backend 2.27.1 · Frontend 1.186.0.

The bundled ZITADEL no longer uses a fixed database password. The chart generates one and applies it to the existing role the next time ZITADEL starts.

The backend worker’s replica count is set with intricBackendWorker.replicaCount. Set it to 0 to pause background jobs, for example while you restore data.

The queue service refuses enqueue tokens meant for another service. Tokens from the current backend release, which carry no audience, are still accepted.

OAuth token exchange, refresh, callback and revocation diagnostics leave out sensitive exception details, and MCP connection checks and OAuth state lookups are handled the same way.

The backend and the PDF consumers ship aiohttp 3.14.5, pypdf 6.21.2 and Pillow 13.0.0, which fix the October 2026 advisories for those libraries, including CVE-2026-112404. Frontend images use Node 24.22.1 with the October security fixes, on Debian Bookworm.

Note

Action required: before the upgrade, only if you run with zitadel-postgres.enabled: false on a cluster that can only pull from approved registries.

Before you upgrade, make sure the cluster can pull zitadel-postgres.image. The ZITADEL pod now uses it for an init container that syncs the database password.

Contact support@intric.ai if you need help with this upgrade.

Oct 21, 2026

intric-helm 5.19.4, which also carries the changes from 5.19.1, 5.19.2 and 5.19.3

Backend 2.25.0 · Frontend 1.184.1.

The backend refuses custom model providers and MCP servers on private addresses or non-standard ports unless ON_PREM is set or you list them in EGRESS_ALLOWLIST and EGRESS_ALLOWED_PORTS. Public destinations are unaffected. The chart README now documents the egress policy: private-network fetches follow ON_PREM, with EGRESS_ALLOWLIST and EGRESS_ALLOWED_PORTS for exceptions.

From intric-helm 5.20.0, the backend honours NO_PROXY again, so installs behind a mandatory proxy reach their own model servers and MCP servers. With ON_PREM set, it also accepts any port on destinations inside your own network, so a vLLM server on port 8000 or Ollama on 11434 no longer needs EGRESS_ALLOWED_PORTS.

Python services and package installers include updated certificate bundles for the emSign CA incident, and the diarization image includes an updated system certificate bundle that rejects compromised eMudhra chains. Operating-system and custom certificate stores need to be checked separately.

The backend’s /version endpoint reports the backend release again instead of DEV, along with the commit the image was built from.

Note

Action required: before the upgrade, if the backend reaches internal model servers or MCP servers.

Before you upgrade, add internal model servers (for example vLLM on port 8000) and internal MCP servers to EGRESS_ALLOWLIST and EGRESS_ALLOWED_PORTS. If you upgrade straight to intric-helm 5.20.0 or later with ON_PREM set, internal destinations need no ports listed.

Contact support@intric.ai if you need help with this upgrade.

Oct 15, 2026

intric-helm 5.19.0, which also carries the changes from 5.18.0

Backend 2.21.1 · Frontend 1.182.1.

The backend no longer fetches Remiss documents, DOCX export images, assistant imports, MediaWiki content or the Google, Microsoft and Slack integration tools’ API calls from private or link-local addresses. Self-hosted installs (ON_PREM=True) keep reaching private networks, so assistant import from an internal hostname and internal wikis still work, and importing an assistant with a sharing code from the same server works when its hostname resolves to a private address. Cloud installs list any internal host the backend must reach in EGRESS_ALLOWLIST.

The bundled Zitadel login no longer reveals whether an account exists: unknown usernames go on to the password step and fail with the generic invalid-credentials error.

The frontend can be turned off with intricFrontendApp.enabled: false, and the Redis and Weaviate volumes can be deleted with the release by setting persistence.deleteOnUninstall.

The sandboxed Python runner compresses scripts before sending them to Kubernetes and rejects scripts that are still too large after compression, so very large spreadsheet queries no longer overload the cluster’s control plane. It also cleans up its payload ConfigMaps when a run fails before its Job starts, instead of leaving them in the namespace.

The backend API server, migration Job and worker accept imagePullPolicy, for installs that move an image tag to new builds.

Note

Action required: none before the upgrade; one optional clean-up after it.

After you upgrade, you can delete leftover ConfigMaps labelled app=sandboxed-python-script-runner that have no ownerReferences. Earlier releases left them behind when a run failed before its Job started.

Contact support@intric.ai if you need help with this upgrade.

Oct 12, 2026

intric-helm 5.17.26

Backend 2.19.0 · Frontend 1.181.0. No manual action — upgrade in place.

The Zitadel bootstrap Job trusts global.caBundle, so bootstrap works over TLS when ingress.zitadelHost serves a private-CA certificate.

Oct 9, 2026

intric-helm 5.17.25

Backend 2.18.0 · Frontend 1.180.0.

The frontend reports how long people wait for an answer as two spans, event.answer.first_token and event.answer.completed, with the model, surface and outcome as attributes. Grafana can show time to first response, time to completion, and the share of answers that end in error, cancellation or abandonment.

Note

Action required: only if you want the answer timings broken down, or embed widgets on sites outside the widget organisation’s allowed origins.

Before you upgrade, add every site that embeds a widget to the widget organisation’s allowed origins. Widgets stop loading on any site not on that list.

After you upgrade, add answer_model, answer_surface, answer_status, uses_knowledge and uses_tools as span metrics dimensions in the Tempo metrics generator config to break the timings down. The overall averages work without it.

Contact support@intric.ai if you need help with this upgrade.

Oct 7, 2026

intric-helm 5.17.24

Backend 2.16.0 · Frontend 1.179.0.

The bundled Redis requires a password and only accepts connections from the backend api-server and worker pods.

The frontend reports how long people actively use the app as an event.session.ended span, with the duration bucketed in session_duration_bucket. Grafana can show average session length and its distribution, overall and per tenant.

Note

Action required: only if you use ArgoCD or other helm template GitOps, run other Redis clients, or want the session-length distribution panel.

Before you upgrade, under ArgoCD or other helm template GitOps, set redis.auth.existingSecret. Give any other Redis client its own NetworkPolicy. A pinned backend image must support REDIS_PASSWORD.

After you upgrade, add session_duration_bucket as a span metrics dimension in the Tempo metrics generator config to get the distribution panel. Average session length works without it.

Contact support@intric.ai if you need help with this upgrade.

Oct 6, 2026

intric-helm 5.17.23

Backend 2.15.0 · Frontend 1.178.1. No manual action — upgrade in place.

The backend can now connect to a password-protected Redis. Set REDIS_PASSWORD, and optionally REDIS_USERNAME and REDIS_SSL, on the backend; leave them unset and nothing changes.

Release images are now the exact images that passed staging, tagged with the version instead of rebuilt for production. The :latest tag moves only when production is deployed, not when a release is cut.

Oct 5, 2026

intric-helm 5.17.22

Backend 2.14.0 · Frontend 1.178.0.

The website crawler now fetches only public http(s) addresses.

Note

Action required: only if you crawl websites on private addresses.

Before you upgrade, set ALLOW_PRIVATE_CRAWL_URLS=true on the backend if any website in Knowledge is crawled from a private-network address, such as an intranet. Without it, those crawls stop fetching pages. Public websites need nothing.

Contact support@intric.ai if you need help with this upgrade.

Oct 2, 2026

intric-helm 5.17.21

Backend 2.13.0 · Frontend 1.177.1. No manual action — upgrade in place.

PyJWT is updated to 2.15.1 in the backend and the microservices, which closes the open PyJWT security advisories.

Oct 1, 2026

intric-helm 5.17.20, which also carries the changes from 5.17.19

Backend 2.12.0 · Frontend 1.177.0. No manual action — upgrade in place.

Sep 29, 2026

intric-helm 5.17.18

Backend 2.10.0 · Frontend 1.175.0. No manual action — upgrade in place.

The chart README now lists the values PROVISION_USER_ROLE actually accepts: User, Creator or Admin, case-sensitive. The USER, EDITOR and ADMIN spellings it listed before are rejected by the backend, so if you set the variable from the old list, change it to one of the new values.

Sep 28, 2026

intric-helm 5.17.17

Backend 2.9.0 · Frontend 1.174.1.

Document extraction for uploads now runs in its own worker pool, separate from chat work such as spreadsheet previews and document exports, and sizes that pool from the backend container’s CPU limit. With the chart’s default limits.cpu of 2000m that is two workers. If you have removed the CPU limit, the pool uses every CPU the node exposes.

Note

Action required: only if you run migrations yourself.

Backend 2.9.0 includes a database migration. With the default intricBackendMigration.enabled: true, the chart’s migrate Job applies it and the backend pods wait for it to finish, so there is nothing to do. If you have turned that Job off, run alembic upgrade head before the new backend starts serving.

Contact support@intric.ai if you need help with this upgrade.

Sep 25, 2026

intric-helm 5.17.16

Backend 2.8.0 · Frontend 1.174.0.

Note

Action required: only if you run migrations yourself.

Backend 2.8.0 includes database migrations. With the default intricBackendMigration.enabled: true, the chart’s migrate Job applies them and the backend pods wait for it to finish, so there is nothing to do. If you have turned that Job off, run alembic upgrade head before the new backend starts serving.

Contact support@intric.ai if you need help with this upgrade.

Sep 24, 2026

intric-helm 5.17.15

Backend 2.7.0 · Frontend 1.173.2. No manual action — upgrade in place.

Sep 23, 2026

intric-helm 5.17.14

Backend 2.6.1 · Frontend 1.173.1. No manual action — upgrade in place.

Sep 22, 2026

intric-helm 5.17.13

Backend 2.6.0 · Frontend 1.173.0.

A custom completion model can now point at an endpoint that speaks the Anthropic protocol, not only an OpenAI-compatible one, with its own base URL, API key, max_tokens and reasoning setting. Pass wire: "anthropic" when you create the model.

Failures in the shared consumer jobs are labelled with the tenant’s name as well as its id, so dashboards and trace queries show customer names instead of UUIDs.

Note

Action required: only if you run migrations yourself.

Backend 2.6.0 includes a database migration. With the default intricBackendMigration.enabled: true, the chart’s migrate Job applies it and the backend pods wait for it to finish, so there is nothing to do. If you have turned that Job off, run alembic upgrade head before the new backend starts serving.

Contact support@intric.ai if you need help with this upgrade.

Sep 21, 2026

intric-helm 5.17.12

Backend 2.5.0 · Frontend 1.172.0 — nothing user-facing in this release. No manual action — upgrade in place.

Crashes in the browser are now written to the frontend log as client error, carrying a reference id that the user sees on the error page, so a screenshot can be matched to a stack trace. A part of the app that fails to download now tells the user that and offers a reload, instead of reporting an internal error.

The web vitals dashboard no longer fills with junk series when an internet scanner probes the telemetry endpoint, and that endpoint now ignores requests from anyone without a session.

Sep 19, 2026

intric-helm 5.17.11

Backend 2.5.0 · Frontend 1.171.0. No manual action — upgrade in place.

Failures in the shared transcription, diarization, PDF pre-processing and document ingestion consumers now carry the tenant they belong to, so you can filter them by tenant in Tempo and Mimir instead of reading them as anonymous production failures.

Sep 17, 2026

intric-helm 5.17.10

Backend 2.4.0 · Frontend 1.170.0. No manual action — upgrade in place.

Sep 16, 2026

intric-helm 5.17.9

Backend 2.3.0 · Frontend 1.169.0. No manual action — upgrade in place.

Ingesting a large document no longer stalls the API pod that handles it. Chunking runs off the event loop from backend 2.3.0, so the other requests that pod is serving keep their normal latency while a document is ingested.

Sep 15, 2026

intric-helm 5.17.8

Backend 2.2.0 · Frontend 1.168.1. No manual action — upgrade in place.

Sep 14, 2026

intric-helm 5.17.7

Backend 2.1.0 · Frontend 1.168.0. No manual action — upgrade in place.

Sep 12, 2026

intric-helm 5.17.6

Backend 2.0.1 · Frontend 1.167.0. No manual action — upgrade in place.

Sep 11, 2026

intric-helm 5.17.5 · intric-services 3.1.2

Backend 2.0.0 · Frontend 1.167.0 in the platform chart; document-ingestion-consumer 1.149.6 in the services chart.

Caution

Action required: before you upgrade.

Backend 2.0.0 replaces the per-user endpoints for tenant user administration and space membership with endpoints that take a selection. PATCH /users/admin/{id}/ and DELETE /users/admin/{id}/ become PATCH /users/admin/bulk/ and POST /users/admin/bulk-delete/; PATCH /spaces/{id}/members/{user_id}/ and DELETE /spaces/{id}/members/{user_id}/ become PATCH /spaces/{id}/members/ and POST /spaces/{id}/members/bulk-remove/. The frontend the chart pins is already updated — this affects your own scripts and integrations that call the Intric API directly. Anything still calling the old paths stops working at the upgrade.

Contact support@intric.ai if you need help with this upgrade.

Sep 10, 2026

intric-helm 5.17.4

Backend 1.258.0 · Frontend 1.166.0. No manual action — upgrade in place.

Sep 9, 2026

intric-helm 5.17.3

Two platform releases in one chart: backend 1.256.0 · frontend 1.164.0 and backend 1.257.0 · frontend 1.165.0. Base images move too: curl 8.22.0 and Terraform 1.16.1. No manual action.

terraform-zitadel-bootstrap 0.3.5 carries the same Terraform bump, if you run the bootstrap yourself.

Sep 7, 2026

intric-helm 5.17.2

Backend 1.255.0 · Frontend 1.163.0. No manual action.

Sep 6, 2026

intric-helm 5.17.1 · intric-services 3.1.1

Backend 1.254.0 · Frontend 1.162.1 in the platform chart; pdf-pre-processing-consumer 1.23.8 in the services chart.

Security — worth taking early. protego ReDoS reachable through robots.txt parsing, so through the crawler on input from the sites you point it at (backend 1.254.0). Transformers save_pretrained path traversal (pdf-pre-processing-consumer 1.23.8, and diarization-nemo 1.9.7 published 09-05 — confirm which chart pins that image in your installation).

Note

Action required: at the next upgrade window.

Upgrade both charts. The platform chart alone leaves the PDF consumer on the vulnerable transformers version — that image is pinned by intric-services, not intric-helm.

Contact support@intric.ai if you need help with this upgrade.