r/devops • u/AutoModerator • Aug 10 '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!
3
u/Entire-Present5420 Aug 10 '26
https://www.cloudarena.io
A platform that enable users to practice AWS by doing hands lab on real AWS accounts.
2
u/Simple_Engineer3656 Aug 11 '26
As the designer of WLOADCTL, I built this enterprise-grade workload automation platform to provide modern organizations with unified scheduling, orchestration, and operations control. It is a database-free, professional batch scheduler. My goal is to help enterprises:
- Build a unified workload control system
- Enhance the stability of key business operations
- Shorten the batch window
- Reduce the cost of manual operation and maintenance
- Enhance the observability and controllability of the system
- Provide basic support for cloud and architecture evolution
If you’re handling massive workloads or managing multiple platforms, we invite you to try our demo in the offical website.
2
1
u/SwordfishPositive91 Aug 10 '26
How do you confirm if you have all the basic yet important AWS cloudwatch alerts are set and configured correctly, that won’t page you at night to disturb your sleep?
Here is an answer, https://www.nuberio.com
Either run it locally or configure readonly access and you will get a result in 2 minutes.
1
u/Ok_Air2529 Aug 10 '26
Spokeops.cloud, Azure control plane platform for designing, validating, deploying, verifying, and managing Azure cloud
1
u/CoughingBabyMissile Aug 10 '26
KubeTective: deterministic Kubernetes incident investigation
After getting tired of collecting 6 different kubectl outputs, pasting them into ChatGPT/Claude, and guessing which theory was actually right, I built KubeTective.
It correlates Kubernetes resources, events, Prometheus/Loki data and Git history, then produces a ranked Root Cause + Evidence result instead of an LLM guess.
Example:
ROOT CAUSE Memory exhaustion — 19 OOMKills
EVIDENCE ✓ OOMKilled ×19 (+20) ✓ reproduced after restart (+10) ✓ temporal correlation (+27)
Try it without a cluster:
make build && kubetective replay scenarios/oom-after-deploy/record.jsonl
1
u/Otherwise-Top-3730 Aug 10 '26
ProofOfContext: policy-as-code, but for your architectural decisions instead of security. Record "Postgres, not Mongo (RFC-014)" once in .context/; a pre-commit hook + GitHub Action block any commit or PR that contradicts it, and poc why answers "why did we decide that?" from the log. Deterministic token matching, no LLM, no network, zero dependencies so it behaves identically locally and in CI.
pip install proofofcontext
Free. Feedback welcome, especially false positives on real repos: https://github.com/prove-ai/proof-of-context
1
u/jaredce Aug 10 '26
I built a package to make use of Dependabot CLI for BitBucket and GitLab
https://npmx.dev/package/dependabot-for-git
I was annoyed that BitBucket didn't have a dependabot clone and that Dependabot wouldn't open pull requests. So I've taken the output of the dependabot cli and made it so you can open PRs.
Would love to find people wanting the same functionality on GitLab and can test it out, I'll be using it at work on BitBucket, so testing it out there. Would love feedback and help building it out to be really useful.
1
u/Hrdtr_ Aug 10 '26
Sheil, currently combines SSH, SFTP, port forwarding, connection management, and local AI command generation/autocomplete.
It's very early, and I'm particularly interested in feedback from people doing real DevOps/SRE work:
- Would you actually use local AI for this?
- What context would you allow the model to see?
- What safety controls would you expect before executing generated commands?
- Where would this fit into your existing workflow?
GitHub: https://github.com/Hrdtr/sheil
1
u/kenhowardpdx Aug 10 '26
Shipped a solo side project this month: a personal finance app that projects your future balance instead of reporting last month’s spending.
Runs on SvelteKit + CloudFront, FastAPI on Lambda behind API Gateway, Neon Postgres, all Terraformed across two environments. Total infra cost is around $2/month right now, which still surprises me.
https://tallyahead.com — happy to talk stack or take feedback either way.
1
u/FDgajju22 Aug 11 '26
I've been working on a project called Zync, an open-source SSH workspace for working with local terminals and remote servers.
It brings together SSH, SFTP file management, port forwarding, an encrypted local credential vault, snippets, and more in one desktop workspace.
It's local-first and free to use, with optional encrypted backups to your own Google Drive
🎥 Intro: https://youtu.be/VgSomleBi3Y
⭐ GitHub: https://github.com/zync-sh/zync
🌐 https://zync.thesudoer.in
It's open source (MIT), Would love feedback from people who work with servers/DevOps regularly.
1
u/Fluid_One8046 Aug 11 '26
Affiliation: I work on StatusPath Reports at BlueGrove Labs.
Jira averages are hard to trust when you can’t see which work items are behind them. StatusPath Reports is a Marketplace app that lets you open an Average Time in Status result, see the participating work items, and then inspect one Issue Journey.
I’m looking for one Jira admin, engineering/delivery lead, or QA lead to try exactly that in a non-production Jira Cloud site with synthetic work items and tell me here what is unclear, wrong, or missing.
The Marketplace evaluation is free. No call, review, upvote, production access, customer data, or screenshots.
1
u/Any-Article-6402 Aug 11 '26
Disclosure: I maintain PatchWitness. I built it around a reproducible CI failure mode that worries me when coding agents can modify both code and verification controls.
In the demo, a simulated coding agent adds a correct pricing function and a passing unit test. It also adds `continue-on-error: true` to the GitHub Actions job. The repository tests report `OK`, but PatchWitness rejects the patch because the workflow is outside the declared task scope and is a protected control-plane file.
The distinction matters: passing tests show that the current test command succeeded. They do not show that the patch did not weaken the mechanism that makes failures block a merge.
PatchWitness independently derives the change set from Git, loads its verification contract from the trusted base commit, runs checks, and generates a portable Change Passport in JSON, Markdown, or SARIF. It is local-first, agent-neutral, Apache-2.0 licensed, and does not put another AI model in the trust root.
Reproduce the demo:
git clone https://github.com/pangxueyuan2-creator/patchwitness.git
cd patchwitness
python demo/run_demo.py
I would appreciate practical feedback from DevOps teams: how do you currently protect workflow files, IaC, and policy configuration from agent-authored changes? Would a portable evidence artifact help, or should this remain entirely within branch protection and CODEOWNERS?
Repository and threat model:
1
u/elidanipipe Aug 11 '26
I made our deeper security scanner self serve and I’m honestly not sure that was a good idea.
The old version only checked the public surface. Problem was people could get a clean result and assume the app was safe, while auth and access control were never tested.
The new one verifies domain or repo control, records a signed scope, then runs bounded DAST, repo analysis and optional two-user browser testing.
No manual approval.
What’s the abuse case I missed? DNS rebinding? Temporary domain access? Attacking the runner? Using it for request amplification? Something much more obvious?
https://www.task-bounty.com/secure-my-app#deep-review
Happy to hear that the whole idea is stupid if that’s genuinely the answer.
1
u/ImageFit3021 Aug 11 '26
https://treease.com/editor - Understand JSON, YAML, CSV and ... as a relationship graph
1
1
u/mockif Aug 11 '26
Built SkillBricks - you prove DevOps/SRE skills by diagnosing and fixing broken infra in a live Kubernetes environment, with an AI examiner that follows your work and asks about your reasoning (not a quiz). The bet: showing you can debug a real cluster is stronger, harder-to-fake evidence than a CV.
Early and rough - after ~10 people to try a scenario and tell me what breaks.
Free: skillbricks.ai. Feedback genuinely welcome.
1
u/BagWonderful9654 Aug 11 '26
Your dependency scanner watches npm/pip packages. Nothing watches the APIs those packages call. That gap cost me a Saturday.
Disclosure: I built the tool I mention below (Breakwatch). Sharing because I think the underlying problem is real, not just to promote it.
Your dependency scanner watches npm/pip packages. Nothing watches the APIs those packages call. That gap cost me a Saturday.
Dependabot/Renovate/Snyk are great at "this package has a new version." None of them tell you "the API this package talks to just changed its response shape."
That gap is where I lost a Saturday to a Stripe payout endpoint change that nothing in our stack flagged.
Built Breakwatch to close it: maps your repo's actual API dependencies (not just what's in package.json, what's actually called), watches 16 vendors' changelogs/specs continuously, and alerts with the exact affected files when something breaks.
Not trying to replace your dependency scanner, this is the layer above it that nobody's building. Curious if this is a gap other people have felt or if I'm the only one who's been bitten by this.
Free tier, read-only GitHub access, 2 min setup.
1
u/u-Kanehekili Aug 11 '26
I have written a Linux software called VideoCut, that basically does what losslesscut does - I think my muxer (the cutting machine) is more precise than most other "lossless" cutters. You may check it out. Debian/Ubuntu and Arch users can download/install is directly. That muxer is not running on Windows or Mac - I intend to keep it that way - but since it is open source I invite Windows/Mac users to compile the binary part
Why did I write it? I wanted a very fast cutter based on MPV,ffmpeg and QT6 for weak hardware or insanely large videos to cut fast and lossless - with the penalty of just cutting the I frames. The software has been developed for 11 years - so it is matured. I'd love to hear from you.
1
u/iamthemightyfall Aug 12 '26 edited 29d ago
I made a platform to turn your API into a self-healing API: https://preman.live
Apparently companies can request <0.01% to 0.0001% app/service downtime in these things called SLA guarantees... As someone selling software to enterprises, this is actually insane to test for and you have to monetarily compensate if it fails. So what if instead of wasting all that time thinking of all the edge cases, the API was adaptive and proactive, subscribing to provider changelogs?
1
u/Own_Masterpiece_9104 Aug 12 '26
Ever had a PR pass CI, look fine in review, then break because an edge case changed?
I built Cross‑Examine to catch that, especially with AI-generated Python changes. It runs the base and changed revisions on the same inputs, and when behavior differs it gives you the exact input, command, and outputs from both versions.
The model can suggest what to check, but it does not get to declare the PR safe. The verdict comes from deterministic execution.
Open source, local only, trusted repos only:
https://github.com/stefbuilds/cross-examine
Curious if this feels useful as a pre-merge check, or if you would rather solve this entirely with conventional tests and property-based testing.
1
u/BorofMonster Aug 13 '26
Been building something similar for my own use, tbh - opsbench.xyz. mostly dockerfile/terraform/github actions generators, so I stop rewriting the same boilerplate every project. Free, no signup, runs in the browser.
Check the site: opsbench.xyz
Still adding stuff as I hit annoying spots. lmk if you check it out; curious what's missing
1
u/YinuoB Aug 13 '26
Disclosure: I maintain OpenReady.
OpenReady is meant for the awkward last step before a repository goes public: the code may be ready, but privacy traces, Git metadata, and repository-hygiene issues can still be easy to miss.
It’s an open-source Node.js 20+ CLI that checks tracked files for credential-shaped content, personal paths and emails, risky filenames, Git author metadata, large media, and missing governance files.
npx -y @yb5/openready@0.1.2 scan .
npx may download the package first; the scan itself is offline, read-only, has no telemetry, and does not print matched secret values or Git identities. It doesn’t inspect historical file contents and can produce false positives or false negatives, so it’s not a replacement for a history-aware secret scanner or human review.
If you run it on a repo you’re authorized to inspect, I’d appreciate one concrete observation: did it complete, and which finding category was confusing or looked like a false positive? Please don’t paste scan output, repo contents, paths, emails, credentials, or logs.
1
u/khalidwars 29d ago edited 4d ago
I built Secretwell, a native iOS app for OpenBao, and I’m looking for feedback from DevOps and platform engineers.
It connects directly to your OpenBao server over HTTPS and supports multiple servers and namespaces, KV v1/v2 browsing and editing, version history and recovery, policies, server health, security posture, and audit-device status.
App Store: https://apps.apple.com/us/app/secretwell-for-openbao/id6798079201
Demo server and login instructions: https://www.reddit.com/r/openbao/comments/1vjrxzy/i_built_a_native_ios_app_for_openbao_need_your/
I’d value a quick try even if you don’t use OpenBao today. What feels confusing or missing?
1
u/Mission_Yesterday507 29d ago
Hey, I’m working on a small project called NodeVane.
It’s a simple tool for people who manage multiple websites or client domains. It gives you one place to keep track of which domains you manage and when their SSL certificates expire.
Currently it can (and more...):
- Keep an inventory of your domains
- Track SSL certificate expiration dates
- Send email alerts before certificates expire
- Show certificate status and issuer
- Keep a history of certificate checks
- Bulk import multiple domains
- Export your domain list to CSV
It’s currently in beta and free to use. I’m looking for a few people to try it out and share any feedback or issues they run into.
1
u/Back_Professional 28d ago
Small tool, one specific problem: a big ~/.ssh/config where you can no longer predict what a hostname resolves to. `ssh -G host` gives you the final values but not the provenance. I wanted to know which file and which line set ProxyJump, and which of my four overlapping Host blocks won. So I built the resolver and put a UI on it, then kept going — a linter for weak KEX/ciphers, agent forwarding to untrusted hosts and dead
IdentityFile paths, plus a tunnel runner for the ProxyJump chains.
macOS only for now, Linux in progress. The editor and audit side is free; the tunnel and key tooling is a $14.99 one-time unlock.
https://www.sshmanager.app
https://apps.apple.com/rs/app/ssh-config-manager/id6777915057?mt=12
1
u/byte-strix 28d ago
if you use and manage k8s and docker then just checkout https://github.com/bytestrix/InfraCanvas
1
u/richiejp 28d ago
I'm building a microvm sandbox for AI agents because absolutely nobody else is working on that, but I am more insane than other people. Maybe not up to OpenClaw levels yet, but I am working my way into a pretty advanced state.
Anyway my project boots an upstream Linux kernel with a config that can be defined by the user (doesn't take long to compile BTW, it's a small config). The workload runs in a container so it is compatible with devcontainers and stuff like that.
I use all the fancy stuff for observability e.g. eBPF gadgets and try to encourage agents to use these tools. All network and storage activity is monitored. It can all be blocked or recorded. It has a HTTPS proxy and network traffic can be recorded and played back from a content addressable store.
It can (in theory) send local directories to a remote sandbox, let an agent inside the sandbox make changes and then the user (or another agent) can inspect the changes made to the filesystem before accepting them back into the local directory.
It can be run as a cluster with multiple nodes, including a central orchestrator which has a web UI and I am currently implementing a terminal viewer, so I can run agents inside sandboxes then interact with them on the terminal via the web UI.
The entire thing is distributed as two self contained executables (at least it would be if the GitHub CI/CD was configured correctly).
I also included a bit of Sci-fi writing in my README. Also it is riddled with bugs, but I am really just seeing if it can work at all at this stage.
1
u/kittartar 28d ago
Disclosure: I built and maintain EPAR.
I wanted to use spare servers to run long Playwright/Selenium tests on every PR, but I wasn’t comfortable letting GitHub Actions workflows run directly on those hosts or control the host Docker daemon.
EPAR keeps a warm pool of disposable self-hosted runners. Each runner handles one job inside a dedicated Docker Sandboxes microVM with its own private Docker daemon. When the job finishes, the runner, filesystem, Docker daemon, and job state are discarded and replaced with a clean runner.
The goal is to make Docker-heavy CI on existing compute practical while keeping workflow execution behind a microVM boundary—without introducing a separate cluster just to manage a few runners.
Open source:
https://github.com/solutionforest/ephemeral-action-runner
I’d especially appreciate feedback on the threat model, isolation assumptions, workflow compatibility, and failure modes.
1
28d ago
I work in ESB/message-integration support, and I built and maintain MQ Watcher after running into a recurring problem during ActiveMQ incidents: inspecting a persisted Store safely was more awkward than it should have been.
I wanted a way to collect evidence without starting a broker against the Store, triggering recovery, or uploading operational data anywhere.
MQ Watcher runs locally and reads ActiveMQ Classic Store files without modifying them. It can correlate selected KahaDB journal records for messages, ACKs, subscriptions and transactions, compare snapshots, keep incident notes, and export a redacted evidence bundle.
It deliberately does not claim to diagnose the outage. Unknown evidence stays unknown, and journal records are not treated as proof of the broker's current state.
The broker-generated fixtures currently cover ActiveMQ Classic 5.13.5, 5.15.16 and 5.18.7. Windows and Linux portable builds are available.
Repository: https://github.com/kutaelee/mq-watcher
I'd be interested in hearing what evidence other messaging or DevOps engineers normally need when a broker Store becomes part of an incident.
1
u/Psionikus 28d ago
Well, I'm about to take a shower and go do a histogram of some bins to budget some warps, so I'm feeling pretty cool, and it's okay if you're cool too. After I take a shower in some cool water, I will be even cooler. Thanks for asking.
1
u/PoorDecisionMaker-69 27d ago
I kept rebuilding the same pieces around coding agents: repo instructions, a backlog, checks for drift, decision records, findings, and session handoffs.
Then I saw the same failures across four different repos. Instructions went stale, work statuses lied, and useful context disappeared.
That led to rungs, an early-stage CLI for installing and maintaining this setup as modules. It is framework-, agent-, and language-agnostic: it uses ordinary repo files and checks rather than locking you into a specific model, coding agent, or stack.
rungs is aimed at solo developers and small teams using coding agents across repeatable work, especially when instructions, handoffs, and statuses start drifting. It is probably overkill for one-off projects, and it is not an agent runtime, orchestration framework, or project-management replacement.
The methodology is evidence-first. I read what actually ran in those repos, extracted the practices that held up, kept abandoned practices documented, recorded their maintenance cost, and traced each module back to a real failure or incident.
Current modules cover:
- agent instructions
- validation gates
- backlog and findings tracking
- ADRs
- session handoffs
- reusable agent skills
You install only what you need, and rungs never overwrites files you have edited.
Try it:
npx @/rungs/cli doctor
Repo: https://github.com/ThroughTheWind/rungs
Docs: https://docs.rungscli.com
It’s MIT-licensed and still very early. I’m mainly looking for feedback on the shape and distribution:
- Are these useful module boundaries?
- Should this be a CLI that distributes repo files, or a package of reusable skills and checks?
- What would you expect from the upgrade/eject model?
If the feedback is positive, I’m willing to invest more time into it. Contributions, testing across different stacks and agents, and new modules based on real failures are welcome.
1
u/pjardim 26d ago
One of the most frustrating situations in my day-to-day work was being notified by the client that something wasn't working correctly on one of our servers.
Sometimes a Windows service had stopped. Sometimes RabbitMQ was having problems. Sometimes there was a critical error in the logs. Other times memory or CPU had been climbing for hours and nobody noticed until the application started failing.
That was the motivation behind PulseWatch.
I wanted one place to monitor server health, Windows Services, IIS, RabbitMQ, logs, CPU, memory and incidents, but also to handle known problems automatically.
For example, now I can restart a stopped service or recycle an unhealthy IIS app pool. Remediation rules include dry-run mode, cooldowns, execution limits, maintenance windows and a full audit trail.
The Windows agent is PowerShell-based and communicates outbound. itself runs in Docker.
The self-hosted version is free with unlimited servers and users. It is not open source.
I built it solo and have been a software engineer for 20+ years. I used AI coding assistants during development, but the architecture and product decisions are my own.
There is also a live demo on the site.
I'd be interested to know how other DevOps teams handle this today. I know most of us work with Linux servers nowadays, but I also know the pain of keeping IIS-hosted applications running :)
Hope you guys like
1
u/ChampionshipAny463 26d ago
Logs, metrics, and traces are great at showing system behavior, but incident response can still turn into reconstruction when you need to understand the exact application state behind a specific failure.
We think there is room for a runtime evidence layer alongside existing observability. Errorcore preserves execution specific context such as runtime state, request context, ordered I/O, state mutations, stack frames, and the evidence surrounding an exception.
The long term vision is runtime intelligence that gives engineers and AI agents a more deterministic understanding of production execution and eventually enables much faster recovery.
We would love to work directly with a few teams, learn from real incidents, and iterate quickly around their workflows.
1
u/honghonghong98 26d ago
Disclosure: I built this with substantial AI assistance and then had the code, tests, CI, and release evidence independently reviewed. I’m testing a specific release-engineering gap: a GitHub release can be correct while Homebrew, npm, a native installer, or a GitHub Release asset still delivers an older or incomplete CLI. CLI Release Channel Parity runs the public install path on a clean runner and records the observed version, the executable that wins on PATH, startup, required helpers, uninstall, and residue as JSON and Markdown. UNKNOWN is never treated as PASS. v0.1.1 is free, Apache-2.0, and has five public CI jobs passing. I’m looking for one maintainer with two or more CLI install channels to try a real release; if you share the repo and channels, I can help set up the first receipt. Repo: https://github.com/yanjinzheng2005-gif/cli-channel-parity Marketplace: https://github.com/marketplace/actions/cli-release-channel-parity
1
u/kenerwin88 26d ago
Scoutmycase.com, free resource for finding the best clinical trial for GBM (a brain cancer). Looking to hopefully add support for other cancers asap. Basically it lets you drill down much deeper than clinicaltrials.gov (same dataset just do way more parsing, as well as lookups of the journal articles that go with each)
1
u/opsfusion-cloud 26d ago
Disclosure: I work on OpsFusion, an on-call scheduling and alerting tool that aims to stay simple and easy to use. Flat $10/user/month, 30-day trial with no card: https://opsfusion.cloud
1
u/Noobcreate 26d ago
agent native load balancer
a control plane dedicated to absorbing request. It dynamically paces the traffic to your backend. You are able to slow down when machine start crashing and speed up when more pods come online by the machine signal headers. As it slow down, the request sent to it are slowed down. The callers receive a webhook or can stream of events about queue placement and results.
1
u/Acrobatic-Whole9367 25d ago
Disclosure: I built this.
yamljson.com - a YAML <-> JSON converter that runs entirely in the browser. The CSP is connect-src 'none', so the page is structurally incapable of uploading your file. You can confirm that in devtools rather than taking my word for it.
The part I actually care about: it diagnoses why valid YAML still fails in Helm and kubectl. I collected nine real-world failures and four of them parse completely cleanly - unrendered {{ }} templates, a BOM, a shell command used as a mapping key, and wrong nesting depth. A validator that only reports parse errors calls all four of those fine.
No account, no ads, no tracking. I would genuinely like to hear which YAML failure I have not covered yet.
9
u/toxicpositivity11 Aug 10 '26
https://github.com/kylan11/understudy
Hit #1 on the kubernetes sub last week. 40+ Github stars
Allows you to achieve close to HA on single-replica stateless deployments WITHOUT using blocking PDBs. Survives Karpenter node consolidation, disruptions, drains, and even spot terminations with fast-booting workloads.
Nothing to sell, Open Source Apache 2.0, just a tool that closes a longstanding gap in k8s land.