lifestyle.gamezon.net

Kestra 2.0 Gives Enterprises One Governed Orchestration Layer Across Every Environment

Business Wire

Kestra today announced new enterprise capabilities enabled by Kestra 2.0, addressing the security, governance and control requirements of enterprise orchestration. Released to the developer community earlier this month, Kestra 2.0 gives enterprises one governed orchestration layer across data, infrastructure, applications, and business processes, and removes the architectural constraint that has kept many regulated and security-conscious organizations from adopting one. Workers now run without any connection to a central database, which means an organization can place execution wherever its security policy requires: in a separate network zone, another cloud, another region, or entirely offline.

Enterprise automation has fragmented. Data teams run one scheduler, infrastructure teams run another, application teams wire their own scripts, and business processes sit in workflow systems of their own. As automation has spread, the hardest complexity has stopped arising inside any single system and started arising at the transitions between them. A pipeline finishes but the job downstream never starts, and no one can say which system owned the process.

AI is making that harder. Agents are entering production and taking actions rather than answering questions, and most organizations cannot say what an agent did or prove it to an auditor. What was a visibility problem becomes a governance problem. Until now, the enterprises that most needed one governed layer were the ones least able to adopt it, forced to choose between governing everything from one place and honoring the security rules that made governance necessary.

“Enterprises did not set out to run five orchestration tools. It happened one team at a time, and the result is that the work a business depends on most is the work it can see least,” said Emmanuel Darras, CEO and co-founder of Kestra. “Kestra 2.0 brings unified orchestration to the Fortune 500, where companies have the most domains to govern and the least freedom in where execution can happen, providing one place to run and govern every workflow.”

Unified orchestration brings four domains that have historically been run separately, on separate tools, under one governed layer:

  • Data. Ingestion, transformation, data lakes and warehouses, and machine learning pipelines.

  • Infrastructure. Enterprise job scheduling, cloud and container infrastructure, provisioning and configuration, CI/CD, and IT and security runbooks.

  • Applications. Microservice coordination, API workflows, event-driven processes, and SaaS integrations.

  • Business processes. Approvals, onboarding, order-to-cash, ticket and issue tracking, and integration with existing enterprise systems.

Consolidation happens at the orchestration layer, not underneath it. Enterprises keep the platforms and applications they already run, and replace the separate orchestration tools that grew up around each domain. Most begin in a single domain and extend into others as the need arises, rather than adopting a new tool for every new requirement.

Kestra 2.0 delivers four enterprise outcomes:

  • Execution wherever security requires it. Workers hold no database connection and no credentials, opening a single outbound connection to the controller. Deployments that were previously out of reach become straightforward: segmented network zones, other clouds, other regions, on-premises, and fully air-gapped environments. Governance no longer stops at the network boundary.

  • Controlled production access for AI agents. Any workflow can be exposed as a tool an external agent calls, with execution approval required before anything reaches production, action-based access control, and full audit logging. Agents are treated as authenticated users, so an agent retrieves only what the person behind it is authorized to see.

  • Predictable capacity on shared infrastructure. Teams sharing one deployment no longer compete for the same compute. Workloads are isolated and capacity can be reserved per team, so a heavy job in one domain does not starve a critical one in another.

  • Failure handling an enterprise can rely on. When something goes wrong, teams decide what happens rather than discovering it afterward. Work can be retried, redispatched, or failed deliberately, so operations that must never run twice fail loudly instead of silently duplicating.

Kestra 2.0’s rebuilt engine is designed to scale more efficiently and flexibly as enterprise workloads grow. In published benchmarks, the new architecture delivered up to twice the throughput on the same infrastructure, while giving organizations greater flexibility to scale execution across teams, workloads, and environments. Full results and methodology are published.

Kestra 2.0 is backed by bug and security fixes through September 2027. It includes breaking changes and ships with migration tooling that rewrites most flows automatically and flags the few that need a human decision.

An early example shows what the architecture makes possible. A global IT infrastructure manufacturer is building a shared service on Kestra 2.0 that will let teams reserve physical machines across its worldwide estate, bringing infrastructure currently dedicated to individual teams into a common pool. The project also covers firmware updates and patching across separate security zones. The deployment depends on workers running with no connection to a central database, which is what 2.0’s rebuilt execution model makes possible. The first pilot environments are expected to enter production in the coming weeks.

The release advances Kestra’s position that enterprises should be able to orchestrate across every domain and every environment through one governed layer, without surrendering control of where execution happens or where data lives.

Kestra 2.0 reached general availability on September 8, 2026. The open-source edition is available at kestra.io and on GitHub, and Kestra Enterprise is available directly from Kestra.

Additional Resources:

About Kestra

Kestra is the open-source platform for unified orchestration, giving enterprises one layer to run, govern, and observe every workflow across data, infrastructure, applications, business processes, and AI agents. Teams declare workflows in YAML and run tasks in any language on an API-first platform. Licensed under Apache 2.0, Kestra’s open-source edition has more than 28,000 GitHub stars and 1,500 contributors.

Kestra Enterprise adds the capabilities large organizations require to standardize on a single orchestration layer, including role-based access control, audit logging, multi-tenancy, reserved capacity per team, and execution across segmented, sovereign, and fully air-gapped environments. Kestra is used by Fortune 500 enterprises across financial services, technology, logistics, and consumer goods. Founded in 2021 by Emmanuel Darras and Ludovic Dehon, Kestra has raised $36 million, including a $25 million Series A led by RTP Global. Learn more at kestra.io.

Media gallery

More Press Releases