A local control plane for AI-assisted software development. No magic-from-a-socket — instead a structured production line of wizard, supervised runs, Git discipline and an automatic quality gate. Reproducible, traceable, sign-off-able.
New · v0.19.0 Security & honesty hardening: governance is now actually enforced (compliance profiles take effect), authorization sealed (RBAC on all write endpoints, IDOR closed), an audit chain head against tampering, and honest limits (gateways experimental, sandbox, a Known-Limitations page). Before that, v0.15.0 brought the enterprise/sovereignty expansion (P0–P4: tenant foundations, attestation, policy-as-code, SBOM). All news →
The four-step wizard only asks what's needed for a concrete
project. Six templates for the most common stacks —
Spring Boot, .NET, Python, Node, Static Frontend, Existing-
Repo-Import. The result: PROJECT.md,
AGENTS.md and an initial prompt you can preview
before starting.
Run orchestration with live logs, token stream and
container sandbox. Every agent runs with hard limits
(--cpus 2 --memory 4g --network=none), writes
only to the workspace, every change is a commit. Browser
notification when you need to make a decision.
Inline diff before every approval. Automatic quality gate from five reviewer roles — Security, Architecture, Hallucination, plus two vendor reviewers. No "Approve / Reject" blind flight, but findings sorted by confidence.
Reference architecture, agent orchestration, guardrails and SDLC integration — as an architecture document, not a tool comparison. If you want to know why the factory is cut this way, start here.
Coding agents are already good at solving individual problems. They are bad at sticking to structure, cutting commits sensibly, getting reviews and checking their own output. The Software Factory takes those steps over — not the creative part.
The result: AI-assisted development that an architect can hand to a client without cleaning up the trail afterwards.
The Architect gets the strongest available frontier model, the Reviewer a lean, fast one — saving tokens where quality isn't hurt and giving the strong model to the strategic roles. The concrete mapping comes from the model registry and follows new releases automatically.
Before every run the platform writes
.claude/settings.local.json and
.claude/agents/<role>.md into
the workspace. Subagents are natively delegable
without touching the CLI.
Optional: every agent runs in an ephemeral Docker
container with hard limits,
--read-only root and
--network=none. The answer to "is it
running on my filesystem?" is: no, only on its
mount.
At WAITING_FOR_APPROVAL the platform
shows the final git diff. You see what
the agent changed before you press the button.
Wizard step 4 shows a token and EUR estimate — before the first run, without a vendor call. JTokkit computes locally.
Software architect with over three decades between mainframe (z/OS, Cobol, REXX) and cloud (Java/Spring, AWS, Azure, Kubernetes, microservices). In the frontend with Apache Wicket and Angular, in mobile founder of a German-speaking Xamarin community.
Certifications (selection): Claude Partner Network (Anthropic), CKAD — Certified Kubernetes Application Developer (CNCF), CCA-Foundations, AWS Certified Cloud Practitioner, Microsoft Certified: Azure Fundamentals (AZ-900), iSAQB CPSA-F (software architecture) and Oracle Certified Professional 12c.
The Agentic Software Factory is my attempt to embed AI agents into the software lifecycle in a way that makes them productive even under mid-market and compliance constraints — structured, traceable, sign-off-able rather than blindly generated.
