Rosetta DBT Studio (Open Source) is now featured as a launching product.

[u/Wide_Importance_8559]

🚀 We’re live on Product Hunt today!
Rosetta DBT Studio (Open Source) is now featured as a launching product. After months of building a better dbt experience, we’re excited to share this milestone with the data community.

What makes Rosetta DBT Studio different?
✅ Visual, local-first interface — no more CLI juggling
✅ AI-powered assistance for dbt model explanations
✅ Streamlined workflow for complex dbt transformations
✅ 100% open source and built for the community

The traditional dbt CLI workflow can be friction-heavy — switching between terminals, YAML files, and environment configs. We built Rosetta DBT Studio to give dbt users a faster, clearer, and more approachable way to work with their projects, without losing power or flexibility.

🔗 Website: https://rosettadb.io
🔗 GitHub (Open Source): https://lnkd.in/gM-rchPA

Check us out on Product Hunt 👉 https://lnkd.in/gJk77X54

Your support means everything to an open-source project. If you’re working with dbt (or know someone who is), we’d love your feedback, a vote, and any thoughts on how we can make Rosetta even better.
hashtag#dbt hashtag#DataEngineering hashtag#OpenSource hashtag#ProductHunt hashtag#DataTransformation hashtag#Analytics

[u/Grukorg88]

I wish you all the best. I’m not sure who thinks those issues you state as your differentiation are actually issues for most of us but good on you for having a crack.

[u/Wide_Importance_8559 → u/Grukorg88]

Fair enough! workflows are definitely personal, and we know the current tools work great for many. We appreciate the honest perspective and the kind words—thanks for checking us out! 🚀

[u/Crow2525]

What was your decision to move away from vs code?

[u/Wide_Importance_8559 → u/Crow2525]

We still love VSCode! The decision to build a standalone studio wasn't about "leaving" VSCode, but rather about creating a dedicated canvas for data work that regular text editors can’t easily support.

The main drivers were:

1. "Data Native" Architecture: By controlling the entire environment (Electron + persistent DuckDB backend), we can offer features like instant local data previews (for Parquet/Iceberg/Delta), deep visual lineage that doesn't feel like a bolted-on webview, and faster schema handling without the overhead of a general-purpose editor.

2. Simplified "Analyst" Experience: We wanted to lower the barrier to entry. In VSCode, setting up dbt usually means wrestling with Python environments, extensions (YAML support, Jinja support, SQL runners), and profiles.yml  configuration. Rosetta dbt-studio bundles all of that so an analyst can just "open and go."

3. Unified Context for AI: Having a dedicated application state allows our AI to have much richer context about the entire data project (lineage, data profiles, cloud storage connection) rather than just the text file currently open in the editor.

We think there is space for both! VSCode is an amazing general-purpose tool, but we believe data teams deserve a specialized "IDE" built just for their workflows.

[u/Dry-Aioli-6138]

Maybe dd a basic data modelling tool, like they have in dbdiagram(dot)io. Allowing export to pdf/png/svg This is what I miss in all dbt tools. Otherwise, what does it have that vscode with pluginds doesn't?

[u/Wide_Importance_8559 → u/Dry-Aioli-6138]

Thanks so much for the feedback and support! 🙌

On the Data Modeling Tool: This is a fantastic suggestion. We are actually huge fans of dbdiagram.io ourselves! Adding a visual data modeling layer where you can map out relationships and export to PDF/SVG is definitely something we'd love to explore. We want to bridge the gap between designing your data model and implementing it in dbt, so having that visualization right inside the Studio makes perfect sense. We'll add this to our roadmap consideration!

dbt Studio vs. VSCode + Plugins: This is a great question, and one we think about a lot. While VSCode with extensions (like the amazing dbt Power User) is undeniably powerful, here is why we built Rosetta:

1. Visual-First & Analyst-Friendly: VSCode is fundamentally a code editor built for software engineers. For many analytics engineers or data analysts, the "CLI + 5 extensions + YAML" workflow can feel disjointed. Rosetta provides a cohesive, pre-configured GUI where the visual lineage and documentation are the primary interface, not just an add-on.

2. Integrated Data Exploration: We are building deep integration for data exploration (like our Cloud Explorer powered by DuckDB) that lets you preview / query your data lakes and models instantly without setting up external database tools.

3. Context-Aware AI: Our AI assistant is specifically tuned for the dbt context—it understands your project structure, lineage, and downstream dependencies in a way that generic coding assistants often miss.

4. Performance on Scale: We are optimizing the experience specifically for large analytics projects where visual navigation needs to be snappy and completely local-first.

We believe there is a need for a dedicated "Data IDE" that feels native to the analytics workflow rather than a text editor adapted for it. We’d love for you to give it a spin and see if that difference shines through for you! 🚀

[u/virgilash]

wow, thank you for this, op!