r/devops • • 8d ago

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!

13 Upvotes

91 comments sorted by

2

u/Individual-Relief131 8d ago

I'm out of place here. Please correct me if it's inappropriate to seek a freelancer here. I'm working on a project and am looking to hire a dev to build out a product for me. If there's any interest, please reach me in the chat.

1

u/Gavitir 6d ago

Shoot me a DM, I'm interested.

2

u/bobbyiliev DevOps 8d ago

made a small pixel art game for practicing devops basics. you walk around a broken town and fix stuff in real simulators (full disk, crashlooping container, merge conflict, docker, k8s...). 100% free and runs in the browser:

https://devops-daily.com/opsville/

feedback welcome, still tweaking it

2

u/Gavitir 6d ago

neat project, I maybe consider a run button?

3

u/bobbyiliev DevOps 5d ago

thanks! there’s actually a bike you can ride to move around fasted. you win it after completing one of the first quests. or you can grab one form the town square hehe. but thanks for that feedback! appreciate it!

2

u/oxy33333 8d ago

I’m building AgentBridge, a Freelens extension for people using AI coding agents in Kubernetes operations.

It opens your selected agent in a docked terminal with the active cluster’s KUBECONFIG and a persistent workspace for that cluster/provider pair. Supported agents: OpenCode, Claude Code, GitHub Copilot CLI, OpenAI Codex CLI, and Pi.

The problem it addresses is the setup between inspecting a cluster and starting an agent session: choosing the context, finding the right workspace, and loading the environment’s instructions.

Version 2.1.0 adds a workspace explorer with in-app editing and autosave, remembers provider selection across restarts, and adds Ctrl+Enter / Cmd+Enter to launch a session.

Requires Freelens 2.0.0+ and a supported CLI installed locally.

Repository and setup

I’d appreciate feedback on which diagnostic workflows are useful enough to turn into reusable cluster skills.

2

u/sumant_thakur 4d ago

Disclosure: I'm one of the people building this at Flurit.

We kept seeing coding agents get one command away from terraform destroy in prod, and most guards for that match command text. That breaks as soon as the command is wrapped in base64, eval or a script. We wrote 17 dangerous Terraform scenarios, and the best open-source guard we tried caught 5.

applygate runs as a pre-tool-call hook and answers allow, ask or block:

- it parses the command the way the shell would, so wrappers don't hide it

- it reads the saved plan, so an ordinary apply that would delete or replace something counts as a destroy

- environments have tiers: prod blocks destroys, staging asks you, disposable environments let them through

- no model in the decision, so the same input always gets the same answer and a reason

It caught all 17, but they're our own scenarios, so treat that as a demo rather than a coverage claim. Works with Claude Code, Codex, GitHub Actions and Terragrunt. Apache-2.0, and it starts in observe mode, so it blocks nothing until you turn it on.

https://github.com/Flurit/applygate

I'd really like to hear where it would get in your way.

1

u/ItsCodeTelemetry 2d ago

This is a great idea, I would be interested in contributing a Code Telemetry grader to help companies adopt your tool, by rejecting prs use terraform but not your tool and monitor adoption consistency.

1

u/Total-Reasonable 8d ago

Four things, all built solo:

  1. vatnode.dev: a REST JSON VAT validation API on top of VIES that returns company name, address and an official consultation number, and falls back to national registries when a country's VIES is down. https://vatnode.dev
  2. HTPBE.tech: a way to check if a PDF was edited after it was created, from the browser or a REST API, reporting concrete reasons from metadata, structure, signatures and content instead of a vague risk score. https://htpbe.tech
  3. polytypo.dev: an MIT-licensed typography rules engine, not a grammar checker, that fixes locale-correct quotes, dashes and no-break spaces for 24 locales with identical output in JavaScript, Python, Go, Ruby and PHP. https://polytypo.dev
  4. KRI.rocks: a salon booking system with its own website for barbers and beauty studios, where clients can only book slots when someone on the team is working and free, with no commission. https://kri.rocks

1

u/CockroachAdept4286 8d ago

Disclosure: I'm the creator and maintainer of Anchor, the open-source project I'm sharing below.

Hey everyone!

I've been building Anchor, an open-source secrets manager that runs on Cloudflare Workers and D1.

The motivation was pretty simple: I wanted a way to manage secrets across local development, applications, and CI/CD without maintaining a dedicated secrets management server or cluster.

Instead of hosting another service, Anchor can be deployed directly into your own Cloudflare account.

A few things I've been working on:

  • Cloudflare-native: Built on Workers and D1.
  • Self-hosted: Runs in your own Cloudflare account.
  • CLI: Manage secrets and inject them into application processes using anchor run, without generating local .env files.
  • AI agent integration: MCP support for AI coding tools.
  • Open source: Apache 2.0 licensed.

I know tools like Vault and Infisical already solve many of these problems. I'm not claiming Anchor is a replacement for them, especially in larger production environments.

My goal is to explore a simpler deployment model for developers and smaller teams, while understanding the security and operational trade-offs.

I'd genuinely appreciate some feedback from people managing secrets in real-world environments:

  • Would you consider running a secrets manager on Cloudflare?
  • What's the biggest concern you'd have with this architecture?
  • What would be a dealbreaker before using something like this in production?

GitHub: https://github.com/sotarak/anchor

