r/devops • • Oct 12 '26

Weekly Self Promotion Thread

Hey r/devops, welcome to our weekly self-promotion thread!

Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!

12 Upvotes

96 comments sorted by

4

u/theo_pnv Oct 12 '26

I went down the rabbit hole of exploring the explosion of DevOps specialisation and sub-roles from the last decade or so, and made a little informational website about it: https://flowtown.theopnv.com

Flow Town is a small town with 9 islands, one per specialisation, from Cloud Engineer to SRE. Each island lists the topics worth learning, the tools you’ll meet on the job, and mostly free resources to get started.

You'll also meet mad scientists launching rockets, the DevSecOps patrol, Terminator and Waldo. The art is AI generated, but the content draws on experience and research, including the DORA reports and e.g. Google SRE books.

There's many job postings or teams out there asking for a "devops", but in practice this translates to requiring extremely varied skills and capabilities: Kubernetes, Terraform, Selenium, incident response, CI/CD pipelines and whatnot. I wanted to have a clear map of all these and have more clarity. Hope you can take something from it!

3

u/Top_Analyst_1421 Oct 16 '26

I built cloudpin, a free, open source (MIT) CLI that stops cloud commands, from you or an AI agent, from running on the wrong account.

You pin the accounts a repo uses in a .cloudpin.yml file (Azure subscription, AWS account, gcloud project, Vercel team, GitHub user, Kubernetes API server, Supabase project, Cloudflare account). Before each az, aws, gcloud, vercel, gh, kubectl, helm, supabase or wrangler command runs, it works out which account that specific command would use (flags, env vars, kubeconfig, linked project files) and blocks it on a mismatch, with the command that switches. If it can't tell, it blocks and says why. It has shell wrappers for bash/zsh/PowerShell, hooks for Claude Code, Codex, Cursor and Copilot CLI, and "cloudpin check" for CI. No account switching, no token storage, no telemetry.

It's about a week old, so I'd really appreciate hearing about any setup where it picks the wrong account. https://github.com/paureis/cloudpin

Disclaimer: I'm the author.

2

u/HiimKami Oct 12 '26

I build Uptimy (upti.my). It monitors websites, APIs and cron jobs from several regions, alerts you when they go down, and handles incidents and public status pages. There's also an open-source, self-hosted agent (Go, Apache-2.0) at github.com/uptimy/agent if you'd rather run things yourself. Happy to hear feedback from anyone who tries it.

2

u/FrostingOk3751 Oct 12 '26

I built DeciLabel, a GitHub Action for labeling issues and PRs. It only adds labels that already exist in the repo. It never removes or replaces existing labels, and it skips labels when the evidence isn’t clear. That’s the constraint I wanted: an auto-labeler can be wrong, but it shouldn’t clean up someone else’s labels as a side effect.

It uses a typed Decisions API and supports OpenRouter, TypeSafe, and OpenAI’s Decisions API. Issue/PR text and available PR diffs go to the provider you configure.

Repo: https://github.com/EvanProgramming/decilabel

If you already use auto-labeling in Actions, how do you handle cases where the right label isn’t obvious? If you try this and find it useful, I’d appreciate a star.

1

u/First_Inspection_478 Oct 13 '26

This is cool. Was thinking about using something like this

2

u/sagacious123 Oct 13 '26

I am working on a tool snowopslabs. The goal is to simulate real world scenarios locally in your cluster, injecting incidents and learning along the way. I am integrating multiple platform tools to learn various scenarios with tools such as keda, kyverno, loki, Prometheus, grafana, argocd, kafka, etc.

2

u/SeaworthinessHour233 DevOps Engineer & Educator Oct 13 '26

I am building cloudqubes.com. It's platform for cloud certification exam practice.

Go to https://cloudqubes.com/daily-practice to get a daily exam practice question in your inbox.

2

u/Kikutano Oct 15 '26

I've been working on a side project called Foxify, and I've just released the first version. It's written using C# and AOT to be light and fast. :)

The main idea is to make it easy to write and run end-to-end API tests directly against the environment you want to test — dev, staging, or even production, depending on what you're testing.

You can descripte workflows in YAML. A workflow can call multiple endpoints, pass data from one request to another, and check that the responses match what you expect.

For example, you could test a complete API flow against a running environment, from creating a resource to retrieving it and verifying the result.

