Nanocl screenshot thumbnail

Nanocl

One server, treated properly: Nanocl runs your containers and full virtual machines from a single declarative Statefile, reconciling what is running against what the file says, so a lone host gets cluster discipline without cluster ceremony. Containers group into Cargoes with replica counts, ordered init containers, and health-aware restarts; finite jobs run to completion and stop. When a workload needs a real kernel or a custom disk image, it boots as a QEMU virtual machine beside the containers instead of forcing a second platform. Publishing is built in: the proxy controller terminates TLS and routes HTTP and TCP traffic, and the DNS controller keeps service names resolving while workloads come and go. Secrets for registries, certificates, and environment variables attach where they are used, never inside the file itself. The daily loop is a CLI and an API: list processes, follow logs, exec into a container, watch events, and back up the entire deployment state before you change it. Namespaces keep projects apart on the same host, and Statefile arguments, templates, and sub-states carry one definition from staging to production. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT or Apache-2.0 licensed.

Deploy
Nautobot screenshot thumbnail

Nautobot

From the first rack to the last circuit, Nautobot is the open-source network source of truth that records what your network should look like and runs automation against it. Built-in models cover locations, racks, devices, interfaces, cables, VLANs, VRFs, IP prefixes, circuits, and contacts, so one searchable record replaces the spreadsheet and the wiki. Teams encode their own standards with custom fields, user-defined relationships, computed fields, and validation rules. Config contexts attach JSON or YAML data, such as syslog servers, to devices by location, role, platform, or tag. Jobs run your own automation code from the web UI, REST API, or command line, on a schedule, or through hooks when an object changes, with approvals and logs built in. Query the data over REST or GraphQL, and let the GraphiQL editor autocomplete a device and interface query you can save inside Nautobot. When an object is created, updated, or deleted, webhooks notify outside systems, with Jinja2-templated bodies and HMAC SHA-512 signatures. Git repositories can carry export templates, Jobs, and config contexts too, so YAML data and Jinja2 templates get pull request review before Nautobot syncs them. Open-source Apps add Golden Configuration for config backup, compliance, and remediation, Device Lifecycle for hardware tracking, SSoT for syncing other systems, and ChatOps. Object permissions and change logging keep a shared instance auditable. 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.

Deploy
Flowctl screenshot thumbnail

Flowctl

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.

Deploy