Lamatic 3 offers a complete reimagined approach to building Agentic Apps. We are thrilled to introduce a developer-focused Studio Refresh, a GitHub-based version control system, and environments. Additionally, we have AgentKit for quick deployment of agents and Vibe Assistants.
Interesting Product @chuck_whiteman@arun2728@naitik_kapadia . I’m curious how the new flow builder changes day-to-day use. Does it actually make complex automations easier to set up without extra guidance?
Thanks @harkirat_singh3777 for the questions. Our focus is to make Agentic automation easier without compromising on developer controls. Here a few way how we make it easier -
Node Based System - we have precomposed AI, Data and Logic Nodes which are specifcally designed for AI use cases
Drag and Drop Flow builder for complex agentic architecture like ReAct, Multi Agent, Supervise
Built in Debugging and Tracing
AI Assistant to help you build flows, Write Code, prompts and test cases
Agent Optimization tools like A/B Test, Fallback, Retry and Parallel Logics.
@harkirat_singh3777 Absolutely! We’ve redesigned the flow builder to feel far more intuitive in everyday use. One of the biggest friction points earlier was variable mapping, and the new selector that @ian_dsouza built removes a lot of that confusion by giving you clearer visibility while you build.
Plus, if you hit a roadblock at any point, there is an AI assistant available on every screen. Whether you need help crafting a prompt, choosing the right node, or even creating your whole flow, the assistant steps in right where you need it.
The goal is to let you create complex automations with confidence and without needing constant guidance.
While the rest of the team focused on the core infrastructure and visual flow, my mission for Lamatic 3.0 was to make the actual building experience effortless using—you guessed it—AI.
I’m thrilled to introduce the Family of AI Assistants living inside the Studio. I built these to act as your co-pilot, so you never get stuck on a blank screen.
We shipped: ✨ Vibe Builder: Generate full AI agents from a single screen just by describing what you want. ✨ Flow & Node Assistants: Get real-time guidance and a mini-expert inside every node to optimize inputs and fix errors. ✨ Code & Prompt Assistants: Write, refine, and debug code or prompts with contextual suggestions without leaving your workspace.
A massive shoutout to @arun2728 for the guidance and help in bringing this architecture to life!
I would love to know: which part of agent building do you usually find the hardest? Hopefully, our new assistants can help solve that! 👇
I'm a Founding Engineer at Lamatic.ai, and I’m the one behind our new Version Control & Environments (Branches) system in 3.0.
Our goal with this release is simple: make the entire user journey smoother, more reliable, and production-ready.
🤔 Why do you need Version Control Systems?
Building production-grade AI agents demands the same engineering discipline as any real-world software system - and that starts with version control. When you're transforming domain expertise into dependable AI flows, you need clarity on every change:
Which prompt performed best?
What model configuration worked?
Who modified what—and when?
That’s why we brought GitHub integration directly into Lamatic Studio. It gives teams a familiar workflow while adding the ability to automatically audit changes, roll back flows or deployments, and maintain full accountability across the board.
🌱 Why environments (branching) matters?
Branching is especially powerful for agent development. It lets you cleanly separate production from development - so you can experiment freely without risking live systems. Spin up a branch, test safely, iterate fast, and merge only when the flow is stable.
In AI systems - where even a tiny prompt tweak can shift behavior dramatically - version control isn’t a nice-to-have. It’s the foundation for building agents that actually perform reliably in production.
Happy to answer questions or dive deeper into how it works!
Both excited & grateful to everyone that worked so hard to turn tons of customer feedback into Lamatic 3.0.
We know that this is just another step on our path to powering the pivot to Software 3.0, but it's a big one. I'm most excited about Lamatic's new Flow Assistant. Not only does it help customers build better agents faster, it's also a cool example of using Lamatic to embed AI into a software product (it's mind-bending that Lamatic is being used to build Lamatic 🤯).
Please check out this list of everything else that's new in 3.0 and let me know your favorite new feature!
@dan_webvizio We have been waiting for you all along, secretly understanding your requirement and building relentlessly.
Report
Maker
Hi ProductHunt,
I work as DevRel Lead @Lamatic.ai , and I’ve been deeply involved in working the developer experience, documentation, and use cases.
We’d love to hear any doc-related thoughts you have, whether it’s something you enjoyed or an idea to enhance the experience. Every perspective helps us refine Lamatic in the right direction.
Looking forward to being part of your journey with Lamatic 3.0!
Replies
Zivy
Interesting Product @chuck_whiteman @arun2728 @naitik_kapadia . I’m curious how the new flow builder changes day-to-day use. Does it actually make complex automations easier to set up without extra guidance?
@chuck_whiteman @arun2728 @naitik_kapadia @harkirat_singh3777
A LOT easier! The Flow Assistant will actually create them for you, but the Builder itself simplifies the process even if you're building from scratch by hand.
Lamatic.ai
Thanks @harkirat_singh3777 for the questions. Our focus is to make Agentic automation easier without compromising on developer controls. Here a few way how we make it easier -
Node Based System - we have precomposed AI, Data and Logic Nodes which are specifcally designed for AI use cases
Drag and Drop Flow builder for complex agentic architecture like ReAct, Multi Agent, Supervise
Built in Debugging and Tracing
AI Assistant to help you build flows, Write Code, prompts and test cases
Agent Optimization tools like A/B Test, Fallback, Retry and Parallel Logics.
Check it out our docs https://lamatic.ai/docs/flows
Lamatic.ai
@harkirat_singh3777 Absolutely! We’ve redesigned the flow builder to feel far more intuitive in everyday use. One of the biggest friction points earlier was variable mapping, and the new selector that @ian_dsouza built removes a lot of that confusion by giving you clearer visibility while you build.
Plus, if you hit a roadblock at any point, there is an AI assistant available on every screen. Whether you need help crafting a prompt, choosing the right node, or even creating your whole flow, the assistant steps in right where you need it.
The goal is to let you create complex automations with confidence and without needing constant guidance.
Lamatic.ai
Hey Product Hunt! 👋
While the rest of the team focused on the core infrastructure and visual flow, my mission for Lamatic 3.0 was to make the actual building experience effortless using—you guessed it—AI.
I’m thrilled to introduce the Family of AI Assistants living inside the Studio. I built these to act as your co-pilot, so you never get stuck on a blank screen.
We shipped:
✨ Vibe Builder: Generate full AI agents from a single screen just by describing what you want.
✨ Flow & Node Assistants: Get real-time guidance and a mini-expert inside every node to optimize inputs and fix errors.
✨ Code & Prompt Assistants: Write, refine, and debug code or prompts with contextual suggestions without leaving your workspace.
A massive shoutout to @arun2728 for the guidance and help in bringing this architecture to life!
I would love to know: which part of agent building do you usually find the hardest? Hopefully, our new assistants can help solve that! 👇
Lamatic.ai
Hey Product Hunt! 👋
I'm a Founding Engineer at Lamatic.ai, and I’m the one behind our new Version Control & Environments (Branches) system in 3.0.
Our goal with this release is simple: make the entire user journey smoother, more reliable, and production-ready.
🤔 Why do you need Version Control Systems?
Building production-grade AI agents demands the same engineering discipline as any real-world software system - and that starts with version control. When you're transforming domain expertise into dependable AI flows, you need clarity on every change:
Which prompt performed best?
What model configuration worked?
Who modified what—and when?
That’s why we brought GitHub integration directly into Lamatic Studio. It gives teams a familiar workflow while adding the ability to automatically audit changes, roll back flows or deployments, and maintain full accountability across the board.
🌱 Why environments (branching) matters?
Branching is especially powerful for agent development. It lets you cleanly separate production from development - so you can experiment freely without risking live systems. Spin up a branch, test safely, iterate fast, and merge only when the flow is stable.
In AI systems - where even a tiny prompt tweak can shift behavior dramatically - version control isn’t a nice-to-have. It’s the foundation for building agents that actually perform reliably in production.
Happy to answer questions or dive deeper into how it works!
Agnes AI
Specific agents with domain expertise are definitely game-changer. How does Lamatic AI measure "reliable"?
Lamatic.ai
Thanks for @cruise_chen this great question.
Test Driven Building - Lamatic Has Support for built in Test Cases which can be used throughout the build process to see response output.
Deployment Test - Test Cases can be setup to automatically test when Agents are deployed, if test fail -> automatic rollback
Real time traces - View incoming request and time travel user interactions
Reports - Comprehensive Flow level analytics of your Project.
Are there any particular aspect of Agent Reliability which you prefer?
Swytchcode
Excited to see what lamatic is building. Congratulations on your version 3.0 launch
Humans in the Loop
@chilarai thank you for your continuous support!
👋Hola Product Hunt!
Both excited & grateful to everyone that worked so hard to turn tons of customer feedback into Lamatic 3.0.
We know that this is just another step on our path to powering the pivot to Software 3.0, but it's a big one. I'm most excited about Lamatic's new Flow Assistant. Not only does it help customers build better agents faster, it's also a cool example of using Lamatic to embed AI into a software product (it's mind-bending that Lamatic is being used to build Lamatic 🤯).
Please check out this list of everything else that's new in 3.0 and let me know your favorite new feature!
Smart tagging
Prompt IDE
Redesigned Flow Builder
Updated Studio
Node Logic
Model Logic (with A|B testing, retry, etc.)
Environments
Version Control
Expanded & Improved Templates
Agent Kits
Prompt Assistant
Code Assistant
Node Assistant
Vibe Builder
Flow Assistant (my favorite!)
Thanks all for your continued support as we keep working hard to support builders everywhere! 🚀
Webvizio
Whoa ... that's a lot of new stuff. How long have you been keeping all this from us? I can't wait to try out the new Assistants!
Lamatic.ai
@dan_webvizio We have been waiting for you all along, secretly understanding your requirement and building relentlessly.
Hi ProductHunt,
I work as DevRel Lead @Lamatic.ai , and I’ve been deeply involved in working the developer experience, documentation, and use cases.
We’d love to hear any doc-related thoughts you have, whether it’s something you enjoyed or an idea to enhance the experience. Every perspective helps us refine Lamatic in the right direction.
Looking forward to being part of your journey with Lamatic 3.0!
Humans in the Loop
@vrijraj curious what's a great developer experience from your perspective? any concrete examples from @Lamatic.ai you're really proud of?
Congratulations on the launch 🎉 🎉
Humans in the Loop
thank you! please do spread the word on LinkedIn, repost this
This is precisely the unlock we needed for cross-functional Agent building. Looks exciting!!