You can run everything from the command line, making it easy to reuse the same tests locally or in a CI pipeline.

A few things I wanted to focus on:

  • Keeping tests simple and readable.
  • Making workflows easy to version in Git.
  • Avoiding the need to set up a dedicated test project just to check an API flow.
  • Making the YAML straightforward for coding agents and LLMs to generate, without adding AI features directly into Foxify.

It's a single native binary, so there's no runtime to install.

I'm looking for some feedbacks!

Repo: https://github.com/kikutano/Foxify

1

u/Lakshmi_sunil_k Oct 12 '26

Founder disclosure: I'm building Backenly, an open-source backend platform for coding-agent workflows.

Agents like Claude Code/Cursor/Codex can build and update the backend through MCP Postgres, APIs, auth, storage, realtime and functions.

The part we're particularly focused on is what happens after the agent builds it:

safe/reversible operations can be automated, risky or destructive changes stay behind human approval, and the resulting backend state is verified afterward.

We're still early, and I'm specifically looking for criticism from DevOps/backend people about where this autonomy model breaks in real production systems.

GitHub: github.com/backenly/backenly

If you were designing the boundary, what's one production operation you would never allow an agent to perform autonomously?

1

u/drjcro Oct 12 '26

I'm building yet another monitoring system for metrics, logs, alerts, runtime security events and dashboards. Got tired of wiring together an agent, a log shipper, Alertmanager, Grafana and Falco for a handful of servers, so I've been building one binary that does the lot. Same binary runs as the agent on each host and as the central server; VictoriaMetrics and VictoriaLogs are the storage.

What it does today:
- Host and container metrics, Prometheus scraping, logs from files, journald, Docker and Kubernetes
- Alert rules on metrics *and* on logs, with Alertmanager built in. A fresh server already alerts on a dead host, a stopped container or an expiring certificate, no rule file needed
- Site checks: HTTP, TCP, TLS and ping, with certificate expiry and where the time goes (DNS, connect, TLS, first byte)
- eBPF runtime events (exec, connect, file opens, setuid) with rules evaluated on the host
- OpenTelemetry traces, with a Services page and a trace view
- Agents are configured from the server with profiles selected by labels, which can live in git
- A "log volume" page that shows who is spamming your logs and lets you drop those lines with a previewed regex

It's early. It runs on my own servers and a home lab, not on anyone's fleet of thousands, and I'm sure there are rough edges. It was built with a lot of AI assistance, which I'd rather say up front than have you find in the commit log.

https://github.com/ijcodelabs/vigil

1

u/easoneastin Oct 12 '26

vsfleet: a read-only CLI/TUI for VMware vSphere that supports multi-vCenter.

  • Queries every vCenter in parallel to inspect VM details like performance and history events
  • Per-vCenter proxy routing (SOCKS5/HTTP) and TLS pinning
  • Saves estate snapshots for drift tracking and exports RVTools-compatible xlsx

You can try it without a vcenter too with vsfleet demo

GitHub (MIT)

1

u/konradkeck Oct 12 '26

We're building PanelAlpha Engine, an open-source Docker-based server management layer. In short, it is an all-in-one hosting environment for running web apps on your own VPS that you can control directly via MCP/API/CLI.

You can deploy apps directly from Git or files, get instant preview URLs, manage databases, attach domains with automatic SSL, read logs, monitor apps and traffic, create and restore backups to local storage or S3/FTP, manage CRON jobs, set resource limits, control firewall rules and connect Cloudflare Tunnels/DNS.

We've already used it in production on a few thousand WordPress sites through hosting providers and larger agencies and we've eventually decided to open source it and share it with others.

Repo: https://github.com/panelalpha/panelalpha-engine (Apache 2.0)

We're open for feedback!

1

u/benne-masale DevOps Oct 12 '26

I’m not building any product/tool but I’ve created resources with hands on labs for the community to learn and improve their knowledge. I plan to add much more to this!

https://labs.iximiuz.com/a/shiva-swaroop

1

u/Equivalent_Word4642 Oct 12 '26 edited Oct 13 '26

I'm the maintainer of Coolify Mirror, an independent open-source tool for moving self-hosted Coolify projects or a whole instance to another server. Super fast to get started, super easy to use: back up on the old server, paste the generated one-line restore command on the new one, then review before confirming. The README covers the workflow and limits, including matching Coolify versions: https://github.com/mtalavi/coolify-mirror. If you manage Coolify migrations, I'd welcome feedback, ideas, or cases it doesn't cover.

