Cost
98 / 100 credits · within its cap.
100 / 100 credits · paused at its cap.
Alex · budget decisionDeploy autonomous agents that understand your applications in business terms and take on software engineering work, from building new features to fixing bugs and testing software. They collaborate with your people, operate within engineering-defined rules, and extend your team's capacity.
Alex connects Nordwind ERP to Rubbr, deploys Support Triage and keeps product, support and engineering decisions with people.
Autonomous Agents
Each agent has a job: where it looks, what it may do, and what it may spend. Their findings arrive with evidence, and a person keeps the decision.
Qualifies feature requests against the real product: sized, sourced, the ones worth a look flagged.
Investigates escalated tickets in the code and a sandbox.
Builds features from agreed requirements and prepares them for review.
Reproduces a bug, fixes it and opens a tested pull request.
Reviews pull requests against your product and your rules.
Keeps the catalogue of your product's features current as the code changes.
Keeps user documentation in step with the product.
Tests your critical user journeys every night.
Makes your pipeline faster, cheaper and more reliable, and removes flaky tests.
Describe a job in your own words: where to look, what to aim for, how much it may spend.
Business-first by design
Rubbr connects your application’s features and workflows to their implementation. Product, support and engineering collaborate with agents in shared conversations, each bringing their expertise.
Invoice due date
Rubbr
The due date is recalculated from the invoice date and the payment terms every time the draft is saved. A date typed by hand is overwritten.
invoice.class.php:412–438Rubbr
Updating the shared brief…
Ana Product
Keep manually entered due dates.
Marco Engineering
Explain when a date moves to month end.
Control
Your rules decide what agents take on, who must approve, and how much they may spend. Keep the rest with your team.
9 agents · your rules, your budget
| Agent | Status | Current task | Budget · credits |
|---|---|---|---|
| Support Triage | RunningBudget reached | Current taskInvestigating ticket #8816Paused at its budget cap | Budget · credits98 / 100100 / 100 |
| Product Analyst | RunningAwaiting scope | Current taskQualifying request R-112Finance scope requested | Budget · credits42 / 80 |
| Bug Fixer | CheckingAwaiting review | Current taskTesting credit-note fixPR #4182 · checks passed | Budget · credits64 / 120 |
6 other agents running
98 / 100 credits · within its cap.
100 / 100 credits · paused at its cap.
Alex · budget decisionInvoicing scope only.
Finance and Accounting · approval needed.
Alex · functional scopeChecks running. Review required before merge.
Checks passed. Review required before merge.
Marco · engineerLive activityQA Engineer · payment journey passed in the sandbox.Support Triage · budget cap reached. Agent paused.Product Analyst · scope requested. Access unchanged.Bug Fixer · checks passed. Engineering review requested.
Agents handle routine changes; a person approves.
Product shapes the change with Rubbr; engineering reviews.
Engineers use their own coding agents, such as Codex or Claude Code, with Rubbr assisting where useful.
Your rules choose the approach. Some work stays entirely with your team.
How it grows with you
The agents and rules that work on day one are the same building blocks you program later. Nothing to rebuild when you outgrow the defaults.
Day one
Connect your tools. Rubbr understands your application and proposes agents and rules for you to approve.
Every week
See what they’ve done, what it cost, and what needs your attention. Your feedback guides their next steps.
When you want
Customize rules, workflows, and approvals. Build your own agents and connect your own tools.
Integrations
Rubbr reads from and writes to your tools, and works next to the coding agents your engineers already use. There is no new process to adopt and no migration to plan.
Not tied to one model provider.
The platform
Everything above is made of six blocks. Use them as they come, or program them: they are code and configuration in your repository.
Answers from a catalogue of features, the code graph and the source, and says which.
catalogue · code graph · sourceDecides what may ship and who must approve, from a file in your repository.
.rubbr/policy.yamlA workflow runtime that records what each result rests on, so a step proved wrong later is repaired from there.
v0.3 · active developmentRuns every change Rubbr builds and every proposal in its own isolated copy of your application.
one sandbox per change · no keys insideAdds your own agents, tools and integrations through one mechanism.
agent: bug-fixer · tools: [read, edit, run]Always-on agents run as workflows when the path is known, or as freer agents for exploratory work, inside your policy, budget and access rights.
triggers → coordinator → workers → report