Hi everyone,

This is a first look at the Autonomous Electronics engineer.

You give it a brief and it builds the board in stages: spec, block diagram, schematic, E-Sketch, layout, route, ECAD. Each stage is its own artifact you can open and inspect.

Our bold vision is for Everyone, regardless of their engineering know-how, to be able to create functional, manufacturable, multidisciplinary products using natural language - electronics, mechanical, controls and software/firmware. The same experience folks enjoy in tools like Lovable for vibe-coding, extended to complex, real-life systems.
We will continuously extend our part libraries for electronics and add specialized functions, like LED chip creation.
Soon we'll start a public PCB/chip library on our website, stay tuned.

Hey everyone,

A quick look at what we're about to ship. Render Studio 2.0 will land in Autonomyware.

Autonomyware takes a product from a single prompt to engineered parts and a full bill of materials, autonomously. Render Studio 2.0 is where that model becomes a shot you can actually use: a hero image for a pitch deck, a store listing, a client review or a turntable for social.

Here's what's coming:

Thanks for being part of our launch!

Your requests gave us some interesting challenges, especially around helping people find manufacturers and figure out how to sell what they make.

We shipped 10 updates during the day and finished #6 on Product Hunt. I ve included a few of the requests and what we shipped below.

Thank you to everyone who tried Autonomyware, asked questions, shared ideas or supported the launch. We appreciate it.
And welcome to everyone who followed us yesterday! We ll keep sharing updates here.
If you ve tried the product, let us know how it went and what you d like us to improve.

Vibe coding got people who'd never written code to try building apps. I keep wondering what those same people would make if getting started with a physical product felt more approachable.
Lately, my feed has been full of Astra and Opus 3D demos lately. I've spent eight years working in 3D, so seeing people describe something and start experimenting with a model is pretty exciting. Now I want to see what they'll create and how far their imagination stretches.
That's what we're working on at Autonomyware: you describe what you want to make and AI works through the design and engineering towards something buildable. Getting more people to try making their first physical product is a big part of why I'm involved.
So I'd love to hear from the people here building apps, websites, whatever else: have you ever wanted to make something physical and just had no idea where to start?
Tell me, what would you like to create?

Building projects requires collaboration.

Share your models directly from Autonomyware.
Turbofan Engine

WOW Our first users were cooking since launch!

Below you can find some pictures of the products created during the last week of testing and the first days of our launch, and the outcome is amazing!

Check out the full 3D models, including the B-rep data, in the Library on our website!

But there is more. Autonomyware creates market-ready products. This includes the requirements, the risk analysis, the architecture, and everything a world-class engineering team would create.

I joined this team a few months ago, and honestly it's been one of the craziest stretches of my career.

Rewind three or four years before this AI era really hit, writing code was the hard part. Slow, painful, every feature a grind. You measured progress in weeks.

Now I watch how in Autonomyware three/four words and it comes back with the entire product: the requirements, the 3D model, the risk analysis, the whole chain. The first time I saw it run end to end, I just kind of sat there. The speed still doesn't feel real, even building it from the inside.

During the development of our Engineering AI, I realized that today's AI models are mostly incredible librarians.
They've read almost everything, and they're brilliant at retrieving and remixing it. Ask for a picture of a chair and you get a convincing chair. But a picture of a chair and a chair you can actually build are very different things. One just has to look right. The other has to hold weight, fit together, and survive contact with the real world.
That gap is where the next phase of AI gets interesting. Not models that know what things look like, but models that understand how things work. Cause and effect. Physics. Whether two parts actually fit, not just whether they look like they do.
We realized that this is the hardest part when using AI in engineering: real, manufacturable products. It's unforgiving but in a useful way. If a language model is slightly wrong, the answer might sound a little off. In an engineering context, if a system is slightly wrong, a part gets driven straight through another one, and the assembly fails. You can't fake your way past reality.
We think that's actually the most honest benchmark for this whole shift. "Looks plausible" is where AI is today. "Works when you build it" is where we are going.
Curious what others working in AI think: where do you see the line between models that describe the world and models that actually understand it? And what's the domain that finally forces the difference?