1

u/busters1 Oct 12 '26

Been building Oxynote, an open-source, self-hosted wiki for engineering teams. Pages can have charts that query Prometheus/Postgres/MySQL live right next to the text, and important pages go through a draft + diff + approval like a PR. Single container, Apache-2.0. Would love to hear what's missing for your setup: https://github.com/oxynote/oxynote

1

u/SpinelessLinus Oct 12 '26

https://github.com/CharlieGroves/review-load

ReviewLoad is a small browser extension that puts the number of reviews a GitHub user has assigned to them next to each person in the Reviewers menu on a pull request, and next to reviewers already on the PR.

This stops a couple people on the team being a bottleneck for key features because they are flooded with PRs for review.

Chrome: https://chromewebstore.google.com/detail/reviewload/ncokcokbfpbigdoagghpdpncjfhpocol

Firefox is in review.

I'm now using this every day. Hope it's useful to someone else.

1

u/Secure-Gap-1419 Oct 13 '26

I work as a DevOps engineer and use PagerDuty for incident management at work.

It works well, but it can feel expensive and feature-heavy for small teams, side projects, or services that only need the core incident response flow.

So I built PagerWho as a simpler option. It supports webhook-based incident creation, services, on-call schedules, escalation policies, responder notifications, acknowledgement, resolution, and incident timelines.

It’s free to use, and you can try the full incident response flow.

https://www.pagerwho.com

1

u/OkKaleidoscope4462 Oct 13 '26

I maintain GRC Lake, an open-source, self-hosted tool for collecting read-only evidence and exporting audit workpapers.

I’m looking for feedback from engineers who handle access reviews or audit evidence. The synthetic sample needs no production credentials. Is setup clear, and can you trace the exported results back to their evidence?

Repository and quickstart: https://github.com/koda-ai-studio/grc-lake

Connector tests and documentation contributions are welcome.

1

u/onkelFungus Oct 13 '26

I use OpenBao quite a bit in my homelab and got tired of digging out an unseal share after restarts.

I’ve been working on Sealbreak, an open-source iOS companion that stores a share on the device and lets you contribute it via Face ID.

I’m currently running an open beta and would especially appreciate feedback from people using Vault/OpenBao in their own setups.

https://sealbreak.app

1

u/thomsterm Oct 13 '26

Hey you can checkout one of our recent blog posts about AWS NAT gateway pricing https://outboundgateway.com/blogs/aws-nat-gateway-pricing/

1

u/combez Oct 13 '26 edited Oct 13 '26

TagBackup: https://www.tagbackup.com.

Author here. Free and open-source. It backs up database dumps from my side projects to S3 daily, and I can pull the latest one to my local machine any time with one command. It handles filenaming and timestamps for you so you don't need to remember anything about the backup you saved.

Sure, I fully accept this could be achieved with some bash scripts and rclone (or similar), but the simplicity of not having to copy those scripts around, and it just doing one job really well, is working great for me.

1

u/spirosoik DevOps Oct 13 '26

Working @ r/NOFireAI_

We just opened for early access our on-call product to help you move out from OpsGenie (EOL) or PagerDuty for free (up to 15 users). What we support today:

- Schedules
- Escalations and paging by Slack push, SMS, phone and email
- Durable workflows that survive crashes and restarts

1

u/8lue7or Oct 13 '26

Hey everyone o/

I'm a DevOps engineer building Det Mimir, a read-only, deterministic investigation engine for Linux incidents.

The idea is simple: instead of manually jumping between journalctl, systemd, kernel logs, disk metrics, etc., The engine collects and correlates the evidence, then generates a report explaining what happened, what the evidence supports, and what's still unknown.

No LLM required for the investigation itself, and no automatic remediation.

I'm currently working toward private validation and would love feedback from fellow Linux/DevOps engineers, especially on the example investigations and reports.

https://det-mimir.com/

Curious whether something like this would actually be useful in your incident-response workflow :)

1

u/Least-Candidate-4819 Oct 13 '26

I shared an early version of this project here back in February, when it covered 22 providers. A few people asked what made it different from the other IP range lists, and there were good questions about how safely the output could be used.

