Jitsu 2.14.0: Kubernetes-native self-hosting, Function Servers, and CronJob-based syncs
Jitsu 2.14.0 is now available.
This is our first stable release since jitsu2-v2.11.0 in August 2025, bringing together roughly 1,600 commits across the platform.
The biggest change is architectural: Jitsu is now Kubernetes-native for feature-complete production self-hosting.
Why we made this change
In earlier versions, several important runtime components were still tied to older deployment assumptions.
User functions, profile builders, and connector syncs needed a cleaner operational model to scale reliably in self-hosted environments.
In 2.14.0, these components now run as first-class Kubernetes workloads.
Function Servers
User functions and Profile Builder v2 now run on dedicated Function Servers.
A new Jitsu operator manages the Kubernetes resources required for each deployment.
This gives us a stronger foundation for:
- workload isolation
- autoscaling
- sharding
- different execution classes
- more reliable production operations
- CronJob-based connector syncs
Connector syncs have moved from Google Cloud Scheduler to Kubernetes CronJobs.
syncctl now reconciles scheduled syncs directly into the cluster. Each sync runs as an independent pod with its configuration stored in Kubernetes.
This removes a cloud-specific dependency and makes production self-hosting more portable.
What else is included
This release also adds:
- MCP server support in Jitsu Console
- generated OpenAPI specifications and API reference
- user API tokens
- audit logs
- maintenance mode
- dead-letter queues and event reprocessing
- improved sync and connection notifications
- a redesigned signup flow
- ClickHouse TTL-based event-log retention
- development Helm charts
- new and improved integrations
- Important upgrade notes
This release includes breaking changes.
Kubernetes is now required for production deployments using functions, profile builders, or connector syncs.
Docker Compose is deprecated for complete production deployments and is now intended primarily for local development and exploration.
Try it and help us improve
We are actively investing in Jitsu again and would love feedback from developers, data engineers, and teams running event infrastructure in production.
Try the release, test the self-hosting experience, open an issue, or tell us what feels confusing, incomplete, or unnecessarily difficult.
We are especially interested in feedback around:
- Kubernetes deployment and upgrades
- connector reliability
- event observability
- function execution
- developer experience
- documentation
Release notes: Jitsu 2.14.0 on GitHub
Self-hosting documentation: Jitsu self-hosting guide
Jitsu is open source, and we would love your help making it better.
Top comments (0)