SELF-HOSTED INFRASTRUCTURE AUTOMATION
Bring Ansible runbooks, Terraform workflows, pipelines, execution runners, credentials, scheduling and approvals together in one place—on infrastructure you control.
Built for infrastructure teams that want centralized orchestration while keeping automation execution inside their own environment.
WHAT ALPHIE DOES
From your first runbook to coordinated infrastructure workflows.
Keep all your automation credentials in one secure place — users, passwords, tokens, SSH keys, and Vault secrets — with simple, audit-friendly management.
Bring your existing automation with you by pointing Alphie at GitHub, Subversion, or local directories and running playbooks in minutes.
Stay in the loop with email updates when runbooks and pipelines finish, fail, or need attention — no constant dashboard watching required.
Model your environment with Targets, Hosts, and Sets so you can aim automation at exactly the machines you intend, and nowhere else.
Turn related playbooks into reliable pipelines so multi-step changes run the same way every time, not as one-off command lines.
Package playbooks, variables, access, and inventory into reusable runbooks that anyone on the team can safely launch with a click.
Offload work to lightweight runners while Alphie automatically chooses healthy, low-load nodes to keep jobs moving smoothly.
Generate Ansible Builder images through a guided form — no YAML wrangling or container expertise required.
Schedule runbooks and pipelines for later, and add approvals when you want another human to sign off before they run.
OPTIONAL EXTENSION
A separate self-service catalog for organizations that want users to request approved automations without working in the Alphie administration interface.
ARCHITECTURE
The Alphie Controller is the central brain. It handles user logins (via local accounts, LDAP, or SAML), stores configuration and job state in Postgres, and serves the web UI. Runners are lightweight workers that sit in your network and actually execute automations, runbooks, or remote actions. The Controller dispatches work to the Runners, collects results, and shows everything back in the dashboard — without needing to give every user direct access to each Runner box.
