Kestra and Bitovi: Platform Engineers Who Build With You

Kestra and Bitovi: Platform Engineers Who Build With You
Robert Walters

Robert Walters

Senior Technical Product Marketing Manager

November 19 2026Company News
Authors
Robert Walters

Robert Walters

Senior Technical Product Marketing Manager

Category
Last Updated

We are excited to announce that Bitovi is a Kestra partner. If you want an outside review of your Kestra setup, senior engineers to build with your team, or someone to keep the platform running after launch, Bitovi can help.

About Bitovi

Bitovi is a US consultancy that has been delivering software engagements since 2006. Their platform engineering team builds internal developer platforms, golden paths, and production infrastructure, and their engineers run Kubernetes, CI/CD, and GitOps in production for clients.

Kestra is part of that practice. Bitovi helps teams set up Kestra workers and flows with the right patterns, and figure out where Kestra should sit in a stack that already has a scheduler, a CI system, and legacy scripts nobody wants to touch.

What Bitovi offers

Bitovi works with Kestra teams in three ways:

  • Assessment: a review of your platform at whatever stage it’s in, ending with a scored report and a prioritized roadmap
  • Build: senior platform engineers working alongside your team on a defined scope, such as standing Kestra up on Kubernetes, wiring it into your CI/CD and Git workflow, or setting up golden paths so new teams start from a working template instead of a blank YAML file
  • Support: operations, upgrades, and roadmap work once the platform is live, with training so your team ends up owning it

Kestra upgrades

For teams still on previous versions of Kestra, Bitovi has a migration package for the move to Kestra 2.0. The upgrade starts from 1.3 and the cutover is one-way: 2.0 drops the old JDBC queue tables on startup, so a database backup is your only way back. Most flows carry over unchanged, and the rest fall into two groups:

  • Changes kestra-migrate rewrites for you, such as json() to fromJson() or condition to when on flow-level checks
  • Changes you rewrite by hand, such as trigger conditions, which the tool flags with a warning and leaves in place

With a handful of flows, you can work through the 2.0 migration guide yourself. With a few hundred across namespaces and teams, it’s worth having someone who has done it before. In the replay below, Bitovi engineering team’s walk through the process: sizing the work with kestra-migrate --check, applying the automated rewrites, fixing what’s left by hand, and validating with kestractl before the switch.

Choosing a Kestra edition

If you are still deciding how to run Kestra, Bitovi published a video on Kestra’s editions, architecture, and trade-offs on their YouTube channel. You can also compare editions in our Open Source vs. Enterprise guide.

Get started

If you’re planning a production rollout and want a second set of hands, Bitovi is a good place to start. And if you have questions for us, join the Kestra community on Slack; we would love to hear what you build.

Newsletter

Get Kestra updates to your inbox

Stay up to date with the latest features and changes to Kestra