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.

Configuring recurring cron jobs via version-controlled YAML manifests becomes seamless with GoCron, giving systems engineers and DevOps administrators a responsive web console to orchestrate scheduled commands with hot-reloading and sandboxed execution. Administrators can declare schedules using standard five-field cron syntax, establish global default configurations, and inherit execution timeouts, retry policies, and environment variable expansions across individual tasks. The interactive web interface provides immediate visibility into upcoming runs, past execution durations, status badges, and expandable terminal output logs stored in local SQLite databases. Operators can trigger ad-hoc job runs on demand, cancel stalled processes, and utilize a built-in sandboxed terminal utility governed by strict command whitelists. Automated health check webhooks dispatch HTTP notifications to external monitoring services upon job initiation, successful completion, or unexpected execution failure. The container environment bundles common server utilities including Restic, BorgBackup, and Rclone, streamlining automated offsite database backups and cloud storage synchronization routines without additional dependencies. Dynamic configuration reloading automatically detects filesystem modifications to YAML manifests without restarting the daemon, ensuring zero-downtime schedule updates. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.