01 / COST
Spend the right model on the right work.
Configure implementation and review models independently. Use lower-cost models where they pass your checks, and stronger reasoning where it earns its cost.
Curie brings AI agents into the workspaces your team already uses. Start with the Software Factory: turn selected engineering issues into reviewable pull requests while your team keeps the final say.
Put selected GitHub issues through a controlled workflow that plans, implements, checks, and returns a pull request for engineers to review.
Each issue runs in an isolated sandbox. Choose models for implementation and review, apply your approval policy before publication, and keep CI and engineers in charge of what merges.
Give the co-worker clear acceptance criteria in the issue tracker.
Follow planning, implementation, review, and verification as work progresses.
Inspect the pull request, checks, and cost before deciding what ships.
Most agents sit in a separate app. Your team works across issues, code, chat, and approvals. Curie connects the agent to that shared context, so work can move forward where the team already coordinates.
Useful work, isolated from the team’s daily flow.
A co-worker with an identity and a place in the workflow.
Delegate work, ask questions, and follow progress from the spaces you already use.
Work and decisions stay in shared context instead of disappearing into a private session.
Set model choices, approval boundaries, and budgets for the work you hand off.
WHY DEPLOY THE FACTORY
The factory is designed to help engineering teams move a bounded issue queue while keeping cost and acceptance visible.
01 / COST
Configure implementation and review models independently. Use lower-cost models where they pass your checks, and stronger reasoning where it earns its cost.
02 / BACKLOG
Admit well-scoped issues with a GitHub label. Isolated jobs can progress in parallel and return a pull request or a clear reason they could not finish.
03 / ROI
Compare accepted PRs, CI results, review effort, cycle time, and total model plus infrastructure cost. Engineers still decide what merges.
WORK WITH THE AGENTS YOU USE
Use an IDE agent, Claude Code, or Gemini CLI for interactive exploration, issue scoping, and PR review. The factory picks up selected GitHub issues for independent execution. The shared handoff is the issue and the resulting pull request.
Explore the open-source factory ↗01
Work locally with your preferred coding agent to investigate and define a bounded issue with acceptance criteria.
02
Apply the factory label to put that issue in the queue. Curie runs the job in an isolated sandbox.
03
Review the linked PR, checks, and cost in your normal GitHub workflow. Your team controls publication and merge.
The Software Factory is the first use case. The platform gives co-workers a shared foundation to run in your infrastructure and operate across workspaces.
Connect to the tools where work starts and where the result needs to land.
Shared memory facilities help the co-worker carry useful context across workspaces.
Configure models and inspect usage, with approvals and cost controls close to the work.
Curie is Apache 2.0 licensed and self-hostable. Start with the Software Factory, inspect how it works, and build from there.
Adopt the open-source platform on your own, or work with CurieTech on a production rollout and a broader AI transformation program.
Try the open-source platform and prove out a bounded workflow.
Get support for a production setup and the controls your team needs.
Bring more agents and workflows into the places your teams work.
See the Software Factory in action or talk through a co-worker for your team.