Introducing Fei. The production grade, vibe coding, autonomous engineer.
Designed for teams that build real products. Fei works in your codebase, uses your components, maintains design system and coding standards, delivering real, production grade code.
We built Fei, because engineering and product teams don’t need another prototype generator. They need an AI teammate they can actually trust in production on their code!
While many AI tools generate code, most stop short of delivering code you’d actually merge. Fei works inside your codebase; reusing your components, following your coding standards, and writing code that passes review on the first try.
From Figma designs, Jira tickets, screenshots, or plain text, Fei translates requirements into backend-ready code in minutes, not days. Fei can even help product teams deliver on production ready prototypes, fully contextual to the code base and not slowing down the development cycle.
The result? Shorter development cycles, Scalable output without extra headcount, no compromise on quality or security, and peace of mind. :)
We believe this is the future of software development: agents that aren’t just “helpers,” but true teammates. Ones that know your stack, respect your conventions, and help you scale like never before.
We’ve already seen Fei accelerate dozens of teams across industries, and I couldn’t be more excited to share it with you today.
I would love to hear your feedback, questions, and/or thoughts!
Most AI dev tools focus on speed of generation. But at AutonomyAI, we asked a harder question: how do you ensure that what’s generated is actually usable in production?
That’s why we built Fei, our agent designed from the ground up to both understand and adapt to your codebase. Fei doesn’t just autocomplete, it:
Reuses your components and hooks into your existing infra
Respects your design system & coding standards
Delivers code that passes PR review the same way a senior engineer would
And it works across input formats: Figma files, Jira tickets, screenshots of a design, or even just plain text specs. Fei ingests requirements and outputs production-grade code in minutes.
Fei enables teams to accelerate shipping, scale output, and reduce review churns, all while keeping quality and security uncompromised.
For us, this isn’t about building a “faster typewriter.” It’s about creating an AI teammate that works alongside engineers the way they actually build.
Excited to hear your thoughts and feedback, and we can’t wait for you to try Fei in your own stack!
Fei actually coding straight into your codebase and keeping your team's standards? That’s wild—makes it way less scary to have AI help, ngl. Super smart move guys!
@cruise_chen Not directly, that would be frightening :) It works within the context of your codebase, meaning, it doesnt create "a red button" it creates "Your red Button" the specific one that exists in your codebase, that it should use.
Devs will still review and PR but the code they're going to be looking it is basically spot-on. :) That's the novelty.
Love the focus on reusing components and following design systems — that’s what often kills AI-generated code. One question: how customizable are the coding standards and linters Fei enforces (e.g., project-specific ESLint/Prettier configs or CI checks)? Would like to know how much tuning is needed per repo.
@jaredl Coding standards are Very customizable. When we model your repo, the coding standards are inferred into a simple text guidelines. You can change them and be as specific as you'd like.
This sort of flexibility was always at the core of our product :)
@jaredl It's also important to note that Fei compiles generated code with the project’s own tsconfig.json, so type rules and compile-time checks are enforced automatically per repo without needing to set configurations explicitly
This makes a lot of sense. I think you all are hitting a key gap that we have right now in using a lovable or cursor to edit already working production code and trust that it won’t change the entire setup, critical components, or even follow our best practices. Excellent work
that's the jackpot right there :) The introduction of PMs and other personas as meaningful contributors to a real codebase. It's the paradigm shift of which Fei is a small but meaningful first step :)
Fei works inside your codebase, reuses your components, and ships backend-ready code from Figma, Jira, or plain text. Faster cycles, zero headcount bloat, and review-passing quality by design.
@adir_ben_yehuda and team @AutonomyAI congrats on the launch. Fei looks pretty cool, looking forward to hopefully trying it out soon. I like the reusable components feature, definitely makes it stand out from Cursor, Lovable and the other tools out there. Looking forward to your continued success in this space 🚀.
Finally an AI that gets production code 😮💨 Actually uses our components, knows our stack, and first-try passes review. Slack integration? Chef’s kiss 🤌 Almost sold me.
@arynvtsa Fei handles this in two steps: first, it gathers all relevant context from your codebase to cover existing cases. Then, it strengthens the shared components in use, making them more maintainable and resilient to edge cases. You can run this automatically or trigger it on specific components to focus where you need! This helps cover edge cases missing in the current component library in the codebase
@Product Hunt: I couldn't sign up using my corporate LinkedIn because the regex on the URL is wanting a person's profile - no offense I don't need everything to be about me personally. Also huge text area to put in a description, but after 15 characters I was told it was too long. So I put an "x" in there . . .since it is required, and all I wanted really was to post this comment (which has taken 15min now instead 60 seconds I thought it would):
@AutonomyAI : Would love to try Fei, but I couldn't see the pricing up front (a requirement for my firm to do business with another firm) and I couldn't try it without talking to a human first (I declined the calendar and the workflow just stopped on that page like, oh, guess we don't go to the next step then, player). . . could be FF. I don't use Chrome unless forced. But if there is a path to those two things - please email me info@altonveridian.com - thanks!
Replies
AutonomyAI
Thank you for supporting us!
We built Fei, because engineering and product teams don’t need another prototype generator.
They need an AI teammate they can actually trust in production on their code!
While many AI tools generate code, most stop short of delivering code you’d actually merge. Fei works inside your codebase; reusing your components, following your coding standards, and writing code that passes review on the first try.
From Figma designs, Jira tickets, screenshots, or plain text, Fei translates requirements into backend-ready code in minutes, not days. Fei can even help product teams deliver on production ready prototypes, fully contextual to the code base and not slowing down the development cycle.
The result? Shorter development cycles, Scalable output without extra headcount, no compromise on quality or security, and peace of mind. :)
We believe this is the future of software development: agents that aren’t just “helpers,” but true teammates. Ones that know your stack, respect your conventions, and help you scale like never before.
We’ve already seen Fei accelerate dozens of teams across industries, and I couldn’t be more excited to share it with you today.
I would love to hear your feedback, questions, and/or thoughts!
AutonomyAI
Most AI dev tools focus on speed of generation. But at AutonomyAI, we asked a harder question: how do you ensure that what’s generated is actually usable in production?
That’s why we built Fei, our agent designed from the ground up to both understand and adapt to your codebase. Fei doesn’t just autocomplete, it:
Reuses your components and hooks into your existing infra
Respects your design system & coding standards
Delivers code that passes PR review the same way a senior engineer would
And it works across input formats: Figma files, Jira tickets, screenshots of a design, or even just plain text specs. Fei ingests requirements and outputs production-grade code in minutes.
Fei enables teams to accelerate shipping, scale output, and reduce review churns, all while keeping quality and security uncompromised.
For us, this isn’t about building a “faster typewriter.” It’s about creating an AI teammate that works alongside engineers the way they actually build.
Excited to hear your thoughts and feedback, and we can’t wait for you to try Fei in your own stack!
Agnes AI
Fei actually coding straight into your codebase and keeping your team's standards? That’s wild—makes it way less scary to have AI help, ngl. Super smart move guys!
AutonomyAI
AutonomyAI
@cruise_chen
Not directly, that would be frightening :) It works within the context of your codebase, meaning, it doesnt create "a red button" it creates "Your red Button" the specific one that exists in your codebase, that it should use.
Devs will still review and PR but the code they're going to be looking it is basically spot-on. :) That's the novelty.
Tidyread
Love the focus on reusing components and following design systems — that’s what often kills AI-generated code. One question: how customizable are the coding standards and linters Fei enforces (e.g., project-specific ESLint/Prettier configs or CI checks)? Would like to know how much tuning is needed per repo.
AutonomyAI
@jaredl
Coding standards are Very customizable.
When we model your repo, the coding standards are inferred into a simple text guidelines. You can change them and be as specific as you'd like.
This sort of flexibility was always at the core of our product :)
AutonomyAI
@jaredl It's also important to note that Fei compiles generated code with the project’s own tsconfig.json, so type rules and compile-time checks are enforced automatically per repo without needing to set configurations explicitly
PopHop
Super happy about this launch. Congratulations, team!
AutonomyAI
@thilina_guruge Thank you so much! :) A very competitive day. But we're happy to see it released.
AutonomyAI
@thilina_guruge thank you for the support!
Pocketlink
this looks really powerful! what's the pricing like?
AutonomyAI
@arynvtsa Thank you! Pricing is super easy, a license per user and get this- unlimited usage!
SeedLegals
I'm a huge fan of vibe coding. It's changed everything. Fei looks brilliant!
AutonomyAI
@anthonyrose Thank you so much!
We like to call working with Fei "Production Grade Vibecoding". It's pretty awesome. Do think it'll stick? :)
AutonomyAI
@sean_peterkin thanks Sean! That's exactly it, we felt that gap and engineered the agent to overcome it 💪
Amazing product! This is a gem for both PMs and devs looking to go beyond ordinary vibe-coding tools
AutonomyAI
@davida_ginter1
that's the jackpot right there :) The introduction of PMs and other personas as meaningful contributors to a real codebase. It's the paradigm shift of which Fei is a small but meaningful first step :)
Fei works inside your codebase, reuses your components, and ships backend-ready code from Figma, Jira, or plain text. Faster cycles, zero headcount bloat, and review-passing quality by design.
Patio
Really like the focus on making UI work production-ready out of the box 👏
AutonomyAI
@julien_rioux thank you Julien!!
Sellible
@adir_ben_yehuda and team @AutonomyAI congrats on the launch. Fei looks pretty cool, looking forward to hopefully trying it out soon. I like the reusable components feature, definitely makes it stand out from Cursor, Lovable and the other tools out there. Looking forward to your continued success in this space 🚀.
AutonomyAI
@preetraj thank you! and i'm happy to give you a run on Autonomy to see the impact!
Super impressed. It actually writes production-ready backend code that fits my stack. Way beyond your average AI dev tool.
Finally someone who's serious about building with AI, this is the future. Faster shipping, fewer bugs, zero fluff.
Finally an AI that gets production code 😮💨 Actually uses our components, knows our stack, and first-try passes review. Slack integration? Chef’s kiss 🤌 Almost sold me.
Pocketlink
the production-ready approach sounds promising! how does fei handle edge cases that might not be covered in the existing codebase? :)
AutonomyAI
@arynvtsa Fei handles this in two steps: first, it gathers all relevant context from your codebase to cover existing cases. Then, it strengthens the shared components in use, making them more maintainable and resilient to edge cases. You can run this automatically or trigger it on specific components to focus where you need! This helps cover edge cases missing in the current component library in the codebase
Theres an issue with the signup, even tho i used my company email, it still tells me its invalid domain or my personal email.
AutonomyAI
@mohammed_nadeem1
Reach out to me on LinkedIn, we'll figure it out :)
@lev_kerzhner sent you a request a while back, anyway my email is nadeem@ohmyweb.in, i get the same error.
Crazy stuff!
Cant wait to use it.
seems like a AutonomyAI that i will keep using ...
@Product Hunt: I couldn't sign up using my corporate LinkedIn because the regex on the URL is wanting a person's profile - no offense I don't need everything to be about me personally. Also huge text area to put in a description, but after 15 characters I was told it was too long. So I put an "x" in there . . .since it is required, and all I wanted really was to post this comment (which has taken 15min now instead 60 seconds I thought it would):
@AutonomyAI : Would love to try Fei, but I couldn't see the pricing up front (a requirement for my firm to do business with another firm) and I couldn't try it without talking to a human first (I declined the calendar and the workflow just stopped on that page like, oh, guess we don't go to the next step then, player). . . could be FF. I don't use Chrome unless forced. But if there is a path to those two things - please email me info@altonveridian.com - thanks!