THE KEY RULE
The agent never decides.
Only people approve a plan, resolve a comment or merge. The agent writes code, runs tests and fixes review comments, but every decision that matters stays with your team, and every action is written to an audit log in plain sentences.
What Axon does
- Turns requirement documents into epics, stories and tasks
- Writes a plan before any code
- Builds and tests in an isolated sandbox
- Opens GitLab merge requests for review
- Fixes review comments on request
WORKFLOW
How Axon Works
Three steps from requirement to merged code, with a human checkpoint at every step that matters.
1. Plan
Upload requirements in Word, PDF, Markdown or text. A model drafts an epic, its stories and small tasks. People keep what makes sense, assign it and move stories to Ready.
2. Build
A Developer runs a Ready story. The agent writes a plan, a person approves it, then the agent builds and tests on its own branch in an isolated sandbox.
3. Review
A Reviewer reads, comments, asks for changes, approves and merges. The agent can fix comments but never resolves or merges.
People approve every critical decision
FEATURES
Features of PixDynamics Axon
Requirements to Backlog
Import a document and a model drafts an epic, stories and tasks in about half a minute. Nothing is added until you confirm, and existing items are reused, not copied.
Plan Approval Gate
The agent reads the code and writes a plan without changing a file. Approve or reject it with a note; your note is the first thing the build step reads.
Live View and Steering
Watch files, terminal and steps as they happen. Type a message to change direction, or pause and stop safely without losing work.
GitLab-Native Review
Merge requests open automatically. Reviewers comment with a severity, add line comments with suggested fixes, and everything is mirrored to GitLab.
Fix with the Agent
The agent answers each review comment on the same branch, up to three tries. Stale suggestions are refused, never applied blindly.
Project Chat and Knowledge
Ask questions answered from the build log, rules and requirements. Add project facts that every agent reads before a task starts.
FIVE ROLES, ONE TEAM
Clear Roles, Enforced by the Platform
Administrator
Sets the platform up for the whole organisation.
Creates projects in GitLab from the platform, gives people their roles and manages keys, models, usage and cost, backups and the audit log.
What an Administrator does
Create projects and switch them on for agents
Choose local or cloud models
Track tokens and spending by day and model
Make, check and restore backups
Maintainer
Plans the work for one project.
Uploads requirements, drafts stories with a model, assigns people, sets stories to Ready and writes the project rules. A Maintainer cannot merge.
What a Maintainer does
Upload requirements and draft stories
Assign a whole epic in one step
Log bugs and ideas with duplicate detection
Write project rules with full history
Developer
Runs the agent and steers it.
Starts their own Ready stories, approves the agent's plan, watches and steers it live, sends the work for review and fixes comments with the agent.
What a Developer does
Run a Ready story on its own branch
Approve the plan, steer, pause or stop
Send for review as a GitLab merge request
Fix comments or apply suggestions
Reviewer
Reads the work and decides.
Reads every changed file, comments, asks for changes, approves, merges and delivers the finished epic to main.
What a Reviewer does
Comment with Must fix, Should fix, Idea or Small thing
Add line comments with suggested fixes
Mark every file viewed, approve and merge
Deliver the epic with a release checklist
Viewer
Sees everything, changes nothing.
Can read everything in the project, which makes it the right role for stakeholders, managers and auditors.
Good to know
Roles are set per project
A person can be a Maintainer here and a Viewer elsewhere
Every Home page shows what waits for that person
SAFETY NETS, ALWAYS ON
Why Choose PixDynamics Axon
for Governed Development?
Isolated Sandbox
One sandbox per run with no open internet. Models are reached only through an egress proxy and a gateway.
Spending Caps
One key per run, a spending cap and every model call recorded. Step and time limits stop runaway jobs.
Watchdog
Ends a step that goes silent, explains why and offers a retry. The same error six times stops a run.
Evidence Gate
If a build changed nothing and passed no test, a person decides whether to continue or stop.
Secrets Scrubbed
Secrets are removed from logs, and comments sent to GitLab can never run as commands.
Guarded Merges
Failed checks block a merge, and every file must be marked viewed before Merge is enabled.
Full Audit Log
Who did what, in plain sentences, for every person and every agent action.
Safe Retries
A failed or cut-off step shows a plain reason and Try this step again, up to three times.
ACCESS CONTROL
Who May Do What
Separation of duties is built in: the person who builds is never the person who merges.
| Action | Admin | Maintainer | Developer | Reviewer | Viewer |
|---|---|---|---|---|---|
| Create projects, give roles, manage keys and models | - | - | - | - | |
| Plan: requirements, stories, assignments, rules | - | - | - | ||
| Run the agent and approve its plan | - | - | |||
| Send for review, fix with the agent | - | - | |||
| Comment, approve, merge | - | - | - | ||
| Read everything in the project |
A Developer may start only their own stories. An Administrator may merge while checks are still running, never over a failed check.
UNDER THE HOOD
Simple, Resilient
Architecture
Runs with Docker Compose in your own environment. One source of truth, optional helpers and a separate sandbox for every run, so you can give agents real work without losing control.
Postgres as the source of truth
Optional Redis and workers
GitLab holds the code
Local or cloud models
Claude Code or OpenHands
Test workspace for every app
2,279
backend tests passing
584
frontend tests passing
81
live checks in Chrome
15
problems found and fixed
Ready to Ship with AI Agents?
See PixDynamics Axon take a requirement document to a reviewed, tested and merged feature inside your GitLab, with your people in control of every decision.
Book a DemoFAQS
Frequently Asked Questions
No. The agent never decides. Only people approve a plan, resolve a review comment or merge. A Developer cannot approve or merge their own work either; that is for a Reviewer.
Each run gets its own sandbox with no open internet. The sandbox reaches models only through an egress proxy and a model gateway that issues one key per run, applies a spending cap and records every call.
Administrators choose which models agents may use, local or cloud. The platform can run Claude Code or OpenHands as the coding agent, selected on the Agent choice page.
Yes. Projects, branches, merge requests and review comments live in GitLab. Projects can be created and people given roles from the platform, and GitLab is updated first.
A failed or silent step shows a plain reason and a Try this step again button, up to three retries. The watchdog ends steps that go silent, and an evidence gate stops builds that changed nothing and passed no test.