Flowctl turns repetitive ops work, such as granting SSH access, restarting a service, or provisioning a server, into self-service forms that anyone on the team can run without holding credentials. Each workflow is a YAML or HUML file with typed inputs, validation rules, and a list of actions. Actions run in order or as a dependency graph, so independent branches execute in parallel. Every action runs in a Docker container, as a shell script, or as another flow, and scripts can target remote servers over SSH, several at once. Sensitive steps pause until a reviewer approves or rejects them. Output from one action feeds the next, files pass along as artifacts, and failed actions can be retried. Cron schedules with time zones and labels run flows unattended, while logs stream live in the browser. Email, Slack, Mattermost, and webhook notifications announce success, failure, waiting, or cancellation. Teams get isolated namespaces with user, operator, reviewer, and admin roles, OIDC single sign-on, and encrypted storage for SSH keys and secrets. A built-in flow editor means nobody has to hand-write files, and custom executors can be added as Go plugins. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

AnsibleForms turns Ansible playbooks into self-service web forms that colleagues can run safely, with the right variables, without filing a ticket or touching a terminal. A colleague picks the form, fills in fields that validate as they type, and the job launches with exactly the variables the playbook expects. Dropdowns can cascade from a database query, a REST call, or a small expression, so the environment list is never typed from memory and the wrong region is never an option. Forms feed playbooks running in runtime containers or templates on the AWX, Semaphore, Rundeck, or Jenkins servers you already have, and workflows chain them with conditions, success and failure paths, and an approval step when a person should look first. Runs can be scheduled, stored, aborted, and relaunched, with live output while they work and a full history afterward. Designers edit forms in the browser and keep everything in Git, sign-in stretches from local accounts to LDAP and OIDC, and credentials travel encrypted or straight from Vault. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.