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.

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.