Architecture first
Every major system starts as an architecture decision record. The models build against written contracts, not loose prompts.
About
One architect. An AI coding team.
Up to now, Bract has been designed and built by one person: Ali Yıldırım, working on it full time and hands-on for almost a year, with top-tier AI models as his coding team.
Founder · Developer and architect · Full time on Bract
Ali Yıldırım
Ali has been building software hands-on for 25 years, as a developer and as a software architect. For almost a year, Bract has been his full-time work. It is the engine he has wanted to build for a long time: one where rendering, procedural generation, physics and streaming are designed together for worlds of any size, and run in a browser tab.
He sets the architecture, writes the decision records, works in the code every day and reviews the work. Top-tier AI coding models act as the team that implements it, which is how one person can build an engine of this scope.
How Bract is built
AI writes the code. Engineering decides what ships.
Working with AI models at this scale only works with discipline. These are the rules every change to Bract follows.
Typed boundaries
Subsystems meet through strict TypeScript contracts and swappable adapters, so changes stay local and reviewable.
Verified, not assumed
Changes pass type checks and automated suites, and engine work is checked visually in a real browser before it counts as done.
Human ownership
The direction, the design and the final review stay with the architect. The models write code; they do not decide what Bract is.
Bract is still in development and not production-ready. The same discipline is why we are careful to say what works today and what does not. See the development status →
Early access 2026
Build with us early.
Early access opens in waves for studios, technical artists and teams building large worlds on the web. Tell us what you are making.