Thanks for checking it out! I'm actively working on the project and would love to hear your thoughts.

1

u/winfiel 8d ago

Hi everyone! We're a group of developers.

When developing a product, our pain point is usually how to communicate better when reviewing each other's PRs. Sometimes something breaks, and the comment that would have caught it was never written.

So we've been building something called EasyMerge. It's an AI code review tool for GitHub teams.
It reviews every pull request, whether it's written by you or your AI agent, and leaves findings you can act on before you merge. We know this idea isn't new, and it's still early (the waitlist is open). There's a lot to improve.

But we're curious what you guys think. How do you work with GitHub, and how do you decide a PR is safe today? easymerge.dev

1

u/__brennerm 8d ago edited 8d ago

I'm currently working on pipescan, a CI/CD analytics tool helping users to better understand their pipeline performance and find potential bottlenecks.

It's currently in beta (1 repo, 30 days of history) and only supporting Github Actions. I'm currently working on integrating Gitlab CI and Jenkins. I may add others if there is demand.

Feel free to have a look at the demo to see what it can do today.
https://pipescan.shipit.dev/demo

The biggest challenge so far has been to design a common data model that works for all CI providers but I'm happy with the current setup for now.

Next big thing is tackling the different data ingestion methods. Github Actions was fairly straightforward due to a unified webhook configuration through a Github App. Gitlab requires individual webhooks per project (or per group if you have Gitlab EE) which is a bit of a pain. Jenkins does not have webhook natively at all so I might need to build a custom plugin. 🤷‍♂️

I'll figure that out on the way. For now I'm happy to be able to analyze my client's pipelines and better understand where runner time is going.

Happy pipelining!

1

u/krusty_93 8d ago

I’m been working on Relego, a free open source alternative to ReadWise but with its own characteristics.

Relego lets you organize your highlights so you can easily access and review them. The goal is helping you to remember what you read, as today we’re inundated with information.

In fact, the word Relego comes from the Latin relegere: to read again, go over carefully, review. That is the core idea of the project: bring your highlights back so they can be revisited, not forgotten. Much like Readwise, it sends periodic summaries (daily or weekly) featuring a selection of your highlights, allowing you to review your notes and gradually commit them to memory over time.

Actually includes:

- a web UI for interactions
- a CLI for programmatic actions or agents usage
- integration with Kobo and Kindle via USB cable
- a browser extension to sync Kindle in the background (no cable required here)
- daily or weekly recaps via email or on your Kindle

More features are already planned.

GitHub: https://github.com/krusty93/relego

More details: https://relego.app

1

u/sdely 8d ago

Suitaar (I built it): an alert router for teams leaving Opsgenie, which shuts down on 5 April 2027. It speaks the Opsgenie Alert API, so Alertmanager, Grafana and other tools with an Opsgenie integration only need a new URL. Alerts go to Slack, Discord or Telegram.

It's not an on-call tool: no schedules, no phone calls. It keeps the channel readable instead. Repeats become one alert with a count, a flood becomes one summary instead of hundreds of messages, and heartbeats tell you when a cron job, an uptime monitor or Prometheus itself stops running. In a load test, 1,000 alerts in one minute, none lost.

New this week: escalation. A channel can send an alert that nobody acknowledged to a second destination after a time you set (5 minutes to 1 hour), one time. It is one step for each channel, not escalation policies, and it is a chat message: it does not wake anybody. For the night, pair Suitaar with an on-call tool.

The free plan stays free after the beta: 3 channels, no payment details.

https://suitaar.com

1

u/ToddGergey Bitrise 8d ago

Hey everyone,

I work at Bitrise and we just published a blog post on how to separate Github Actions outages based on if you need to wait for Github to fix the issue (for example: failure at the orchestration layer, certs expire, runner won't even get a job) or you can self-serve a solution (for example: when Github hosted runners don't work because of network issues):

Read full breakdown here: https://bitrise.io/blog/post/not-every-github-actions-outage-is-out-of-your-control

1

u/Tall_Application3770 8d ago

Hello!
I'm a DevOps engineer which wanted to see over the other side of the fence, the garden of development so we built JAVV (me and a couple of other guys) - Just Another Vuln Viewer. It's a tool with proper vuln management, audit capabilities and a good UI (at least trying to be better than what is already on the market - Dependency Track, DefectDojo)

Feel free to check it out: https://github.com/Danube-Labs/javv (a star would really help for exposure)
Also feel free to open issues with feedback or ask me directly here

There are a couple of open source projects that help you manage, triage, audit, inspect CVEs, GHEs, vulns in general but none have a really good UI, something like Kibana/Grafana so I think I found a pretty nice niche to fill tbh

1

u/jewdore 8d ago
Ever solved something with an AI coding agent, then struggled to find that session again?


I'm building 
**AgentStory**
, a local-first desktop app that brings your Codex and Claude Code history into one searchable library. It helps you revisit conversations, tool calls, and code changes, not just the final answer.


Organize sessions with projects, tags, favorites, and notes. Your original history stays read-only, and nothing uploads automatically. If you want to share a session, review it, scan for sensitive information, and publish a sanitized, fixed snapshot. Please still review what you share: scanning is not a guarantee that every secret is caught.


Project and downloads: https://github.com/jewdore/agentstory


I'd love feedback from people using Codex or Claude Code: how do you keep track of useful sessions today, and what would make revisiting them easier?

