03 Integrating Qwak into JFrog
Translating an ML product into a larger platform · 2025–2026
Bringing Qwak’s model discovery into JFrog’s AI Catalog and broader platform ecosystem
Overview
After Qwak was acquired by JFrog, I led the product design integration between two very different platforms - a focused ML product and a large DevSecOps ecosystem.
The challenge was bringing Qwak into JFrog without simply forcing one product into the other: translating workflows, consolidating overlapping experiences, and deciding what to preserve so existing users weren’t disrupted.
From standalone Qwak to an integrated JFrog experience
Contributions
Translated Qwak’s ML workflows into JFrog’s product architecture, navigation, and language so they felt native to the larger platform.
Consolidated overlapping workflows instead of duplicating functionality across the two products.
Migrated Qwak visually to JFrog’s design system before the technical integration, creating a bridge between the products while they still ran separately.
Preserved familiar workflows where they were already working, minimizing disruption for existing Qwak users.
Worked across different technical constraints and design systems to define what should be kept, adapted, or retired.
Preserving what worked while adapting Qwak to a broader platform
Outcome
Qwak’s ML capabilities became part of JFrog without losing the workflows existing customers relied on. JFrog gained an integrated ML experience that felt native to the platform, while the gradual migration reduced disruption throughout the transition.
Takeaway
The hardest part of integration isn’t merging products - it’s deciding what to preserve, what to adapt, and what shouldn’t change.
Contact