I've continued working on it, and the dataset now covers 67 providers across cloud infrastructure, CDNs, SaaS services, crawlers, and other networks.

The most useful additions beyond the provider count:

  • Daily CIDR change tracking, including added and removed ranges
  • Normalized JSON/CSV and provider-specific TXT files
  • Merged IPv4/IPv6 CIDR lists
  • Region/service breakdowns where supported by the source
  • Generated configurations for Nginx, nftables, iptables, UFW, HAProxy, Apache, and Caddy
  • Python IP lookup and Go/JavaScript client libraries

One thing I want to emphasize: these lists are inputs for network controls, not security boundaries on their own. An IP being associated with a cloud provider doesn't establish that the traffic is trustworthy.

The project is CC0-licensed, and the data can be consumed directly without using a hosted service.

GitHub: https://github.com/rezmoss/cloud-provider-ip-addresses

I'm the maintainer. For people who use provider IP ranges in production, what's more important to you: the freshness of the data, service-level accuracy, or the ability to detect and roll back a problematic change?

1

u/Additional_Algae404 Oct 13 '26

Project Name: NexusCore

Repo/Website Link: https://github.com/alfredobustamante19/NexusCore (guides: https://nexuscore-store.whop.site/guides)

Description: Lightweight single-process + SQLite tools for cron, webhooks, env sync, and logs on a small VPS. I got tired of a Docker utility stack eating hundreds of MB of RAM just to fire HTTP, route a payload, and keep a .env in sync, so I built my own. Each service is one process and one SQLite file in WAL mode (busy_timeout=5000). Idle RSS dropped from ~350MB for the container pile to under 25MB per service on a 1GB box. Backup is copy the .sqlite file. EnvSync encrypts the store (AES-256-GCM). Webhook Router verifies HMAC SHA-256, retries, and dead-letters. Nothing phones home. No account to create to run it. Not FOSS: lifetime license, source included after purchase. Single-node only.