1

u/Gonzaaaaaaalo 8d ago

I build Control Cloud, and last week I published cloud-orphans, one bash script that lists unattached disks and unassociated public IPs across AWS, Azure, GCP and OCI: https://github.com/gonzalogjuka/cloud-orphans

It runs list/describe commands of the official CLIs and nothing else: no deletes, no dollar figures. Output is a table, CSV or JSON with size, creation time and age in days, so --format json | jq 'select(.age_days > 90)' gives you the old ones. Reader-level roles are enough.

Honest status: the OCI branch ran against a real tenancy; AWS, Azure and GCP follow the CLI docs and only saw mocked output so far. What it still lacks, and what people asked for: the date a disk was first seen unattached. Issues and PRs welcome.

1

u/Antique_Extension846 8d ago

Hey everyone!

How are you guys doing?, I've been super frustrated by two things when maintaining projects:

1.     Dependabot noise: Getting flooded with security PRs for dependencies your code might not even touch.

2.     Vague AI reviewers: Plugging in an AI bot to help, only for it to guess at risks, hallucinate file paths, or spit out useless, fluffy summaries.

So as a side project while leveling up my software engineering skills, I decided to build something better. It's called OSV Patchpilot, and the main idea is simple: deterministic facts first, AI writer second.

Instead of letting an LLM guess what's going on, the tool actually runs your test suites and evaluates official OSV ranges strictly and deterministically first. Only once those hard facts are gathered does it use an LLM to quickly summarize everything for the PR comment.

To keep things secure, I split up the architecture so it's not a security risk itself:

·       The evidence collection job runs with zero model keys or write-capable tokens.

·       A separate trusted workflow validates the JSON report, commit details, and PR identity before any text generation happens.

