:mega: Hi all :wave: super excited to announce 2 m...
# announcements
b
📣 Hi all 👋 super excited to announce 2 more major milestones in the path to GA’ing Flyte 2: a backend dev box with a completely reimagined UI. 👉 Try it here 🤔 What is the backend devbox? The dev box lets you run a real Flyte 2 backend (including full scheduling, persistence, API surface) with a single command: flyte start devbox. This is the same architecture that will power Flyte 2 in production. Whatever you build against it today will carry forward. 💻 Reimagined Flyte UI We’ve taken our UI for Union.ai (the enterprise Flyte platform) and created a free Flyte version so our community can have a truly best-in-class DevEx. We’ve spent two years building it alongside teams running AI at scale, and you can feel that. *️ Some highlights:* • Real-time execution state. • Interactive debugging so if a task runs out of memory, you can rerun it with more resources right from the UI, no code changes. • And when Flyte self-heals from a failure, you can see exactly what happened and when. Not just that it recovered, but how.
🚀 7
flyte 2 5
woohoo 5
🙌 5
❤️ 7
🎉 3
1️⃣ 1
🥰 1
🦜 2
🙏 1
🤯 1
celebrate 1
🎯 1
💯 1
📣 1
🔥 9
flyte 11
📈 Thank you for Flyte 2’s momentum since March. 700,000+ downloads, 78 releases, ~900 merged pull requests, 44 contributors. I’m floored every time I look at these numbers. A specific thank you to André Ahlert, who contributed the Flyte Plug-In Registry. That kind of initiative is what makes this community different. 🛣️ What’s next? Our next milestones are releasing a production-grade Flyte 2 backend with single-cluster support for distributed execution and multi-cluster support after that. This is a fault-tolerant, open-source backend that will bring everything – autoscaling, resource awareness, and resilient state management – to production environments. Every release brings us closer to a fully open source Flyte 2, and we’re building it in the open you, the Flyte community. Until then… Run the dev box. Explore the UI. Tell us what you think.
🙏 1
🤝 Contributing You might have noticed a change in the
flyte
repo: • Flyte 2 will be maintained in the
main
branch, which is now the default branch: https://github.com/flyteorg/flyte • Flyte 1.x will be hosted in the
master
branch, which we will continue to maintain for the foreseeable future: https://github.com/flyteorg/flyte/tree/master If you’re curious what the differences are in the programming model between Flyte 1 -> 2, check out this doc: https://www.union.ai/docs/v2/flyte/api-reference/migration/