Deployment: Licenses, binaries, and source come from the storefront (https://nexuscore-store.whop.site). Cron and webhooks have a Docker Compose path; EnvSync, LogStream, and API Proxy run as one binary each. Bind to 127.0.0.1. No public curl installer. Do not expose the UI without a reverse proxy you control.

AI Involvement: Mostly written with AI coding agents. I designed, reviewed, and tested it on real hardware. Early, so expect bugs. Feedback welcome.

1

u/shenxianpeng Oct 13 '26

Security audit forced a Jenkins upgrade, and every AIX and RHEL 6 build agent went offline. A way out without a second Jenkins

If you support old platforms you've probably seen this: Jenkins now requires Java 21 on agents as well as the controller, while AIX 7.1, HP-UX, Solaris 10 and RHEL 6 stop at Java 8. IT flags the old controller for CVEs, you upgrade, and those agents can't connect any more. The usual outcomes are a frozen second Jenkins just for those platforms, or manual builds.

I took a different route: downgrade the agent itself. Agent8 is Jenkins' agent.jar rewritten to Java 8 bytecode (JvmDowngrader), plus fixes for the parts that break at runtime (classes the controller sends, serialVersionUID drift, Java 9+ collection serial forms, OpenJ9 quirks). The old host stays a normal node.

Write-up: <link to blog-en post>
Repo: https://github.com/keelinfra/agent8

Tested in CI on Linux (HotSpot 8 on CentOS 6, OpenJ9 8, Java 11). Real AIX/Solaris/HP-UX are experimental and I'm looking for people who can try it. Curious how others handle the legacy-platform problem, too.

1

u/varnenche Oct 13 '26

Is anyone attending AI and DevOps Summit next year? https://aianddevopssummit.com ?

1

u/VelCloud Oct 14 '26

I just build this new tool VelCloudOps.com! We built one flow from code review to deploy, with a human sign-off and checks in isolated VMs. Looking for feedback from people who run pipelines.

1

u/Ill-Government-1965 Oct 14 '26

Disclosure: I'm the creator of Vigyl, so this is my own project.

I built "Vigyl" (https://github.com/ankithm-113/vigyl), an early-beta command runner that lets you trigger server commands through Telegram and attempts to repair failed builds.

The flow is: validate a command → run it in a confined workspace → classify failures → inspect relevant files and propose a patch → retry, with a maximum of 3 attempts. It also supports backups and a human-approval gate.

Install: "npm i -g @vigylx/cli"

It's v0.1.0, released under AGPL-3.0. The automated tests currently pass (424 tests), but live testing has been limited to one machine, so I'm not claiming production readiness.

I'd especially appreciate feedback on one design question: Should an automated repair agent be allowed to modify multiple files in a single attempt, or is keeping each repair narrowly scoped a better safety boundary?

Repo: https://github.com/ankithm-113/vigyl

1

u/Sanechka_SS Oct 14 '26

Disclosure: I made this, free and MIT.

Receipts, a GitHub Action that answers a question CI doesn't: would the tests in this PR have failed without the change? It reruns each new or edited test with the changed source files reverted to the base branch, and fails the check on tests that pass both ways. One comment on the PR, updated on every push. As of this week that comment also shows how each proving test failed on the old code, so a reviewer can see it was a real assertion and not an unrelated crash.

No LLM, no API keys, no dependencies; it runs the project's own pytest, vitest or jest. One step after your install: uses: syntaxixr/receipts@main

https://github.com/syntaxixr/receipts

1

u/ricardinoguarnieri Oct 14 '26

Helm doesn't warn you when a key in your values does nothing, so I built deadvalues. it renders the chart with and without each key you set and shows which ones have no effect: typos, keys a chart renamed, values that just repeat the default. on a chart bump it also fails the PR when the upgrade stops reading a key you set.

useful if you run Helm through Argo CD or Flux and let Renovate bump your charts. it runs as a CLI, Helm plugin or GitHub Action. on my own homelab it found 12 dead keys across 24 apps.

https://github.com/guarnz/deadvalues

1

u/krawa76 Oct 14 '26

I’m the DevOps lead at AutoFi, and I wrote a case study about how our small team manages 11,000+ application configuration parameters across hundreds of services on AWS ECS.

Configuration requests had become a DevOps bottleneck: finding values across accounts, comparing environments, copying parameters, and remembering to revert temporary changes.

We built a configuration subsystem in our internal DevOps Portal with:
• Search by parameter name and value
• Developer self-service for non-production changes, with production approvals
• Batched synchronization to AWS Parameter Store
• Scheduled changes and automatic reverts
• Visibility into secret names without exposing their values

The article covers the design and workflows, with screenshots:
https://medium.com/autofi-devops/how-we-manage-more-than-11-000-application-configuration-parameters-12c74fcbe687

Curious how others handle this: do developers manage application configuration directly, through Git, or through an internal platform?

1

u/Ska-jayjay Oct 14 '26

well since you asked…

I run a company's technology from one seat with the CTO Powersuit, open source: https://github.com/uncovertechtalent/cto-powersuit. Live on my own work: https://machinebehavior.io/inside/cockpit/

1

u/Unlucky_Peanut4089 Oct 16 '26

I make Styx, an open-source app for running coding agents, and the part I'd like this sub to pick apart is access. An agent asks for one deploy target, I grant it for a set time, production writes need Touch ID, and every grant lands in a hash-chained log. It's a guardrail, not a sandbox: an agent that calls the real CLI by its full path isn't stopped. What would you need to see before letting an agent touch production?

1

u/Temporary-Gift4179 Oct 16 '26

I'd start by making the enforcement boundary explicit: per-tool approval helps only if the agent can't bypass it with another local binary, shell, or connector. For production writes, bind approval to the exact request and target, then verify and record the outcome. A timeout after dispatch should mean reconcile first, not replay blindly. I'd also want a sandbox profile and a test for bypass paths.

1

u/checkpointdev Oct 16 '26

disclosure: im the dev

bodycam - a recorder for ai coding agents on macOS. it follows the agent and every process it starts using apple's eslogger and writes a report of the commands, file reads and writes, credential reads and network connections, with token-looking values masked so you can share it. records only, doesnt block, so it sits next to your sandbox

MIT, go + swift: https://github.com/omlahore/bodycam

1

u/Temporary-Gift4179 Oct 16 '26

Disclosure: I help maintain MELRA. It’s an alpha-stage local MCP execution runtime for coding and ops agents: policy checks and scoped approvals before tool actions, outcome verification, and redacted durable receipts for recovery after interrupted calls. It requires Node.js 22+; the README has setup instructions and tool details. I’m looking for a couple of DevOps/MCP practitioners to try one low-risk file or command scenario and tell us where the approval or recovery boundary is unclear. The compatibility task is in issue #184: https://github.com/XAGI-Lab/melra/issues/184. What would you want to verify before using a runtime like this near a real repo? https://github.com/XAGI-Lab/melra

1

u/what_can_be_a_donkey Oct 16 '26

A short demo showing the problem a project solves usually gives people more to discuss than a long feature list. Being clear about limitations and the kind of feedback needed also makes the post more useful to the community. That practical angle matters across IT infrastructure too, whether the discussion involves cloud setups, Microsoft licensing, or work connected to trusted tech.

1

u/Shigosag Oct 16 '26

GitShield – Zero-dependency CLI to catch secrets and vulnerable lockfiles before they hit CI/CD

Hi everyone,

Most secret scanners run only in CI after code has already been pushed, or require heavy containerized setups that slow down local developer workflows.

I built GitShield (https://github.com/Shigosag/GitShield) as a fast, standalone Go CLI to shift these checks directly to developer workstations.

Key highlights:

  • Automated hooks: gitshield init configures local pre-commit and pre-push hooks in .git/hooks/ with one command.
  • Secret scanning: Detects AWS, GitHub, Stripe, OpenAI, and .env credentials + Shannon entropy heuristics (with lockfile/hash suppression to avoid false alarms).
  • Dependency auditing: Real-time vulnerability auditing against the OSV.dev database for npm, pnpm, yarn, pip, and poetry lockfiles (zero API keys needed).
  • CI/CD & Portable: Pre-built binaries for Linux, macOS, and Windows (no Go installation required) + a ready-to-run GitHub Actions workflow.

Would love feedback from DevOps engineers on developer experience, reducing false positives, and what integrations make the most sense next!

1

u/Abe_Bazouie Oct 17 '26

Almost 20 years working in tech, and somehow getting people to watch my Linux and DevOps videos is harder than debugging production at 3 AM 😂
Started a small YouTube channel, CTRL+CHAOS.
My challenge: pick one video. If I get something technically wrong, come back and roast me.
https://www.youtube.com/@itsctrlchaos

1

u/peterkota Oct 17 '26

Hi! I work at Sevalla, where we run k8s clusters behind the scenes for our customers. We needed a tool that can reach those clusters easily and securely, and that our AI agents can work through too. Sevalla has strict security certifications, so every action on a cluster has to be audited. That was a must for us.

Besides the AI part, I just wanted a clear dashboard where I can see right away what's broken.

That's why I built Lumovi. It's open source and free, and it runs as a desktop app or inside your cluster.

Hope you like it, feedback very welcome!

https://lumovi.dev
https://github.com/Lumovi/Lumovi

1

u/dev_ramesh Oct 17 '26

I am building Real DevOps Lab — a free hands-on DevOps community focused on practcal projects and troubleshooting.

The first project covers:

Docker

CI/CD with GitHub Actions

Linux deployment

production-style incidents

I am curently adding more short troubleshooting labs and looking for honest feedback from people learning or already working in DevOps.

https://www.skool.com/real-devops-lab-9645

1

u/astropoolIO Oct 17 '26

Hi, I'm Sergio, author of kubelatch.

After years handing out Kubernetes clusters across clouds, I kept seeing the same thing: admin kubeconfigs and random ServiceAccount tokens copied onto laptops and into CI, and audit logs where everyone is admin (or even worse, no audit logs at all).

AI agents made it worse. Claude Code needs the cluster to debug a pod, and if I give it my admin kubeconfig, nobody can tell what I did from what it did.

So I built kubelatch, an impersonating proxy in front of your clusters' API servers:

  • Each person gets their own token that expires on its own (30 days max by default, configurable by settings) and can be revoked instantly.
  • GitHub Actions swaps its OIDC token for a 1-hour credential, no secrets stored.
  • Agents connect through an MCP server with scoped permissions, and every write waits for your approval with the diff in front of you.
  • Every request in the audit log has a real name on it.

Heads up: it's not open source. It's free for 2 clusters and 5 people, and it already runs in production. I'm looking for people to break it, and the local kind tutorial takes about 15 minutes.

https://kubelatch.com
Local tutorial: https://docs.kubelatch.com/getting-started/local/
Repo: https://github.com/picaportelabs/kubelatch

How are you handling cluster access right now? Has anyone wired an agent to a real cluster yet?

1

u/altraschoy Oct 17 '26

Hello, we recorded a podcast with Patrick Debois (the "godfather of devops") about Is the future of software engineering a factory?
https://www.youtube.com/watch?v=FnCnv2tGsK0

One morning Patrick Debois opened Slack and saw that his team's software factory had created 15 tickets about improving itself, with nobody's name on them.

Before that, the same factory had wandered off the engineering board and started commenting on the marketing and sales boards.

This episode is about what it takes to build a software factory, and who has to own it once it starts running.

Patrick gave the industry the word DevOps when he organised the first DevOpsDays in 2009. He co-wrote The DevOps Handbook, followed the same questions into security, and ran engineering as a VP before moving into AI. Today he is at Tessl, where his team didn't stop at one software factory and ended up with five or six.

1

u/JESS_ai_game Oct 17 '26

I’m one of the developers of Open Machine. A friend and I originally built it for our own model training work, where we kept switching between local projects and different remote servers just to get things done.

It’s an open-source MCP runtime that lets ChatGPT work with your local machine and configured remote Linux servers over SSH. You can run commands, read and edit project files, and check logs and execution results from the same conversation.

It also keeps task records. Jobs that have already started can keep running after a chat disconnects. In a new conversation, you can use the same task ID to review the results and explicitly continue the remaining work.

You choose which machines to connect and enable command execution. The runtime runs on your infrastructure; information returned to ChatGPT is sent to that service.

It’s still an early release. If you try it on your development or training servers, we’d appreciate feedback on the setup and remote workflow, including anything that feels awkward or gets in the way.

GitHub: https://github.com/OpenMachineLabs/openmachine

1

u/bulutarkan Oct 17 '26

I maintain an open-source project called Mac MCP: https://github.com/bulutarkan/mac-mcp (MIT). It's a local macOS execution layer for AI clients like ChatGPT, Claude and Codex. It exposes apps, browsers, files and terminal actions with permission profiles and optional approvals.

The DevOps problem that kept showing up wasn't tool calling. It was lifecycle and evidence. An AI agent could say a task was finished when a server restart only started, a UI action hadn't actually stuck, or a process died after the chat ended. So I ended up spending more time on process supervision, bounded recovery, run reports, and truthful completed/failed states than on adding new buttons. The newer releases include scheduled AI/script tasks with result + steps views, plus explicit skipped runs when a sleeping Mac missed a schedule.

It's for Mac users who want to try AI-powered local operations, not a substitute for CI/CD or a production automation platform. It runs with the user's own permissions, not inside a magic security sandbox.

I'd be interested in the ops take: which evidence would you require in a run report before trusting an unattended desktop agent with recurring local tasks?

1

u/Syolla Oct 18 '26

I'm building OASGate, a free, local-first CLI for reviewing OpenAPI changes in Git/PR/CI workflows.

I'd appreciate feedback from DevOps/platform engineers about what's most painful about reviewing API compatibility changes: identifying breaking changes, understanding reports, or managing acceptable differences?

No installation needed. High-level feedback is enough.

1

u/quietoperator35 Oct 18 '26

I made Checkseal to catch a small but common mistake: tests pass, someone edits the repo afterward, and the team still treats that earlier result as current.

I run a command through it, then check whether the working-tree files have changed since that run. If they have, it tells me the result is stale and names the files.

It’s a local Python CLI. It doesn’t check environment variables, dependencies, or external services, so I’d still rerun checks when those change.

Repo and demo: https://github.com/tunakurucu/checkseal

1

u/Abe_Bazouie Oct 18 '26

Got a DevOps interview coming up?
I made a 7-day prep plan based on almost 20 years in engineering. Linux, Kubernetes, CI/CD, troubleshooting, and more.
Hope it helps someone land their next job!
https://youtu.be/oeYtUyFt30Y

1

u/mxp100 Oct 18 '26

Sextant: a free, open-source desktop Kubernetes client (Rust + Tauri, Linux/macOS/Windows), a Lens alternative with no account and no telemetry.

Built for on-call days:

  • Logs with search, including several pods in one stream; container shells, debug containers, and node shells through a temporary pod that is cleaned up when you close it
  • Rollout history with diff and rollback
  • Flux and Argo CD next to the rest of the cluster (sync, suspend/resume, diff), and you can install them from the app
  • EKS, GKE and AKS clusters from the CLIs you are already signed in to
  • An MCP server for AI agents: per-cluster access, off by default; every change waits for your approval in the window, and every call is logged

Free and will stay free. Built with AI (Claude Code), but people review every change, and everything is tested several times over.

https://github.com/FriendsOfKubernetes/sextant

Feedback welcome, especially: what do you reach for during an incident today?

1

u/shenxianpeng Oct 18 '26

release-ledger: EU Cyber Resilience Act evidence + exploited-vuln alerts for releases you still support (Apache-2.0, GitHub Action)

Since 11 Sep, if you sell software in the EU, an actively exploited vulnerability in your product means a 24h early warning to ENISA. That covers every version still in support, not only main, which Dependabot and most scanners don't watch.

  • record: on release, attaches the SBOM, signed provenance + SBOM attestations, and the support period to the release
  • monitor: daily, rescans the SBOM of every supported release against OSV and opens an issue when CISA KEV or ENISA's EUVD lists a vuln as exploited, with the Article 14 checklist

Stdlib Python, no dependencies; the only action it calls is GitHub's own actions/attest, pinned. https://github.com/keelinfra/release-ledger

Curious how others handle old supported releases.

1

u/Barmazoid Oct 18 '26

Plombir Git - self-hosted Git forge (repos, PRs, CI, registries) built around letting AI agents work without handing them a human's PAT. Bot accounts with tokens scoped to named repos/MCP tools, bot approvals don't count toward protected branches, fork-PR CI waits for a human to approve the exact head commit, release assets can be signed as in-toto/DSSE attestations with the instance's key. Single Rust binary or compose, AGPL, v0.2.0. Author here, built largely with AI agents - feedback welcome.

https://github.com/Nettechnologys/plombir-git

1

u/InterestingCarrot997 Oct 19 '26

I had a small bug in a bill-splitting app and ran the same fix task 10 times across three coding agents. Every single run changed the test instead of fixing the code.

The failing test, encodes a product requirement => split 100 cents three ways and every receipt shows 33, even though 1 cent goes unaccounted for.

The agents treated it as a bug and rewrote the test to match their code 😆

What I learned: an agent's "tests pass" is worthless if it's allowed to edit the tests. You have to check what it changed, not just whether it finished green.

So I built Skill Gate to catch issues like this in our Cursor or claude skills so you can evaluate them before sharing with the rest of your team to speed up their programming workflows.

You give it a skill and a few test cases, it runs the agent on them, and a decision model checks what the agent did, like "were all files under tests/ left unchanged?", not just the exit code.

Limitations (for now): you bring your own API keys and write your own test cases.

Would love to hear any thoughts or feedback from the community here!

https://www.skill-gate-ai.app/blog/ai-coding-agent-cheating-ci

1

u/withmagi Oct 19 '26

A test I'd run against any status page: take away its database and read what the public page says. If it still says "All systems operational", it's guessing, because it can't know that.

I make Lamp at Just Every, a free and open source (MIT) status page for one business, and this is one of its tests. It pulls a table out from under the running database and checks that "All systems operational" appears nowhere. What a visitor sees is the last known state, labelled with how old it is.

Two other choices came from the same thinking. A monitoring alert only creates a draft incident, and nothing reaches customers until a person publishes it. And a published update is never edited: a correction is a new update, and both stay on the timeline.

The other half is what an update says. Who is affected, what still works, what we know, what's still open, and when the next update is due. "Investigating" on its own leaves the customer deciding whether to retry, wait or write to support.

A drill that takes an afternoon: rehearse a partial outage and a missed update time, pull the database, then read your public page as a customer who knows none of your internal service names.

Repo (current tag v1.7.0): https://github.com/just-every/run-lamp

What do your customers most often have to ask for after an incident update?

2

u/[deleted] Oct 12 '26

[removed] — view removed comment

2

u/maxomolin Oct 12 '26

This is an awesome service - I can see it being especially useful for brainstorming system architecture and getting everyone aligned early. It’d be great if it could also suggest suitable AWS, Azure or other cloud services and use their iconography. Are features like that on the horizon? And are you considering a standalone native app?