Today we are releasing ASE 1.0 — Agentic Software Engineering — a self-hosted control plane for defining, launching, supervising, governing, and reporting on multi-agent software engineering work.
ASE is built for the engineering and platform leaders who have watched coding agents move from demo to production over the last eighteen months and asked the obvious next question: how do we run this with the same operational seriousness as the rest of our regulated software estate?
This release is our answer.
The problem we built ASE to solve
Coding agents are now genuinely useful. They plan work, write code, run validations, open pull requests, and increasingly cooperate across long-running tasks. In a regulated environment, that capability creates a new operational gap.
A single agent on a developer’s laptop is a productivity tool. A constellation of agents writing production code on behalf of an organization is something else: a workflow that crosses identity, access, change control, audit, and evidence boundaries. Most teams running agentic coding today are stitching that boundary together with shell scripts, ad-hoc logging, and trust.
That works until an auditor, a regulator, or an incident reviewer asks the questions our customers cannot afford to answer with a shrug:
- Which version of which prompt, model, and policy ran this change?
- Who approved the launch, and against which definition?
- What evidence do we have that the agent did not exceed its scope?
- How do we reproduce, or revert, what an agent did three weeks ago?
- Who owns the identity and the credentials the agent acted under?
ASE exists so those questions have crisp, defensible answers.