From task to pull request, checked before it reaches you.
David reads the project's repository, makes the change in an isolated sandbox and only delivers after the tests and the browser pass. If all you have is the idea, the Factory builds the product stage by stage.
14-day trial · No card · Then a free plan
David, Development: “Fix the date filter on Acme's report — task #212.”
It was the time zone in the filter. Fixed, the tests pass and the browser checked the task's 3 criteria. Shall I open the pull request? Open a pull request on Acme's repository. Pull request opened, with the diff reviewed. The merge is yours.
Studio Bravo is a demo company. Made-up data.
Development, before and after
The client's request becomes a task, the task becomes a message to the dev, and the context gets lost on the way.
David starts from the project's task, with the repository linked and the scope in view.
Nobody knows if the fix works until someone opens the system and tests it by hand.
A real browser opens the change and checks every acceptance criterion before delivery.
Reviewing AI code means reading a huge diff without knowing what was tested.
The pull request arrives with an independently reviewed diff and the tests already run.
A product idea turns into months of meetings before the first line of code.
The Factory researches, specs and builds in 11 stages, stopping for your OK at the decisions.
From repository to live product
Two modules: one for the code you already have, one for the product that doesn't exist yet.
Developer agent
David codes in your repository
Link the GitHub repository to the project. David clones it, reads the code, makes the change and runs the tests in an isolated sandbox — and you follow it all in the workspace.
- An isolated sandbox for each job
- Preview, diff and files in the workspace
- GitHub pull request only with your OK
QA
Checked before it reaches you
Before the pull request, a real browser opens the change and verifies every acceptance criterion. The diff goes through an independent review.
- Acceptance criteria checked in a browser
- Independent diff review
- Tests run in the sandbox
Data
The project's database, without leaving the workspace
Browse the tables, rows and columns of the database the project runs on, and run read-only SQL to understand a bug before asking for the fix.
- Tables, rows and columns
- Read-only SQL
- In the same workspace as the code
Factory
From idea to live product
The Factory researches the market, tests demand, writes the specification and builds the product with agents, in 11 stages from spec to launch. You approve every decision.
- Human checkpoint at the decisions
- Sprints with scope, cost and what each agent delivered
- Several products in parallel, each at its own stage
Code that knows who it's being built for
- From task to codeDavid starts from the project's task: scope, deadline and client are already there, no separate brief.
- From ticket to bugA problem reported to support becomes a task in the project, and whoever fixes it sees the ticket it came from.
- From product to operationsThe Factory has its own wiki, support and sales stages: what it launches is born on the base you run on.
Modules you can switch on today
Read from the same catalog as the module store: if it's listed here, it's in the product.
- Developer Agentfrom R$188/month
- Repository workThe developer agent clones the project's repository, reads the code, makes the change and runs the tests in an isolated sandbox.
- Pull requestsThe work is delivered as a pull request on GitHub, with the diff independently reviewed before it opens.
- Automated QAA real browser opens the change and checks each acceptance criterion before the pull request is delivered.
- Factoryfrom R$387/month
- PipelineSeveral products running in parallel, each at its own stage.
- SprintsSprints with scope, dollar cost and what each agent actually delivered.
Does he merge on his own?
No. Opening the pull request and merging it both ask for your OK, every time, and every action is logged.
Does it work with any repository?
With GitHub repositories linked to the project. Other providers aren't supported yet.
Do I need to know how to code to use the Factory?
No. You describe the idea and approve the decisions; the agents build. Building uses prepaid AI credits.
Where does the code run while he works?
In an isolated sandbox, with a clone of the repository. Nothing reaches your repository without going through the pull request you approve.
Be the owner again.Not the integrator.
Start with the area that hurts most. In 14 days you'll know whether BaseOS stays — no card, and a free plan afterward.
14-day trial · No card · Then the free plan