Rubbr

The business-first AI software factory.

Deploy 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.

Watch it work
The business-first AI software factory.
Film not available yet

    Alex connects Nordwind ERP to Rubbr, deploys Support Triage and keeps product, support and engineering decisions with people.

    Autonomous Agents

    A team of autonomous agents. Each with a job.

    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.

    Product Analyst

    Qualifies feature requests against the real product: sized, sourced, the ones worth a look flagged.

    Support Triage

    Investigates escalated tickets in the code and a sandbox.

    Feature Builder

    Builds features from agreed requirements and prepares them for review.

    Bug Fixer

    Reproduces a bug, fixes it and opens a tested pull request.

    Code Reviewer

    Reviews pull requests against your product and your rules.

    Catalogue Steward

    Keeps the catalogue of your product's features current as the code changes.

    Docs Writer

    Keeps user documentation in step with the product.

    QA Engineer

    Tests your critical user journeys every night.

    CI Optimizer

    Makes your pipeline faster, cheaper and more reliable, and removes flaky tests.

    Your own job

    Describe a job in your own words: where to look, what to aim for, how much it may spend.

    Business-first by design

    People and agents, working together. In the language of your business.

    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.

    Rubbr · Nordwind ERPsample data

    Invoice due date

    Ana + Marco

    Ana Product manager

    Why does the due date on a draft invoice reset when payment terms change?

    Rubbr

    1. Search the catalogue
    2. Read the invoice code

    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.

    Customer invoice draftinginvoice.class.php:412–438

    Marco Engineering

    Make it clear when the date moves to the end of the month.

    Rubbr

    Updating the shared brief…

    Shared brief

    • Ana Product

      Keep manually entered due dates.

    • Marco Engineering

      Explain when a date moves to month end.

    Control

    Your engineers stay in control of cost, risk and quality.

    Your rules decide what agents take on, who must approve, and how much they may spend. Keep the rest with your team.

    Rubbr · Nordwind ERPsample data

    All agents

    9 agents · your rules, your budget

    AgentStatusCurrent taskBudget · credits
    Support TriageBudget reachedCurrent taskPaused at its budget capBudget · credits100 / 100
    Product AnalystAwaiting scopeCurrent taskFinance scope requestedBudget · credits42 / 80
    Bug FixerAwaiting reviewCurrent taskPR #4182 · checks passedBudget · credits64 / 120

    6 other agents running

    Cost

    100 / 100 credits · paused at its cap.

    Alex · budget decision

    Risk

    Finance and Accounting · approval needed.

    Alex · functional scope

    Quality

    Checks passed. Review required before merge.

    Marco · engineer

    Live activityBug Fixer · checks passed. Engineering review requested.

    • Rubbr leads

      Agents handle routine changes; a person approves.

    • You work together

      Product shapes the change with Rubbr; engineering reviews.

    • Your team leads

      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

    Start on day one. Make it yours over time.

    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.

    1. Day one

      Your factory, ready to work.

      Connect your tools. Rubbr understands your application and proposes agents and rules for you to approve.

      • Application connected
      • Functional catalogue ready
      • Agents configured
    2. Every week

      Your agents get better.

      See what they’ve done, what it cost, and what needs your attention. Your feedback guides their next steps.

      • Weekly activity
      • Completed work
      • Feedback and decisions
    3. When you want

      Make the factory yours.

      Customize rules, workflows, and approvals. Build your own agents and connect your own tools.

      • Rules as code
      • Custom workflows
      • Agents & integrations

    Integrations

    Works with what you already run.

    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.

    • GitHub
    • Jira
    • Sentry
    • Datadog
    • Slack
    • Confluence
    • Notion
    • Codex
    • Claude Code
    • Your own tools

    Not tied to one model provider.

    The platform

    The building blocks of your factory.

    Everything above is made of six blocks. Use them as they come, or program them: they are code and configuration in your repository.

    01

    Product context

    Answers from a catalogue of features, the code graph and the source, and says which.

    catalogue · code graph · source
    02

    Rules as code

    Decides what may ship and who must approve, from a file in your repository.

    .rubbr/policy.yaml
    03

    Rubbr Workflows

    A workflow runtime that records what each result rests on, so a step proved wrong later is repaired from there.

    v0.3 · active development
    04

    Sandboxes

    Runs every change Rubbr builds and every proposal in its own isolated copy of your application.

    one sandbox per change · no keys inside
    05

    Agents and plugins

    Adds your own agents, tools and integrations through one mechanism.

    agent: bug-fixer · tools: [read, edit, run]
    06

    Background work

    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
    Explore the platform →

    See Rubbr on your own applications.

    Book a demo

    See Rubbr on your own applications.

    Tell us a little about your team, so the demo fits your context.

    What would you explore first? Optional