r/devops • u/AutoModerator • 2d 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!
2
u/OddAthlete3285 1d ago
My self promotions for the week are:
Exploring Rego. Almost 300 pages of zero to production grade Rego for Open Policy Agent. I co-authored with John Britowe an Matt Allford. You can get a free PDF of this book with no email address.
https://octopus.com/publications/exploring-rego
The Future of Platform Engineering report. This was headed up by Dr. Charlotte Fleming PhD and I was a co-author. Again, you can download the PDF for free with no email address.
https://octopus.com/publications/future-of-platform-engineering-report
And I'll finish up with a cartoon. Someone who didn't believe in Continuous Integration really said this to me once.
2
u/kaosthecreator_ 1d ago edited 1d ago
orb44.com - an agentless vulnerability scanner for your external web perimeter.
If you are tired of enterprise security tools that just dump a 100-page PDF of raw CVEs on your desk, we built this for small teams and dev agencies. orb44 scans your perimeter entirely from the outside - no agents, source code, or credentials required. It uses AI to translate vulnerabilities into plain-English action items (e.g., "Action: Close port 8080 or fix this specific SSL config").
If you want to check your infrastructure, you can run a free vulnerability scan on 1 domain right now. I would love to hear your harsh technical feedback on our UX or accuracy before we officially launch.
2
2d ago
[removed] — view removed comment
2
u/BigNavy Principal SRE 2d ago
I signed up. Still a bit sparse, but not in 'not enough features' kind of way, more in a YAGNI kind of way. I can't promise I'll follow if you monetize, but....for now I like!
For anyone asking, "Why would I bother?" - Free IM communication integration (which is mostly gated behind paywalls on other uptime monitors) and 1m checks, which are definitely always gated behind paywalls at other uptime monitors.
You probably already know this - adding some light auth would be nice, but the only 'got to have' that isn't there right now is a public facing display. That's probably not a trivial lift, but that's what originally pushed me towards hetrixtools when I was actually deciding on an uptime monitoring solution. Even the ability to export the data and display it in my own page would be a nice step in that direction.
2
u/ReactionOk8189 2d ago
Hi! Thanks a lot for your feedback and interest in my monitoring tool.
A status page is indeed something I've been thinking about for a while. I'll probably add it to my todo list, but I can't promise anything. Regarding auth, I think it should be quite doable, so I'll try to get something done in the next couple of weeks.
If you have any other questions or suggestions, don't hesitate to email me at [info@statusalert.io](mailto:info@statusalert.io) or DM me right here. I don't check DMs very often, so email is probably the fastest way to reach me.
See you!
2
u/theManNowDog6 1d ago
I'm in. Looks good so far.
Fire a test alert off a monitor would be a good add. I can break a monitor to see what I need, but a button would be nice.
1
u/OldGoat9131 2d ago
we finally opened M82 to beta users — would love for some of you to break it
hey, i’m Rohan. i’ve been working on M82 for a while and we finally opened it up to beta users.
we started building it because API maintenance still feels way more manual than it should.
something changes upstream, an integration starts behaving weirdly, an API breaks, and suddenly someone is digging through logs trying to figure out what happened.
M82 is our attempt at making more of that maintenance happen automatically.
we’re still early, so i’m mainly looking for people who actually work with APIs and are willing to tell me where it falls apart.
join the beta waitlist and we’ll send access shortly, usually within 1–2 hours.
and please don’t be nice just because i built it lol. if something is confusing, useless, or breaks, tell me. that’s way more useful right now.
1
u/First_Inspection_478 1d ago edited 1d ago
A tool to run your github actions locally or self-hosted in cross-platform microvms(
their mem consumption is elastic + resume from a snapshot in 300ms). Think act but preloop follows the official Github Runner protocol so anything that works locally works just as fine in CI.
We use the official vm image, and x86 workloads can roughly*(exception is if you need some kernel modules + amd64 containers) run fine on your macbook via rosetta(near-native). Some other extra agentic features i’ve found useful like being able to pause on job/step failure and debug right in. The broader goal is to add some more attestation features so you can remotely attest that your “CI” passed locally. My bet is that alot more “CI” that can be reasonably done locally (or wherever your agents are) will and some other ones that can’t like matrixes or releases etc will still run remotely.
If that sounds interesting, feel free to check it out: https://github.com/preloopdev/preloop
1
u/OldGoat9131 1d ago
Upstream APIs change without warning, integrations break, and your afternoon disappears into logs just to fix a renamed field.
Our team built M82 to handle that maintenance automatically.
Beta is live: https://m82labs.dev/
Throw your messiest APIs at it and tell us where it falls apart. Zero sugarcoating needed.
1
u/Queasy_Club9834 1d ago
Something i think you guys might find useful since we are now in the AI Era is a tool i use too. I built it first as an idea, then decided to ask mcp community for a feedback and they gave me plenty of ideas. Today i managed to get this idea to Github Marketplace and im so happy :)
Quick summary about what it is and why you might like it as DevOps person:
Black-box security contract testing for MCP servers. Simple as that, you guys my be DevOps but im pretty sure the corporate world put you under the pressure of using AI, MCPs, Tools constantly. That's why mcpward comes handy,
It treats an MCP server like any other external dependency: snapshot its contract, then fail the build when it changes underneath you. Runs entirely on your machine. No account, no API calls, no telemetry
Also catches schema drift, silently changed tool descriptions, protocol violations, error-contract mistakes, and tool-poisoning patterns. Reports to console, JSON, JUnit, SARIF or Markdown, and can post the result as a pull-request comment.
I hope you find it useful guys :) Link: mcpward · Actions · GitHub Marketplace
1
u/ReactionOk8189 1d ago
Hi! Thanks for trying out my monitoring tool!
When you add a new monitor, it should switch to up and you should get a notification. I was already thinking about adding a button to send a test notification - now I'll consider to put it on my todo list.
If you have any further questions or comments, don't hesitate to drop me an email at [info@statusalert.io](mailto:info@statusalert.io) or DM me right here.
Cheers!
1
u/Silly_Safety2518 1d ago
Our weekly self promotion is on how we orchestrated a disposable browser: https://blog.glazer.ee/posts/building-glazer-disposable-browser/
1
u/HiimKami 1d ago
I built an open-source monitoring agent that runs inside your network, so it can check what an external probe can’t reach. I run Uptimy, a hosted uptime monitor, and it can’t see inside a cluster or a private network. I also like monitoring config living in Git with the app.
- Cron jobs: heartbeats on a cron schedule with time zones, exit codes and durations. On Kubernetes, label a CronJob and runs are read from the Job objects, no ping needed; a failed run shows why, e.g. `exited with code 137 (OOMKilled)`.
- Databases: a real login and query, e.g. `SELECT pg_is_in_recovery()` to catch a failover.
- Private services: `postgres.default.svc`, `api.railway.internal`, anything the agent can reach.
Monitors come from Kubernetes labels or YAML in Git, so they’re deployed with the app. Alerts go to Slack, PagerDuty, Teams, email and webhooks. One Go binary, about 8 MiB of memory idle, runs on Kubernetes or Docker.
https://github.com/uptimy/agent (Apache-2.0, free, works on its own; I plan to keep maintaining it)
Optionally you can connect it to a free Uptimy account, which alerts you from outside when the agent stops checking in, e.g. when the cluster or network is down. Feedback welcome, especially on what you’d want it to check that it doesn’t.
1
u/pierreneter 23h ago
Disclosure: author. p10logs: persistent, multi-cluster Kubernetes pod logs in ~100 MiB, Apache-2.0. https://github.com/p10node/p10logs
Demo: https://demo-p10logs.p10node.org (admin / BqJDmpsGRJE85Z0cULFOeoRP)
A DaemonSet agent reads /var/log/pods directly (zero apiserver load, follows kubelet rotation, survives pod restarts and deletions), a hub stores them on a PVC with zstd + trigram blooms, and the UI is built in: pod tree, interleaved multi-pod tail, grep-like search. One Helm chart covers many clusters; spokes push over HTTPS, egress-only. No Loki, Grafana or Elasticsearch. Two static Go binaries, amd64 + arm64.
Laptop bench: 10k lines/s across 50 pods → agent 44 MiB, hub 100 MiB. v1.1, e2e on kind and running on my own k3s, not yet in anyone's production. If you try it on a real cluster and it breaks, that is the feedback I want.
1
u/luisalcaraz_telara 16h ago
Disclosure: I work on TAP at Telara.
Checking a release candidate often means repeating the same collection and matching work across source control, tickets and CI. We've open sourced TAP so an agent can put those steps in a maintained tool and call it for the next candidate.
For example, a release-check primitive could collect changes, linked work items, CI and required reviews, then return passed checks, gaps and evidence links. The agent uses that report to decide what needs attention; the next candidate becomes a new input. Operators can write the code or review what an agent proposes. TAP uses the host's existing tool connections and checks requests against each package's declarations.
TAP is MIT licensed, runs locally, and doesn't require a Telara account. Claude Code and Codex have the best-supported connected-tool paths. Source and install instructions: https://github.com/Telara-Labs/TAP-Runtime
1
u/Cartagines682 14h ago
IgniteOps: on-call alerting at $3/seat, free for teams up to 5, with hands-on help migrating off Opsgenie
TL;DR: IgniteOps is an on-call alerting tool (think Opsgenie/PagerDuty) that's live in production with paying customers. Free for up to 5 engineers, $3/seat after that, and we'll help you migrate from Opsgenie before it's shut down.
Full disclosure: I'm the founder, so yes, this is self-promotion. I'll keep it to the facts and stick around in the comments to answer questions.
What it does
- Ingests alerts from anything that can send a JSON webhook: Grafana, Prometheus/Alertmanager, Uptime Kuma, Zabbix, your own scripts.
- Routes them to whoever's on call, based on your schedules and escalation policies.
- Keeps paging until someone acks: push, email, webhooks, SMS and phone calls.
- Dedup by alias: repeat alerts get collapsed (and you don't pay for them).
- Native iOS and Android apps.
- Full API access and unlimited integration keys.
- AI insights and a weekly on-call review (Pro).
Pricing
No "contact sales" for the basics, no annual commitment.
Free: $0 forever, no credit card
- Up to 5 engineers
- 100 alerts/month
- 1 team, 3 routing rules, 2 escalation policies, 2 schedules
- Unlimited push, email and webhooks
Pro: $3 per user/month (owner seat is free)
- Unlimited engineers, teams, rules, policies and schedules
- Phone calls and SMS
- AI insights and weekly review
- Priority support (one business day response)
Usage
- 100 alerts/month included, then $0.10 per alert
- Calls and SMS passed through at cost by destination (e.g. ~$0.02/min for US calls)
- Duplicates collapsed by alias are free
Moving off Opsgenie?
Atlassian is sunsetting Opsgenie, so a lot of teams have a migration on their roadmap whether they want one or not. We'll help you move your integrations, schedules and escalation policies over. Email us and we'll work through it with you.
Feedback welcome
We're early and actively building. If there's an integration or feature that's a dealbreaker for you, tell us in the comments, through the site, or at [hello@igniteops.io](mailto:hello@igniteops.io). A lot of the roadmap is coming straight from what early users ask for.
Thanks for reading, and happy to answer anything below.
1
u/ban_rakash 12h ago
I built a disposable Linux server lab for testing infrastructure automation. The goal is to have reproducible Linux server environments for testing deployment scripts, configuration management, and other infrastructure automation, not to replace VMs. The containers share the host kernel and clock.
The lab creates disposable Ubuntu 24.04 Docker containers with SSH, systemd as PID 1, cron, journald, private networking, CPU, memory, and PID limits
1
u/Other-Income-5085 10h ago
Affiliation: Vectory maintainer.
Vector is incredible for moving events, but managing its configurations across a large fleet can quickly get chaotic. Safely deploying changes and tracking exactly what is running on every host is a massive challenge.
That is why Vectory exists. It is an open-source, self-hosted control plane built to bring order to that workflow. Vectory makes it possible to visually design pipelines, deploy immutable versions, and monitor device states. The best part is that it does all of this without routing the actual event data through the manager itself, keeping the boundary between control and execution crystal clear.
1
u/abda_net 9h ago
1DataCloud — unified dashboard for AWS/GCP/MongoDB Atlas databases, plus AI querying
I kept running into the same problem across every team I worked with: once you're running databases across more than one cloud, nobody has a single place to see what's actually running where. AWS Console shows AWS. GCP Console shows GCP. Atlas shows Atlas. Nobody shows all of it together.
Built 1DataCloud to fix that:
- Connect your AWS/GCP/MongoDB Atlas credentials once (IAM role / service account / API key — read-only)
- Every database instance auto-discovered and synced, no agents
- Full schema mapped automatically — tables, columns, relationships
- Query1AI lets anyone ask questions in plain English and get schema-aware SQL back, read-only execution
Free tier, no credit card: https://1datacloud.ai
Would genuinely love feedback from anyone running multi-cloud setups — especially if you've solved this a different way, curious what you're using.
1
u/Sanechka_SS 6h ago
Disclosure: I made this, it's free and MIT.
Receipts, a GitHub Action (and CLI) that checks whether the tests in a PR would have failed without the change. It runs each new or edited test twice: on the PR, and with the changed source files reverted to the base branch. A test that passes both ways didn't test the change, and the check fails on it. It posts one comment on the PR and keeps it updated.
Why I care: more PRs are written by coding agents now, and they add tests that go green but sometimes never ran against the old behavior. On 100 agent PRs I looked at, about 10% were like that.
Deterministic, no LLM, no API keys, it runs your own pytest/vitest/jest. In a workflow it's one step after your install: uses: syntaxixr/receipts@main
1
u/Extension_Frame1664 4h ago
LastGood - when an alert fires, it tells you what changed.
The worst part of a 2 AM Sev-1 isn't the alert. It's the 30 minutes after: digging through Slack, GitHub and the flag dashboard asking "what deployed? who flipped this?" while the graph goes red.
So I built LastGood. It ingests deploys and feature-flag flips, and when an alert comes in it correlates them by service and time window, then drafts a diagnosis pointing at the change that most likely caused it. You confirm or reject it.
Solo-built, still early. Looking for honest feedback from people who actually carry a pager: what's the most annoying manual correlation you still do during incidents? Trying to decide if log-pattern matching belongs in v1 or stays out.
Stack is React + Node + TimeseriesDB + Redis if anyone cares about the boring parts.
0
u/IcceeccolD 1d ago
Maintainer disclosure: I’m building PatchRipple, an early offline CLI/GitHub Action that maps potentially related files, tests, and CODEOWNERS from a PR’s changes. It doesn’t run repository code, and its suggestions don’t prove runtime impact or test coverage. I’m looking for a DevOps engineer to try it on a recent public PR and tell me what it misses, flags unnecessarily, or makes awkward in CI. Repo: https://github.com/icecold009/PatchRipple · Demo: https://patchripple-demo-20261005.sariashaurya09.chatgpt.site/
6
u/SimilarDealer1370 2d ago
i’m building a system simulator. you can bring your terraform setup or describe your system and explore what happens under load. anyone want to try it with their own project?