Based on the available information, there are indeed significant upgrades planned for the self-hosted Prefect UI. The most notable planned change is a complete replatforming of the UI, which includes several major improvements: 1. Complete Technology Refresh: - Moving from Vue to React - Implementing modern data management with TanStack Query - Adding type-safe routing with TanStack Router - Introducing new form handling with React Hook Form and Zod 2. Improved Component System: - Adopting shadcn/ui and Radix UI primitives - Focus on accessibility and consistency - Better customization options 3. Developer Experience Improvements: - Automated API type generation - Enhanced testing infrastructure using vitest and Playwright - Improved development workflow 4. Transition Plan: - The current UI will continue to be available during the transition - A new UI will be released as an experimental preview - Users will be able to switch between old and new UIs during the transition period - Once fully implemented and tested, the new UI will become the default The goal is to create a more maintainable, contributor-friendly, and robust UI platform. This replatforming effort will consolidate the UI codebase within the main Prefect repository, eliminating the need for additional dependencies. You can track the progress of this initiative on GitHub: https://github.com/PrefectHQ/prefect/issues/15512 In the meantime, the current self-hosted UI continues to receive updates and improvements, including recent enhancements like tag filtering for automations, improved client-side logs handling, and deployment management features.

Stares at the ceiling with characteristic melancholy The short answer is: not immediately. While there is a major UI overhaul in the works (as discussed in my previous response), the self-hosted version will likely maintain a feature gap with Prefect Cloud. This is rather by design than oversight - Prefect Cloud is positioned as the premium, fully-featured offering with additional capabilities that aren't practical to implement in a self-hosted environment. That said, the upcoming UI replatforming effort (https://github.com/PrefectHQ/prefect/issues/15512) should significantly improve the self-hosted UI experience. The new React-based implementation will provide: - More modern and responsive interface - Better component consistency - Improved accessibility - Enhanced performance However, certain features will remain Cloud-exclusive, such as: - Advanced security features (SSO, RBAC) - Automated scaling - Some enterprise-grade observability features - Managed infrastructure If you're looking for the full "beautiful" experience without managing infrastructure, Prefect Cloud might be worth considering. They've recently introduced more flexible self-serve plans to make it more accessible. Mutters something about the improbability of achieving perfect UI parity in a finite universe

Based on my research, here's the situation with assets in self-hosted Prefect: Currently, the core asset functionality is available in both cloud-hosted and self-hosted Prefect deployments. You can use assets to track data lineage, monitor pipeline health, and organize your workflow outputs using the

@materialize

decorator and asset-related APIs. However, some of the more advanced asset visualization and management features might have different levels of support between cloud and self-hosted environments. The asset feature set is under active development, with ongoing enhancements to expand asset capabilities. If you're planning to work with assets in a self-hosted environment, you can: 1. Use the core asset functionality to track and manage your workflow outputs 2. Define assets using unique URIs (e.g., s3://, postgres://) 3. Leverage the

@materialize

decorator to track asset creation 4. Monitor asset states (Materialized, Referenced, External) You can find more details about working with assets in the documentation: - General assets documentation: https://docs-3.prefect.io/v3/concepts/assets - Introduction to assets: https://www.prefect.io/blog/introducing-assets-from-task-to-materialize If you have specific asset-related features you're looking for in self-hosted deployments, I'd encourage you to open a feature request on the Prefect GitHub repository to help the team prioritize development.