Ansible Workbench · Live · free trial
An Ansible IDE in the browser, wired to the same runtime as your pipeline.
A browser-based Ansible IDE. Each developer gets an isolated workspace with ansible-navigator wired to the same AWX execution environment the pipeline uses.
Overview
Sign in and get an isolated VS Code workspace that already knows how to run playbooks — inside the very execution environment your automation will run in later. No local setup, no version drift between laptops.
One workspace per developer
Signing in starts a private code-server container. Your files, your extensions, your terminal — reachable from a browser, nothing installed locally.
The same execution environment as CI
ansible-navigator in the workspace is pointed at the shared AWX execution environment image. Working in the IDE and passing AWX QA stop being two different things.
Single sign-on, self-service
Authentication is OIDC against Keycloak. Enable registration in the realm and developers onboard themselves; no ticket, no manual account creation.
Multi-tenant by construction
Workspaces are separate containers with their own lifecycle and an idle timeout, so an abandoned session stops consuming the host.
How it works
- You sign in through Keycloak (OIDC).
- A Flask gateway starts or resumes your personal code-server container.
- The container's entrypoint configures ansible-navigator to use the shared execution-environment image from the registry.
- nginx proxies your browser to that container under your own path.
- An idle timer stops the workspace when you stop using it.
Where it runs
Self-hosted. It is a Docker Compose stack you can run on your own infrastructure, alongside your own AWX and registry.
What it is not
It is not a hosted SaaS with your source on someone else's disk. The trial runs on our infrastructure; a deployment runs on yours.
Let’s talk