Product
Self-managed software for reviewable Ansible automation
BacklogZero is a self-hosted product that turns operational requests into reviewable Ansible playbooks and AAP job templates, using the ITSM, Git, and automation systems you already operate.
What it does today
- Agents draft Ansible playbooks from an IT request or an operator instruction.
- A person reviews and refines the draft before it is committed.
- The team commits the playbook to Git.
- BacklogZero creates an AAP job template. Controller runs only what you approve.
How the workflow operates
The supported path is request, draft, human review, Git, then an AAP job template. Review, commit, and execution approval stay with your team. They are not optional decorations on an unattended run.
An Agentic Orchestrator Between Your ITSM, Git, and AAP
You already run these systems. BacklogZero drafts, commits, and pushes between them.
Systems it works with
ITSM
Availability: Generally available — self-managed
Self-managed subscriptions work with Jira and ServiceNow.
Git
Availability: Generally available — self-managed
Self-managed subscriptions use Git through AAP projects.
Ansible Automation Platform
Availability: Generally available — self-managed
One BacklogZero install is licensed for one AAP environment. Job templates run on Controller under your existing controls.
Other ITSM or Git layouts
Availability: Custom FDE only
Layouts outside the self-managed integrations are separately scoped custom engineering.
Crane
Availability: Custom FDE only
Crane (Beta) exports AAP configuration as code, including export from AWX onto AAP. It is available in custom engineering engagements. AWX is not the control plane for the self-managed subscription.
Enterprise SSO
Availability: Custom FDE only
Enterprise authentication is not included in the self-managed subscription.
What you deploy and manage
You install a containerized appliance on infrastructure you operate, with scripts for Podbay, Podman, Docker, or a VM. You manage the appliance, the language model you select, and the connections to ITSM, Git, and AAP.
What stays on your infrastructure
- The default language model runs locally. No cloud LLM API key is required.
- Optional Anthropic or OpenAI configurations send prompts to those providers. That is a customer-selected exception to the local default.
- Playbooks you commit live in your Git. Job templates live in your AAP Controller.
- Crane does not export credential secrets from the source Controller.
- This site does not claim a compliance certification.
Review and approval
Generated playbooks are drafts. A person reviews them, commits to Git, and approves what Controller runs. The product does not execute unapproved automation.