A software factory, not an agency. An engineering studio, run as a method.
CandyFactory is an engineering studio in México. It is built for work on software that is already running: repos somebody else wrote, a backend nobody fully remembers, infrastructure that has to keep serving while the new thing goes in. How that work is done is the method. What holds it up is the rest of this page.
Things you can check without taking our word for it.
An engine that ships. Bonfire is the tooling we build with, and it is public: bonfire-ai on PyPI, installable today, with the source in the open.
A cadre of agents that does the work. Tests get written by one agent, the code that has to pass them by another, and a third verifies the result on its own. It is real, it runs, and we will run it in front of you.
Gates that stop us. They are inside those open repos where you can read them. They run on every change we make, they block work that is not right, and nothing ships until a person says so.
A method we practice on ourselves, continuously. Attach, comprehend, build, detach. It is how this page was built, and it is written out in full on the method page.
We would rather say this ourselves than have you find it out.
You will not find logos, case studies or a wall of names on this page, and that is not modesty. For the work this page describes, there are none.
We have not run this method on another company's system. Not once. It is proven on our own work and offered outward. When that changes, this paragraph changes with it, and you should hold us to that.
The discipline is the method, not the headcount.
A bigger room does not make a system understood. What makes work trustworthy is that it passed something it could have failed, every time, with no way around it. That is a property of the method, and it holds at whatever size the shop is.
So we run the factory as a method rather than as a payroll. The cadre carries the volume, the gates carry the standard, and a person carries the judgement about what is worth building at all. What you buy is a defined stretch of that capacity, not a seat count.
Thirty years of production software.
None of this arrived with the models. The method is what three decades of building systems that had to stay up compressed into, in businesses where an outage was money leaving the building. The agents are new. The discipline they are made to obey is not.
That is the part worth knowing before you hand anyone access to your repos. If you want the full working history behind it, it is on the CV.
Tell us what you have.
Not what you wish you had. The messier the description, the more useful it is to us, because the mess is the thing we are equipped to read.