An autonomous software factory

Software that
takes care
of itself.

Give it a goal. It builds customer software—and can fix, review and deploy changes to its own code while the factory is running. Autonomously.

Built by Perttu Isotalo. Running on real projects.

An illustration of the recovery loop. Not a live feed.

Already running.
Already doing the work.

1,000pull requests merged
3 weeksof reported activity
0human merge approvals

Reported by Perttu from his own factory, October 2026. Some regressions still need his guidance.

The work behind the work

Building software is one job.
Keeping the builder working
is another.

A failed pipeline can stop an agent just as easily as a developer. perttu.ai watches the factory from outside its execution loop, identifies what broke, and initiates the repair that lets the work continue.

01 / Human-led → autonomous recovery

The same work.
Less waiting between steps.

Human handoffs can leave eligible work waiting. The autonomous factory can start, review and deploy within its authority, while independent customer projects progress.

Shared elapsed-time comparison: human-led recovery can wait for availability, approval and handoffs between active processing stages. Autonomous recovery begins when eligible and continues through diagnosis, repair, review, deployment and retry without routine human handoffs. Active work is shown with equal duration in both lanes. Compute, tests, dependencies, authority or exceptional decisions can still block progress.
Illustrative timing, not a benchmark. The highlighted difference is waiting between steps.
See how the factory changes and deploys its own code +
Detailed recovery flow: perttu.ai diagnoses, OpenExec changes and reviews the factory code, deploys the repair and retries the original task. Independent customer work can continue.
Routine autonomous recovery. Some failures still need human guidance.

02 / Less time directing traffic

Step away.
Come back to
what changed.

The goal is to spend less time guiding every step. Observe progress, steer when needed, and let routine execution and recovery happen in the background.

YOUR FACTORY / WHILE YOU WERE AWAY↗
The work kept moving.
✓
Delivery continued

Implementation, review and validation progressed.

✓
A factory failure was repaired

The interrupted project was retried after the fix.

↗
The learning was recorded

A daily build journal captures what changed.

YOU RETAIN DIRECTIONWork resumed

Illustrative outcome summary

03 / Three layers. Distinct responsibilities.

The builder.
The console.
The outside observer.

One system, with a deliberate separation between doing the work, orchestrating it, and checking that the factory keeps functioning.

Autonomy needs authority.
The observer has authority to initiate factory repairs. Human guidance remains necessary for some regressions and decisions.

01OpenExecEXECUTION+

The implementor. It carries out software work through implementation, automated review, validation and delivery—including repairs to the factory itself.

02Agent ConsoleORCHESTRATION+

The interface and orchestrator. It coordinates work across projects and lets you observe progress, chat with the system and steer its direction.

03perttu.aiOBSERVATION+

The outside observer. It checks whether the factory is running, distinguishes factory failures from project failures, and initiates repairs so interrupted work can resume.

The build journal

What changed. What broke.
What we learned.

Explore the journal ↗

Keeping the original work in view

I followed several repairs through review and delivery, including a recovery of a live data source. The factory also left accepted work waiting for delivery, so I am tracing the original results rather than treating a…

Read the article ↗

A finished task still owes its result

I kept the factory moving yesterday, but much of its time went into reviews and repeated attempts to prove what had changed. Corrections reached the shared code while several original requests still waited on delivery…

Read the article ↗

Built from a personal question

Perttu IsotaloBuilder of perttu.ai
Can I build a system that takes over my work—and keeps itself capable of doing it?

That question started this journey two years ago. Today, the factory builds projects and improves its own machinery. The experiment continues in public, including the regressions, bottlenecks and lessons along the way.

Watch the factory grow.

Field notes from building a system that takes care of the work.

Read the journal ↗