Building an AI Software Engineer our alpha users already think is lovable

Last year — just a month into development — something unexpected happened. We were surprise hunted on Product Hunt.

From Alpha to Beta, onward to an AI software engineer

We made #1 Product of the day & week. It took us by surprise. We scrambled to add an ‘alpha’ label to GPT Engineer, and we heard loud and clear signals we were onto something people wanted.

But that was just the beginning. Since that surprise hunt, we’ve personally onboarded hundreds of users from our waitlist, and relentlessly iterated based on it.

This wasn’t just about polishing rough edges; we’ve been experimenting with the very core of GPT Engineer. We tried multiple agentic AI architectures, combinations of LLM models, and abstractions to interface with models, edit code, and provide the iterative feedback loop needed to build real apps in real time.

The goal? To strike a balance between speed and reliability, give seasoned developers a tool to turbocharge productivity, integrate with workflows they love, while lowering the barrier to entry for anyone to create software.

Graduating from alpha to beta

We’re really proud of where GPT Engineer is today. In our latest iterations, we’ve found that founders, CTOs, product engineers, and maintainers of internal tools are able to build front-end & ship software faster than ever before. With that, we’re graduating from ‘alpha’ to ‘beta’.

The move to beta is more than a label change. Generating a new front-end takes on average 15 seconds, to go from prompt to prototyped. Edits take on average seconds — not yet WYSIWYG — but quick enough to stay in flow while iterating towards a viable product. Errors can be auto debugged by AI. Deploying takes a single click. We’ve made huge strides in both reliability, and capabilities.

In part, we’ve been able to achieve this by being opinionated in GPT Engineer’s tech stack. Front-end is built React, Tailwind & Vite. GPT Engineer can integrate directly with Supabase & OpenAPI specification backends, but for now we recommend using it to build front-end, and taking over in your IDE from there (everything syncs with GitHub, two-way).

Join the waitlist & shape the roadmap

The beta still has a waitlist, but if you’re a founder, product engineer, CTO, or internal tool builder — get in touch for immediate access, and be part of shaping the next phase of GPT Engineer to your needs.

We’re committed to a future where anyone can build software, and we believe this is just the beginning.

We’re excited to have you all along for the journey.

Let us know what you think

We’re always happy to hear any feedback you have. To reach us, you can: