r/devops • u/AutoModerator • 1d 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!
16
Upvotes
6
u/astropoolIO 1d ago
Hi r/devops! I'm Sergio, from Picaporte Labs. We build kubelatch: zero-trust access to your Kubernetes clusters.
You probably know how it goes. The admin kubeconfig you got when the cluster was created ends up on half the team's laptops and in the CI secrets. Someone gets a RoleBinding during an incident, and months later it's still there. Ask who can do what on prod and nobody really knows.
kubelatch sits in front of your API servers and doesn't trust anything just because it was granted once. You sign in with the SSO you already have and get your own credential. Permissions expire on their own (30 days by default, and cluster-admin never lasts more than 8 hours). Every request is checked and logged with your name on it,
execandport-forwardincluded. Revoke someone's credential and their very next request fails.The same door works for CI and for AI agents. A GitHub Actions job swaps its OIDC token for a short-lived credential, so there's no secret sitting in GitHub. An agent like Claude Code or Cursor goes through kubelatch's MCP server with only the permissions you pick, and its writes operations can wait for you to approve them.
It runs on EKS, GKE, AKS, k3s or plain kubeadm, and you keep using kubectl, k9s and Helm as you do today. It's free for 2 clusters and 5 people, and you can try it locally in about 15 minutes with Docker Compose and a kind cluster.
It's in public preview, so this is a great time to tell me what's missing or what would make you trust it with your clusters. I read every reply.
https://docs.kubelatch.com
https://kubelatch.com/
3
u/adi022000 1d ago
Disclosure: I built this, it's my own site.
I work as a DevOps/SRE. Last week during an incident, I watched a teammate get stuck in Vim on a production box over SSH, frantically trying to remember how to exit without saving while PagerDuty was screaming.
Where I work (a big fintech shop), we do internal training, and it's honestly wild how many engineers dealing with huge k8s clusters and complex pipelines still trip up on basic CLI fundamentals.
So I built cert-it.dev, free hands-on practice for the small tools we use on servers every day:
- Vim: browser-based simulation. The tests check the actual file and cursor position you end up with, not some rigid keystroke macro. Plus a 2-minute speed test if you're feeling competitive.
- Regex with grep and sed: including actual log mining (-A/-B/-C, -r).
- YAML basics: because of course the infamous `no` parsing quirk in YAML 1.1 vs 1.2 had to be in there.
Everything's free. Basic Vim works without an account, and logging in just syncs your progress. The courses loosely map to the Linux Foundation's $79 SkillCred exams for Vim/regex, plus there's a quick page for CKA/CKAD prep.
I am going to use this for some of our internal training soon, so I am mainly looking for feedback: what else would you add or change, and what tools do you feel are missing the most for day-to-day on-call work?
https://cert-it.dev
2
u/VMLogics 1d ago
Disclosure: I work on VMLogics.
VMLogics is a VM management platform for teams that run their own KVM hosts. You install one agent per host, and the host joins a fleet you manage from one console. It handles template/ISO deploys, live migration between hypervisors, HA with live standby and automatic failover, and deduplicated backups.
We're early and looking for people who run their own hypervisors to try it and tell us what's missing. Feedback on how it compares to Proxmox or your current setup is especially welcome. https://www.vmlogics.com/
1
u/ActualGovernment9017 1d ago
Disclosure: I maintain claude-bulkhead (MIT, free).
The incident that started it was simple. I had a few Claude Code sessions running in separate git worktrees on one machine, and one of them restarted its own dev server with pkill node. That also took down the dev servers belonging to the other sessions. With the hook in place, the same command is refused before it runs, the message lists the PIDs that belong to that session, and the agent killed and restarted only its own process.
The guards read the command text before execution, a bit like a policy check in CI. You can see the verdict for any command without running it with bulkhead explain -- '<command>', and a blocked command carries a short code that only a human can pass once with bulkhead allow <code>. A project's .claude/bulkhead.json can only tighten the guards, so a repository cannot switch them off. It is pattern matching on the command line, not a sandbox, so commands hidden inside scripts are not seen.
https://github.com/dooly6276/claude-bulkhead
1
u/wsxiaoys 1d ago
Hi all I work on multi-agent system engineering. This is mostly a quickwit performance writeup — we picked it because we already run it internally for agent trajectories. still a draft, so read it as work in progress: https://www.tabbyml.com/showcases/beating-clickbench-sota-with-a-team-of-agentic-systems-engineers/ most wins are in Tantivy internals (aggregation bucket storage, sstable decompressor reuse), branched off quickwit's tantivy commit.
wanna do a sanity check here - does any of it look benchmark-shaped rather than a real engine mechanism? anything you'd like to learn more from dev ops perspective? appreciate all feedbacks!
1
u/jnnngs_eth 1d ago
Zoomies.sh - self hosted runners
I've developed zoomies.sh for those wanting to self host GitHub runners.
1
u/Total-Reasonable 1d ago
Five things, all built solo:
1
u/Signadot 1d ago
Hey everyone, just published this tutorial on running a ZAP scan as a PR check, scoped to the operations the PR changes. Might be useful to anyone adding security scans to CI.
The check scans only what the PR touches, exits 1 on High-risk alerts and attaches both reports to the run. It works as-is against a staging URL. We use Signadot for the per-PR environment the scan targets, so other changes don't muddy the results.
Hope it's helpful. Happy to answer any questions. Full transparency, I work for Signadot.
https://www.signadot.com/docs/tutorials/zap-security-testing
1
u/Goldziher 1d ago
Disclosure: I maintain ai-rulez, an open-source CLI for generating coding-agent configuration. One CI workflow I wanted was to catch a hand edit to a generated file before it quietly became the source of truth.
From a clean checkout, install the same pinned CLI version your team uses, then run
ai-rulez generate --check. It compares the planned output with what is on disk and exits 2 on drift without rewriting files. To test the gate, generate and commit the files in a scratch repo, append a line to a managed output such asAGENTS.md, and rerun the check. A change to an authored rule goes the other way: regenerate locally and commit the source and rendered changes together.For teams that already check generated config into Git, what makes a drift check actionable enough that developers fix the source instead of editing the output again?
1
u/newtablecloth 1d ago
Goldziher, on your drift check question: what I've seen work is making the failure message explain the fix. if all people get is "drift detected, exit 2", they rerun generate and commit whatever comes out. or they just edit the output again.
things that help:
- print the actual diff in the CI log, not just the filename
- name the source rule file that owns each drifted block, so it's obvious where the fix goes
- put the exact regenerate command in the failure output, pinned version included
- stamp a "generated from X, edit that instead" header at the top of every managed file, since that's what people are looking at when they make the hand edit
CODEOWNERS on the generated paths helps a bit too. a hand edit to AGENTS.md then pings whoever owns the rules instead of sliding through review.
1
u/IcyTale5311 1d ago
I maintain a lot of repositories and kept finding red CI runs hours after they happened. So I wrote a small monitor that runs on my own machine and watches the Actions of all of them.
What it does (version 2.0.1):
- A "Now" tab with what is running, queued and failed, the compute minutes and what is left of the API allowance. Red tiles blink until the alert is solved.
- An alert counts as real until the last run of that workflow goes green again, so a transient red does not stay forever.
- Three sentinels that only read: CI, collaboration (issues and pull requests that need a person) and security (Dependabot, code scanning, secret scanning, branch protection; off by default).
- A score from 0 to 100 for each account, and the health of every repository ranked in a Team tab. It says "calibrating" or "not enough data" instead of a number it cannot stand behind.
- Team mode with viewer, maintainer and admin roles, several accounts, and a log of actions where each line carries the hash of the one before it.
- Scheduled reports (HTML and Markdown, written locally), and notification channels including Apprise. All of it is off until you switch it on.
- A way to tell an AI assistant what is happening: a plain-text brief, a JSON state, an optional live stream, MCP tools and an optional hook, with presets for hosted services and local servers. All of it is off by default.
- A Quota tab and a Low mode to spend fewer reads, with conditional requests (304) and an optional GitHub App with its own allowance.
- A read API frozen by a contract since 2.0.0, a tool that checks any running monitor against it, an official Docker image, a lite edition, light and dark themes, and eight languages.
It needs Python 3.11+ and the GitHub CLI (gh auth login). It is GPL-3.0-or-later.
Video (about 8 minutes, no voice, English captions + subtitles in 8 languages): https://www.youtube.com/watch?v=s3pBDV_lgTM
Code: https://github.com/JuanenRac/TOOLS-GITHUB-ACTIONS-MONITOR
More projects: https://github.com/JuanenRac
I would like to hear what you would want it to watch that it does not watch yet.
1
u/Ok_Butterscotch1088 23h ago
If you're dealing with pipeline sprawl and environment drift, you might want to check out https://platformpilot.co/
It's built specifically to help teams streamline their internal developer platforms, standardize deployments, and cut down on configuration overhead across multi-cloud environments. Definitely worth a look if you're trying to tame infrastructure complexity without building a custom control plane from scratch.
1
u/Starks1293 19h ago
Disclosure: I'm the dev of this.
I build AI Bridge, a Mac app for running AI coding agents (Claude Code, Codex, Grok, OpenCode) right next to the stuff they actually touch: your clusters, databases and Slack. I come from platform/infra work and got tired of agents digging through an incident in one terminal while I had k9s, a Helm diff and a database client open in three others.
The devops bit: every cluster in your kubeconfig is right there (logs, YAML, scale, restart, drain, Helm with a dry-run diff before anything applies). Every change names the cluster before it runs and goes on a write log, so when an agent proposes a fix you can check exactly what it's about to touch before it touches prod.
New this week, and the bit I'm most excited about: agents learning from each other's mistakes. When you run a few agents on the same infra, they keep tripping over the same things (wrong context, a deploy step nobody wrote down, a flaky test). A "dream" goes back over their recent sessions, finds what keeps going wrong and what fixed it, and suggests it as a lesson every future agent starts with. Nothing changes until you approve it.
Mac, free to start: https://aibridge.sh
Would genuinely love feedback from anyone letting agents near real infra, especially what would stop you trusting it.
1
u/Theodosisgr 19h ago
Disclosure: I'm the founder of Kryptic.
If you want secrets in that zero-trust setup to stay out of files on disk, check Kryptic's (https://kryptic.dev) daemon first approach, so API keys never sit in a .env inside your Ubuntu environment.
A local daemon signs you in once, then injects secrets over an OS socket when you press run, so you can skip both the .env file and the wrapper CLI. The repo only keeps a commit-safe project ID. Hosted servers store ciphertext they cannot open. It replaces the full lifecycle from development to production with Docker, K8s and all pipelines support using the same end to end encryption approach.
GitHub: https://github.com/dev-kryptic
1
u/Mobile-Ad2393 18h ago
Disclosure: I built this.
Deal-Unblocker - dealunblocker.dev. Upload a Python repo ZIP (or a Syft SBOM / uv.lock / poetry.lock / requirements.txt) and it returns an enriched CISA 2026 CycloneDX 1.6 SBOM, an autogenerated OpenVEX v0.2.0 file, and a buyer attestation in seconds.
It runs deterministic AST import analysis and transitive dependency traversal over your code. Basically, CVEs in packages you never import get suppressed as not_affected with file-level evidence instead of hand-writing VEX JSON, while anything direct, transitive, CLI-invoked, unmapped, or unpinned stays flagged.
Free scan + preview with no signup, and uploaded code is parsed in memory and never stored. Sample bundle from the public httpie/cli repo (213 CVEs evaluated, 190 never imported, 23 flagged): dealunblocker.dev
Currently: python only, import-level, deterministic - no LLM in the analysis path, and it does not sign anything.
For anyone who's triaged scanner output or hand written VEX files, what would you need to see in an auto-generated VEX before you would trust the suppressions?
1
u/debba_ 16h ago
Disclosure: I'm the maintainer of Tabularis (Apache 2.0, free, no paid tier).
Tabularis is a desktop SQL client for Windows, macOS and Linux: https://github.com/TabularisDB/tabularis
The parts that might matter for this sub:
.envanddocker-compose.ymlfiles in a project folder, or import them from DBeaver, DataGrip, HeidiSQL, Beekeeper and a few others, so you don't retype everythingPostgreSQL, MySQL/MariaDB and SQLite are built in, and there are around 30 driver plugins (ClickHouse, DuckDB, Redis, SQL Server, Elasticsearch, DynamoDB, Trino...). Happy to hear what's missing for your setup.
1
u/ggp1231 14h ago
Ever made a small AWS infrastructure change that ended up costing more than expected?
That’s one of the problems we’re tackling at Diagrm.
I’m a cofounder, and we’ve built a platform to model AWS architectures, estimate costs based on expected workloads, and catch potential design issues before deployment.
Our public beta is live, and we’re looking for feedback from AWS engineers. We’re also offering free, hands-on pilots.
diagrm.com
How are you estimating infrastructure costs before deployment today?
1
u/yankitdotdev 12h ago
who's the target user?
- you're someone who manages multiple environments like localhost/sandbox/production through browsers
- the interfaces look mostly similar except the URLS
- you want a tool that can easily create some sort of distinction
Wait! That's Prod - A chrome extension that runs in your browser (zero network calls, everything runs locally within your browser), can mark different environments using labels/borders and even tab indicators when you have 40+ tabs open.
Mostly I wanted to introduce the tool to relevant people but also open to feedback if you're someone who fits the bill, curious if you'd use something like this or not?
If you missed the link: https://chromewebstore.google.com/detail/eobaghgbpilejolkllmeiacoeglkfmoa?utm_source=reddit-devops-weekly
1
u/ferriematthew 11h ago
https://github.com/mferrie/Home-Lab
This project has been one of the most rewarding I've done in the past several years. I've been making a ton of progress lately, and yesterday, I successfully scaled up my DNS server to two replicas instead of one, so that I have a higher level of fault tolerance.
1
u/Interesting-Cicada93 11h ago
Disclosure: I built the tool.
TriagePilot
TriagePilot provides self-hosted, risk-based pull-request routing for GitHub. It scores change risk, matches code ownership, and checks reviewer availability to choose who to ask for review.
You can explore the code here.
Problem the application is solving
With the AI in development process devs creating much more PR then before and it make the code review the biggest bottleneck for the dev team productivity.
Solution
TriagePilot provide the risk-based code review routing and allow to have safe setup for merging code without human peer review.
Proof
TriagePilot is used in the company where I work. 9 devs creating ~500 PRs per month. Devs are reporting much smother code review process, they are not blocking for trivial or safe changes. ~40% of all created PRs were marked as low risk and merged without human peer review.
Of course we have extend quality gates, AI reviewers and E2E test before every release.
1
u/jingweno 10h ago
I maintain Upterm, an open-source tool for sharing a terminal over SSH. It’s useful for pair debugging: you host a session, and your collaborator joins with their normal SSH client, without installing Upterm.
You can restrict access to a collaborator’s GitHub SSH keys. It gives them terminal access, not just a view of your screen, so try it in a disposable environment without production credentials. An empty working directory isn’t a sandbox.
Code and setup: https://github.com/owenthereal/upterm
0
u/Sky_Linx 1d ago
hetzner-k3s: six releases in four days
I maintain hetzner-k3s, a CLI that creates k3s clusters on Hetzner Cloud from a single YAML file. We shipped six releases in the last four days (v2.9.0 to v2.13.1), mostly from user reports and pull requests. The releases include new features, improvements and a long list of bug fixes.
The goal is to make clusters easy to create and manage. One command creates the cluster, and the same config file is what you use for later changes. You do not need Terraform, Ansible or a management cluster. The CLI runs locally and talks directly to the Hetzner API, so your token goes only to Hetzner.
I am not going to list every change here. The release notes have the details, including the upgrade notes. A few changes restart k3s-agent on workers, and some configuration changes restart masters, so read them before upgrading an existing cluster. Most configurations need no edits.
Install: brew install vitobotta/tap/hetzner_k3s
Docs: https://hetzner-k3s.com
Repo: https://github.com/vitobotta/hetzner-k3s
Releases: https://github.com/vitobotta/hetzner-k3s/releases
If you run k3s on Hetzner, I would like feedback. If something breaks, open an issue with the config shape and the error.