Open source, self-hosted, and documented at ansibleforms.com.
Your playbooks already know how to do the work; AnsibleForms lets users ask for it. Describe a form in YAML, fill its dropdowns from databases, REST APIs and JavaScript expressions, and every submission becomes the extravars of an Ansible playbook, a template on AWX, AAP, Ascender or Semaphore, or a job on Rundeck or Jenkins, with approvals, schedules and a full job history along the way.
- Cascaded dropdowns fed by databases, REST APIs and JavaScript expressions, with field dependencies
- Standalone jobs or multi-job workflows, with approvals, and one-off or recurring schedules
- Notifications by email, Slack, Teams, Telegram or webhook
- Role-based access with local, LDAP, Microsoft Entra ID and OIDC (Keycloak, Okta, Auth0, Authelia) logins
- Credentials kept encrypted in the database or fetched from HashiCorp Vault and CyberArk, masked in job output
- A chat assistant and an MCP server, so users and AI agents can find and launch forms
- Configuration as code, a built-in form designer, and a REST API with interactive docs
- Runs on Docker or Podman, on Kubernetes, or natively on a Linux server, installed in one command