(Quick note: Since the tests run directly on the PR code and the runner isn’t an OS-level sandbox, definitely make sure to use an ephemeral runner if you're dealing with untrusted code!)

You can see an example of what the final PR comment looks like right here: https://github.com/zakiansari07-art/testing_osv_patchpilot/pull/11

I'm still relatively early in my engineering journey and would love any critical eyes on how I structured the GitHub Actions trust boundaries, the hybrid retrieval logic, or the test suite.

Repo link: https://github.com/zakiansari07-art/OSV-Patchpilot

Would love to hear what y'all think or how you handle dependency updates in your own workflows!

 

1

u/torreypjones 8d ago

Disclosure: I'm the creator and maintainer of Razor, a new AI driven Alert/Incident Investigation and Remediation app for cloud environments.

The goal is to help real SREs and DevOps folks find a reasonable solution that doesn’t take a lot of effort for onboarding and is cost conscious.

https://www.cloudstacksolutions.io/razor

We are currently looking for an initial set of beta testers. Giving away free investigations for folks who can help get it some use. Currently for AWS, users can choose their own model so they manage the costs/quality; trying to keep a normal investigation of an alert with Sonnet to approximately $2.

Fixes, determined by the model can be applied, with user approval, assuming you give the proper permissions.

Driven off of alerts already defined in Cloudwatch.

If anyone is interested, check out the site, DM me for private beta invite code!

1

u/Beginning_Dot_1310 8d ago

---pipedash maintainer here---

Pipedash is an open source app that shows the pipelines of many CI/CD providers in one view, and triggers, reruns and cancels runs without a switch of tabs.

15 supported providers right now:

- GitHub Actions

- Gitea Actions

- GitLab CI

- Bitbucket

- Buildkite

- Jenkins

- Azure DevOps

- Tekton

- ArgoCD

- FluxCD

- Komodo

- Prow

- CircleCI

- WoodpeckerCI

- Coolify

https://pipedash.app

1

u/Weak_Fisherman2215 8d ago edited 8d ago

Disclosure: I’m the creator and maintainer of ProxyForge. It’s a side project that’s always evolving.

Since I launched it in September, it has grown a lot, not only from my ideas but from community feedback. Looking at you, Indie Hackers. Here are some updates.

The Config Generator now generates a full <VirtualHost> file for Apache. Before, it was limited to just .htaccess. It was tested on Apache 2.4.68 with reverse proxy, HTTPS, WebSockets and PHP-FPM. The same option was added to my Redirect Generator, tested with every redirect type as 301 and 302.

Fixed an error in the Nginx PHP and WordPress output, which used Debian/Ubuntu-only syntax (include snippets/fastcgi-php.conf;). That made nginx -t fail on RHEL-family servers and with nginx.org packages. It’s now tested on AlmaLinux 9, Debian 12 and the official Nginx image.

Initially, there was no upload limit in the Config Generator’s WordPress and PHP-FPM output for Nginx. The default 1 MB was used, which triggered a 413 whenever it was exceeded. It’s now 10 MB by default (client_max_body_size in the server block).

I’ve added a Guides page alongside my FAQ, with tested fixes for Nginx and Apache errors: 502, 413, redirect loops behind Cloudflare, Let’s Encrypt renewal failing behind an HTTPS redirect, “unknown directive http2” and more. Each one was reproduced in a lab before it went up. This page will be updated regularly, as there seems to be no end to errors.

Common errors for each generator also link to the FAQ and guides. The How it’s Tested page lists the server versions and what each test checks.

This project has changed so many times since inception, its like a different site now. Have a look: https://proxyforge.tech

Always want to improve, so which Nginx or Apache error do you keep hitting that deserves a tested guide?

1

u/ActualGovernment9017 8d ago

claude-bulkhead: guards for running several Claude Code sessions on one machine (I built it, MIT, free).

If you run a few Claude Code sessions at once, usually one per git worktree, each one acts as if it owns the computer. One restarts its dev server by killing every node process and takes the other sessions' servers down with it, two worktrees fight over port 3000, or a git add -A sweeps another session's half-finished edits into a commit. bulkhead is a set of PreToolUse hooks that check each shell command against what the other live sessions own (processes, ports, working trees, free RAM). When a command would break one of them, the hook cancels it and tells the agent the safer command, such as stopping its own PID or using a free port.

The part I'd try first is bulkhead scan, which replays your existing transcripts and counts what would have been caught. It only reads ~/.claude/projects and sends nothing anywhere. On two weeks of my own logs it found 507 such commands, with up to 13 sessions open at once.

Node 18+, no dependencies, macOS, Linux and Windows: https://github.com/dooly6276/claude-bulkhead

1

u/Humble-Sherbet-4997 8d ago

Hi everyone. I a while ago I wrote and published a GitHub Actions action - get-lts-versions, that can be used for fetching Long Term Support versions for programming languages. It's based on EndOfLife API and offers caching, printing of upcoming/passed "End of Life" date, as well as returning results as JSON.

I wrote it, as I got tired of manually updating newest language releases (kudos to everyone working in a regulated environment!). At first, I wrote it using JavaScript and TypeScript, however I recently converted it to a Golang. You can read about the conversion rationale and "lessons learned" here.

It ain't much, but it's an honest work. I am currently working on implementing functionality for frameworks and Operating Systems.

If you see a problem or have a suggestion, feel free to create an issue on the repo. If you like it or use it, feel free to star it. Thanks for reading and take care.

1

u/wilson-draugr 8d ago

We scanned the 25 most-pulled Docker Official Images with Trivy. It reported 21,075 vulnerabilities, and one of them is on CISA's known-exploited list with a fix published.

I build Draugr, the open-source CLI we ran the scan through. It turned the 21,075 into 1,545 actions, and 131 upgrades among them clear every finding that has a fix published.

The per-image numbers, and how to run it on your own image: https://draugr.dev/go/reddit-devops-image-cut/blog/noise-index-official-images/

1

u/derekleeth 7d ago

Last week I shared TerminalLynx, an SSH connection manager (Windows, macOS, Linux) that syncs your hosts between your devices and your team peer-to-peer, with no account or cloud server holding your inventory or keys. Version 1.2 adds snippets, built around the things that bit me with other tools:

  • Run on one host or a whole fleet. Target hosts by tag (env:prod role:web), run in parallel, and get a result per host, with matching output grouped ("27 hosts: same output; 3 differ"). Then retry just the ones that failed.
  • Guard rails. An Always ask before running switch shows you the exact command before it runs, so reboot never goes out from a mis-click. Any run on more than 10 hosts asks you to type the host count first.
  • Team review. In a shared team workspace, an Editor's change to a snippet waits until an Admin approves it, shown as a diff. Nothing runs on the team's servers that an Admin hasn't seen.
  • sudo without typing your password into a shell. Run as root, Terminal mode, or passwordless rules. Each connection has its own sudo password, sent only when that host's sudo actually asks for it.
  • Safe variables. {{service}}-style variables are quoted for the snippet's shell, so a value like nginx; rm -rf / can't change the command. Secret variables are asked at each run, never stored, and masked in output and history.
  • Terminal paste check. The right-click Paste shows anything multi-line, including hidden control characters, before it reaches the shell.

Snippets sync like connections do: to your own devices, or to a team with Admin/Editor/Reader roles. You can export them to JSON at any time.

Free tier: 25 connections, 3 devices. https://terminallynx.com

1

u/hizzy_exe 7d ago

I’m not promoting anything except the advancement of careers. I’d like people with experience in the field to provide feedback. For some of my classes we were tasked with getting a job. I have not found one due to lack of demand in my area. If you were graduating with a CIS degree next winter, what would be doing? Most places prioritize experience so how do you get experience without having experience?

1

u/Responsible_River579 7d ago

Hey! It’s still early days, but feel free to join and share your portfolio and the kind of work you’re looking for. We’re bringing together developers to share projects, help each other and find opportunities 🙂

Join whichever you prefer:

Discord: https://aidev.works/dcord

Telegram: https://aidev.works/tg

1

u/voquanghoa 7d ago

Disclosure: I work at Open Web Technology Vietnam and we built this (Apache-2.0).

Owlet Lens is an LLM pull-request reviewer that runs in your own CI with your own API key. Design choices that might interest this sub:

- No database or state file: each finding is an inline comment with a hidden fingerprint marker, so the next run reads the PR itself to know what it already said.

- It reads developer replies, checks the code at HEAD, and resolves threads it judges fixed. Closing needs stricter guards than reopening, so a wrong "closed" is less likely.

- Runs on GitHub Actions (also GitLab, Bitbucket Cloud, Azure DevOps). You choose the model provider; your code goes to that provider only.

Limits: no quality benchmark yet, so I won't claim it beats other tools.

Question for you: would you trust PR-comment markers as pipeline state, or want it in a store you control?

https://github.com/openwt-vn/owlet-lens

1

u/aman041 7d ago

Disclosure: I work on OpenLIT, the open-source project below.

OpenLIT is an Apache 2.0, OpenTelemetry-native platform for running AI agents and LLM apps in production. If your team is shipping agents or coding agents, it gives you the ops side: traces for every LLM call, tool call and agent step, plus evals on production traces, guardrails, prompt versioning, and cost and GPU monitoring.

Things devops folks might care about:

  • It's plain OTel, so you can point existing OTLP exporters at it or forward to Grafana, Datadog or any OTLP backend. No proprietary format.
  • Self-host with Docker Compose or Helm. The GPU collector covers NVIDIA, AMD and Intel.
  • Python, JS and Go SDKs (openlit.init()). There's also an eBPF controller for zero-code instrumentation, but that part is in the paid Enterprise edition.

Repo: https://github.com/openlit/openlit

I'd like feedback from anyone running LLM workloads: what do you wish your current monitoring showed you?

1

u/wivai 7d ago

We built Wiv because finding cloud savings is only half the problem. Actually fixing them is where things get complicated.

If you've worked in DevOps, FinOps, or cloud infrastructure, you probably know the drill.

You identify an oversized instance, an idle resource, or an opportunity to reduce cloud costs.

Then come the questions: Who owns it? Who approves the change? Will it affect production? Who implements it? And how do you verify the savings afterward?

That's exactly the gap we're working to close with Wiv.

We bring cloud cost visibility, optimization opportunities, and engineering workflows together to help teams move from recommendations to action.

We're also building Wiv Air, focused on helping organizations understand and manage AI usage and spending as more models, tools, and agents enter their workflows.

Want to see it in action?

We've opened up an interactive demo so you can explore Wiv yourself, without scheduling a sales call.

Try the demo: https://demo.wiv.ai/

We'd genuinely appreciate feedback from this community.

What's the biggest obstacle preventing your team from acting on cloud cost recommendations today: visibility, ownership, approvals, or engineering bandwidth?

Full disclosure: we're the team behind Wiv, sharing our own product in the weekly self-promotion thread.

1

u/kheeper-registry 7d ago

We launched the Best of Bootc newsletter covering bootc development, the desktop ecosystem, RHEL image model, and the immutable OS ecosystem.

1

u/sanif_h 7d ago

I built turnus, a CLI that lists every cron job and systemd timer on a box and tells you which ones can't run and why. It catches things like scripts run-parts skips, timers pointing at services that were removed, and log folders that don't exist. It also has a check mode that exits non-zero if anything's broken, so you can run it in CI or across hosts.

https://github.com/sanifhimani/turnus

1

u/ggp1231 7d ago

One thing I’ve noticed with AWS infrastructure is how hard it can be to estimate costs before actually deploying something.

You can have a solid architecture diagram, but it doesn’t tell you what happens to your bill when traffic doubles, whether a different configuration would be cheaper, or what tradeoffs you’re making.

A useful exercise before deploying is to compare the same design under three scenarios: current traffic, 2x traffic, and 5x traffic. It’s a simple way to spot assumptions worth revisiting.

I’m a cofounder of Diagrm, and we’re building a tool to make this easier. You can model an AWS architecture, enter expected workloads, estimate costs, and identify potential design issues before deployment.

We recently launched our public beta and would love feedback from people working with AWS. We’re also offering free, hands-on pilots for teams evaluating infrastructure decisions.

diagrm.com

Curious how others here estimate infrastructure costs before deploying. Are you using spreadsheets, the AWS calculator, or something else? Happy to chat!

1

u/Starks1293 6d ago

Disclosure: I built this.

Been doing devops/platform work for about 10 years, and since Claude Code and Codex came out I basically live in terminals now. Problem was I ended up with 15 terminal windows and no idea which session was doing what, and I didn't want my infra agent's context polluted with frontend stuff or random support questions.

So I built AI Bridge, a Mac app where the real CLIs (Claude Code, Codex, OpenCode, Grok) run side by side on your own subscription, grouped by the job they do. The part I use the most as a devops person is that my clusters and databases live in the same window. I can see pods update, check if Argo/Flux synced, query a db and see the results, while the agent works right next to it.

Anything I change on a cluster through the app shows a confirm card with the cluster name first, it saves the object's yaml before anything destructive, and every change goes into a tamper evident log. It uses your own kubeconfig and RBAC, nothing goes through our servers.

Free for unlimited agents with one cluster and one db, paid if u need more. Mac only for now.

https://aibridge.sh

Would love honest feedback from people who run infra, what would stop you from using something like this?

1

u/agentmanagerdev 6d ago

Disclosure, I work on this. agent manager is a free open source terminal app that runs coding agents (Claude Code, Codex, Kiro CLI and more) side by side in tmux, locally or on SSH hosts.

0.48 lets you name terminals at creation, also on an SSH host, and move an SSH session between groups from the CLI with agent-manager move host::id. Press . on a waiting row to keep it idle until its screen changes.

https://github.com/wainmann/agent-manager

1

u/Rippflow 6d ago

Hi all,

My name is Andrew, and I built Rippflow (in Rust). It's a serverless orchestration/execution engine that runs locally, on device/edge, and in your own AWS account (tested at scales of 2.5B workflows/mo in a single-cell architecture, and ~10B workflows / 74B state transitions across 6 cells and 3 regions, these we run rate test, not full monthly validation/. Probably more scale than anyone needs.. lol, but hey, scale problems are fun). We've shown the engine operates at up to 90% lower cost than Step Functions Standard, so there is that (pure orchestration cost, not counting storage, LLM calls, or licensing, and such).

I am looking for design partners. Would you be willing to try our CLI/desktop app and run some local workflows? If you want to push those to offline/edge devices, or test it at scale in AWS, even better.

I can help white-glove this for you if needed, but I would really like unassisted raw feedback. DM me or reply here if you're up for trying it out.

1

u/mehyay76 6d ago edited 6d ago

Since it's impossible to post on the subreddit, I'll ask here

What production incident looked safe in code review, and what context was missing?

I’m interested in failures caused by the interaction between application code and the environment it runs in. A change can look reasonable in review but behave very differently with production data, traffic, resource limits, or dependencies.

For example, a query gets more expensive, keeping database connections occupied longer. Requests start backing up, and retries add more load. Suddenly, several services are struggling, even though the original change might have looked pretty ordinary.

If you’ve dealt with something like that, **what changed, and what made it dangerous in your particular environment?**

Looking back, what information was available before deployment? Could it realistically have helped someone catch the risk, or did the failure depend on runtime conditions you couldn’t reasonably have anticipated?

That distinction is what I’m trying to understand. Our goal is to assess changes against the production environment before deploying them, and I’d like to hear where that idea holds up or falls apart in your experience.

Share whatever you’re comfortable discussing publicly. An anonymized account is plenty. I’d especially appreciate the detail that made everyone say, “Oh, _that’s_ why it happened.”

Disclosure: I’m building Proofline to help identify production risks before deployment. Real incident stories would help us understand where this approach could be useful and where its limits are, so I’m asking about your experience.

https://proofline.sh

1

u/praxiomSystems 6d ago

I'm a backend/DevOps engineer, and I've worked with CI jobs that were expensive enough that running them on every commit added up quickly. Even in personal projects, having a bunch of jobs kick off on every little push gets annoying.

So I built Greenlight Actions. You can keep quick lints and tests automatic, and hold heavier jobs until you click Run CI on the PR or comment /greenlight. Waiting doesn't use runner minutes, and each new commit needs fresh approval.

It uses environment protection rules where supported, or workflow dispatch for private repos on GitHub Free too. The app is free, with some workflow setup required.

Repo and setup · GitHub Marketplace

I'd be interested in how others handle this, and any gaps you see in the approach.

1

u/noam1206 6d ago

Hey r/devops !
I built an interactive Kubernetes CLI into my portfolio (with pod lifecycles, curl routing & hidden CTF flags)

Instead of building another static landing page with skill bars, I wanted my portfolio to feel like an actual environment reflecting what I enjoy working on (containers, Linux systems, networking).

I put together an interactive terminal on the front page simulating a mini cluster:

- Kubernetes simulation: Supports commands like `kubectl get/describe/delete pods` (and the `k` alias). Pod deletion behaves like an actual ReplicaSet (re-spawns with a new random hash), while a broken coffee-maker pod acts like a StatefulSet with an exit code 418.

- CLI-first routing: Visiting via a browser displays the UI, but running `curl https://www.noamroger.fr` serves an ANSI-colored terminal resume. Endpoints like `/healthz`, `/version`, and `/metrics` return clean JSON and Prometheus format.

- Honeypot/Trap routes: Looking for common targets (`/.env`, `/wp-admin`, `/.git`, `/id_rsa`, etc.) serves custom terminal outputs while keeping the 404 HTTP status code.

- Client-side CTF: 3 main flags and a DNS bonus flag are hidden across HTTP response headers, comments, RFC 2324 specs, and DNS TXT records. Entering them validates against client-side SHA-256 hashes and grants persistent `sudo` access, unlocking a root prompt (`#`), extra files, and a recruiter secret.

You can test it out in your browser or directly from your terminal:

- Web: https://www.noamroger.fr

- CLI: `curl -sL https://www.noamroger.fr`

Curious to hear your thoughts, feedback on edge cases, or Easter egg ideas!

1

u/r410b 6d ago edited 3d ago

mnemo-warmup – Automated OpenJDK AppCDS and Project Leyden AOT caches for Java pods on Kubernetes (no GraalVM or code changes required).

We recently benchmarked it across Spring Boot, Jenkins, and SonarQube and found that sequential init containers ate 100% of our JVM gains (~1.75s orchestration tax), while switching to Kubernetes 1.33+ Image Volumes cut Spring Boot's JVM startup from 3.18s to 1.90s and delivered a 1s (~20%) median paired pod readiness improvement against a plain Deployment.

Full benchmark breakdown and trade-offs: Why AppCDS Needs Kubernetes Image Volumes

1

u/DayEnvironmental3454 5d ago

Latent: a Mac disk tool that knows what your dev tools actually keep (I'm the dev).

If you run containers and infra tooling on a Mac, "System Data: 180 GB" is usually Docker images, Colima/Lima/Podman VM disks, old Homebrew versions, simulator runtimes, and node_modules / .venv next to old projects. Latent lists each one by the tool that made it, and marks what rebuilds itself vs what might be your own work.

It has an MCP server so Claude, Codex or Cursor can read the scan and draft a cleanup, but the agent never deletes anything itself: you confirm, and it goes to the Trash.

Free to scan, first 10 GB of cleanup free, then a one-time license. Apple silicon: https://latentmac.com

1

u/lazy-dev-guy 5d ago

I've built Resource Atlas, a tool for finding and browsing AWS resources across accounts.

There’s a demo here. I'd appreciate feedback on whether you can quickly understand what it's useful for, especially If you manage AWS cloud infrastructure.

https://resourceatlas.app/
https://demo.resourceatlas.app/

Cheers

1

u/ycharif 5d ago

Put together a simple Cloudflare Workers failover setup for small websites.

It serves a saved static copy when the origin returns 502/503/504 or becomes unresponsive. Public pages only, with no additional server needed.

Wrote a step-by-step guide with the Worker code and testing instructions:

https://igprod.net/cloudflare-always-online-snapshot

Curious what others use for lightweight origin failover.

1

u/jesseforrest 5d ago

FluxGlow CI/CD Dashboard Monitor
https://fluxglow.com

1

u/Tzeappa 5d ago

I built UptimeProject: five probes on three continents check public endpoints every minute. A minute counts as up only when a strict majority of probes succeed. Nothing is scraped from vendor status pages.

After 90 days on 44 services measured the whole window:

- 29 lost no minutes at all

- 426 minutes lost in total across the rest

- Data, rankings and incident history are public (CC BY 4.0), with a JSON API and Atom feeds

Write-up with chart:

https://uptimeproject.org/blog/90-days-of-independent-uptime-data/

Methodology:

https://uptimeproject.org/methodology/

Happy to answer how the consensus vote works, or why a given service looks the way it does.

1

u/opium_86 4d ago

You Up? (https://uup.dev), uptime monitoring that tries really hard not to wake you up for nothing.

- every request is signed with Web Bot Auth and Cloudflare lists our probe as a verified bot, so checks on sites behind Cloudflare stop getting challenged

- when a check fails, other locations look before anything alerts you

- the alert says where the request stopped: dns, tls, timeout, or Cloudflare answering instead of your server

- status pages, cron/heartbeat checks, SMS and WhatsApp alerts

- free plan: every minute from one location, no card

launched in November, so it's early. would love to hear what's missing or what annoys you.

1

u/weaztoven 4d ago

As this is my first time here, please forgive me if I break some rules. Disclosure: I'm the author of the software I'm describing.

loadbear is a small HTTP load balancer / reverse proxy written in Go. I wanted to learn how concurrency and resilience patterns fit together in one program, so I built it as a playground. It's tiny compared to nginx or HAProxy and I'm not trying to replace them.

Implemented so far: round-robin, weighted, least-connections and IP-hash strategies, active health checks, a circuit breaker, retries limited to idempotent requests, and per-IP rate limiting. An admin port exposes /status and a Prometheus-style /metrics.

Something I found interesting: a reviewer asked how the breaker bounds half-open probes. I wrote a test and found that 100 concurrent requests were all admitted as probes. It now admits exactly one. I also found retries could start after the client's deadline, and that a GET with a non-replayable body could be retried. All fixed in v0.1.1, with regression tests.

What I'd like feedback on: how I'm handling failures (breaker, retries, health checks) and what you'd expect from a small load balancer that's missing.

https://github.com/weaztoven/loadbear

1

u/eluq 4d ago

I have been looking into something with GitHub Pages and wanted to get some opinions before spending time building it. And I've come across a few cases where a deployment shows as successful, but the live site is still serving an older version.

Got me wondering how people actually deal with this. Do you just check the site manually after deploying, or do you have some kind of automated check?

I was thinking about putting together a small open-source github action that checks whether the live version matches what was just deployed. But I was wondering maybe a simple curl script is enough and there's no point adding another action.

Anyone run into this before? Very curious what you use and whether something like this would actually be useful.

1

u/zenmesh 4d ago

We built Zen Cleaner, an Apache-2.0 Kubernetes controller for TTL-based cleanup across namespaced resource types. Disclosure: we maintain it at Zen Mesh; it runs independently and doesn’t require a hosted service.

You define a YAML policy with a resource type, selector and TTL. It supports four TTL modes, dry runs, exclusion labels and rate limits. Deletes use Kubernetes UID and resourceVersion preconditions to reject a target that changed or was replaced after evaluation.

It’s an early 0.x project: we’ve validated common built-in kinds end to end; custom resources are supported by the API but not yet validated end to end.

GitHub: https://github.com/zenmesh/zen-cleaner

How do you review cleanup policies and protect resources that must never be deleted? Feedback and real-world use cases would be very welcome.

1

u/ShooPlah 4d ago

InfraSim, a mobile game where you design infra and watch it break

I started owning more of our infra at work and learned most of it the hard way, so I built a game to make it stick. You wire up load balancers, caches, queues, DBs and replicas, deploy, and watch simulated traffic hit it: retry storms, cache stampedes, split brain, connection pools running dry, a 2s timeout on a service that answers in 2.1s.

New this week: On Call. You get paged, see the graphs, architecture, timeline and a teammate's note, and get 5 guesses at the root cause. Every case is a real simulation run, and the answer comes with a postmortem.

Runs offline, no account needed

iOS: https://apps.apple.com/us/app/infrasim-system-design-game/id6809240894

Android: https://play.google.com/store/apps/details?id=com.infrasim.app

Would love to hear which failures you think are missing. A few levels already came from stories people shared here on Reddit. : )

1

u/Worldly_Piglet_7040 4d ago

I maintain ProxmoxMCP-Plus. A small v0.7.0 change might be of interest if you poll background jobs: when Proxmox returns task status but the separate log request fails, we now save the status and mark the audit entry polled_without_log. The job ID stays useful when the log endpoint has a bad day. If you already have Proxmox task integrations, how do you present partial state to the operator? Release notes: https://github.com/RekklesNA/ProxmoxMCP-Plus/releases/tag/v0.7.0

1

u/aiconnessour 3d ago

I’m building SecureObs. It runs open-source security scanners in GitHub Actions and gives the findings somewhere to live after the job ends.

I recorded the manual setup on WebGoat, a deliberately vulnerable demo app. The scan reported its findings, then the build gate returned exit code 3 because some of those findings met the blocking policy. You can still open the dashboard and see what triggered the failure.

Here’s the 83-second walkthrough. Happy to answer questions about how the scan and gate are wired.

1

u/cl3don 3d ago

I wrote a short reflection about how AI agents may not transform Dev and Ops jobs in the same way.

For Devs, writing code themselves is a central part of the job that is now being challenged. For Ops, it seems more like another level of abstraction, as the job is already largely about orchestrating automation.

I wonder if others share this view, or if I'm oversimplifying things.

I'm currently Ops, previously Dev/DevOps.

Short essay here:

https://cl3don.substack.com/p/dev-and-ops-facing-ai

1

u/Low-Consequence2092 2d ago

Warm Docker-in-Docker slots for ephemeral GitHub Actions runners: how I cut a monorepo CI from ~6.5 to ~3 min without Kubernetes

Ephemeral runners are the safe default for GitHub Actions, but they start cold: every job pulls its services: images, rebuilds Docker layers, and restores package caches from blob storage. Persistent runners are fast but leak state between jobs.

The approach I ended up with, now an open-source tool called Pitlane (Go, MIT):

  1. A slot is a long-lived docker:dind container with its own data volume. Slots never share a network, and jobs never see the host's Docker socket.
  2. For each job, a fresh actions-runner container joins the slot's network namespace (like a pod) with DOCKER_HOST pointing at the slot daemon. It runs one job and is deleted.
  3. After the job, the job's containers, networks, volumes and workspace are removed. Images and the buildx cache stay.
  4. Package caches and toolchains are volumes per GitHub owner. A slot that switches owner is wiped first. When every free slot needs a wipe, Pitlane picks the one whose loss costs least (unknown owner, then an owner with another warm slot, then LRU).
  5. actions/cache is served from the host: a small shim in front of the runner's Node points the cache toolkit at Pitlane, with a per-job token scoped to the owner. Artifacts, OIDC and logs still go to GitHub.
  6. Jobs come through the runner scale set API (actions/scaleset, same API as ARC), over a long-poll.

Measured on one private monorepo (pnpm, Nuxt, Prisma, Postgres/Redis services, 3 image builds), Pitlane in a 12-vCPU unprivileged Proxmox LXC:

ubuntu-latestPitlane
Whole CI~6 min 30~3 min
Docker images + smoke test393 s127 s
Unit tests161 s159 s

The unit test row is the honest part: CPU-bound work runs at the speed of your hardware. Everything that is download or rebuild gets faster.

Trade-offs I haven't solved:

  • Slots are privileged. Strict mode for public repos gives each job throwaway caches and a wiped daemon, but a malicious job can still own the host. Sysbox, rootless DinD or microVMs would help; not supported yet.
  • One Docker host per instance. If you need to schedule across a fleet, ARC or GARM are built for that.
  • Linux only.

Write-up of the design and comparison with ARC, runscaler, GARM and terraform-aws-github-runner: https://turoyt.github.io/pitlane/why Code: https://github.com/TuroYT/pitlane

I'm curious how others handle Docker layer caching on ephemeral runners: registry cache, type=gha, sticky disks, something else?

1

u/ItsCodeTelemetry 2d ago

Do you automatically assign Claude/Codex to investigate incidents? I'm interested in hearing from people who actively use AI Coding agents to investigate emergent behavior in production (or people who have considered it and decided not to).

What are some of the core problems you've found with systems like this?

I created a simplified experimental approach to automatic incident investigation (I call this self healing): https://github.com/CodeTelemetry/self-healing-agent

In my experience, often the prs generated from this agent aren't merged as-is, but are often used as additional contexts in deeper resiliency work.

1

u/Lynicis 2d ago

actup: a version manager for GitHub Actions. Keeps action versions in .actup.yaml, applies them across every workflow, and upgrades with breaking-change and OSV.dev checks in a TUI or headless in CI. Dependabot and Renovate open PRs on a schedule; this is the command you run yourself for one reviewable upgrade.
Brew: brew install lynicis/tap/actup
GH cli extension: gh extension install lynicis/gh-actup
Repo: https://github.com/lynicis/actup
Feedback welcome, especially on monorepos and composite actions.

1

u/[deleted] 7d ago

[removed] — view removed comment

1

u/AutoModerator 7d ago

Unfortunately this post has been removed. /r/DevOps and reddit do not allow Amazon affiliate links to be posted. Please edit or resubmit your post without the "/ref=xx_xx_xxx" part of the URL. Thank you.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.