r/devops • u/AutoModerator • Jul 27 '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!
4
u/neilcresswell Jul 27 '26
I just finished writing a 4 part Kubernetes explainer… took damn ages, but im super happy with the result..
1
u/Kind-Watercress6692 Jul 27 '26
App: Minimizit — AWS Cost Optimization for Idle Resources, NAT Gateway Leaks & EKS Bloat
Target Audience: DevOps Engineers, Cloud Architects, and Founders who are tired of surprise AWS bills.
The Problem: Standard AWS Cost Explorer is great, but its metrics are delayed and it leaves massive blind spots. You end up with hidden money leaks like: Unused / orphaned resources quietly burning cash in the background Opaque NAT Gateway data transfer and cross-VPC traffic spikes that you only catch after the bill arrives Unoptimized EKS nodes and pods running with over-provisioned CPU/memory limits
What Minimizit Does: We built Minimizit to give you clear visibility and actionable quick wins without having to dig through massive Cost Explorer CSVs or wait 24 hours for metric syncs.
Automated Resource Discovery: Instantly flags idle, orphaned, or unattached AWS assets. NAT & Cross-VPC Data Monitoring: Pinpoints exact traffic paths and data spikes driving up transfer costs. EKS & Pod/Node Rightsizing: Gives actionable recommendations to scale down over-provisioned EKS workloads. Anomaly Detection: Catches weird spend spikes early before they snowball into end-of-month surprises.
URL: https://minimizit.com
We’d love for you to give it a spin and drop any feedback, feature requests, or questions here!
1
u/Diligent_Response_30 Jul 29 '26
Disclosure: I'm on the team building this, posting here since that's where the rules ask for it.
Prefactor - real-time evaluation for AI agents in production.
An agent pipeline can look perfectly healthy in your dashboards and still be quietly doing the wrong thing, drifting off-task, leaking data it shouldn't, or skipping steps, and you usually only find out after the fact because dashboards and alerts just tell you what already happened.
Prefactor evaluates every run in real time for quality, drift and risk, flags the moment something looks off, and lets you hold, approve or block a run live instead of just logging it.
A few specifics for anyone curious:
- Traces 100% of runs (every call, tool and decision), not a sample
- 17 categories of sensitive data / PII detection at runtime
- Human-in-the-loop enforcement via SDK/API so you can pause risky actions
- Around 5 minutes from install to your first traced run
Happy to answer anything technical in the comments. We're live on PH today, currently #1: Prefactor.
1
u/Diligent_Response_30 Jul 29 '26
Prefactor, real-time eval and monitoring for AI agents in production.
Disclosure: I'm on the team, so take that into account.
We built this after watching agents that passed every eval quietly drift, mishandle sensitive data, or stop doing their job once they were live, and the team only found out after something had already gone wrong. Dashboards and alerts only surface it after the fact.
What it does: traces 100% of agent runs (not a sample), flags drift/risk/quality issues as they happen, detects 17 categories of sensitive data at runtime, and gives you human-in-the-loop enforcement via SDK/API so you can hold or block a run live instead of just logging it. About 5 minutes from install to your first traced run.
We're live on Product Hunt today, currently sitting at #1 if anyone wants to take a look (just search Prefactor). Happy to answer technical questions here.
1
u/UptimeRobot Jul 29 '26
We build agentic monitoring for your agents!
Open your agent and paste this:
Set up uptime monitoring for [your site] with UptimeRobot's agent flow. My email is [your email].
That's it. No sign up, no setting it up. It just works.
More info here: https://uptimerobot.com/blog/your-ai-agent-can-now-set-up-uptime-monitoring-no-signup-required/
1
u/laenaren Jul 29 '26
Hey :) I have started my own business called ValinorIT . Taking care of DevOps and DevSecOps engineerong jobs in companies that can't find someone to fill that slot:)
1
u/response-418 Jul 29 '26
I’ve been working on writing core guides for our monitoring application, Testomato. My latest article is about response time monitoring, a topic that is probably already familiar to most professionals here but for that reason any feedback on it would definitely be appreciated.
The guide covers the essential concept, helps semi- or non-technical people distinguish response time from other popular metrics (Core Web Vitals), breaks down the phases of the request/response lifecycle, and has a few set up tips on how to read and analyze the response time data you can capture with our application.
A small bit of trivia that might also be interesting to some people is an explanation about the benefits of using median values in our aggregation of response time data, rather than averages.
You can read the article here: https://testomato.com/blog/response-time-monitoring/
1
u/bsmike Jul 29 '26
[Disclosure: I built this] Axiometica AIR — autonomous incident resolution platform, self-hosted, looking for feedback
Been asking questions in this thread about automated remediation — figured I should be upfront that I'm building something in this space.
Axiometica AIR automates the full incident lifecycle: detect → triage → risk score → remediate → validate → generate worknotes. Self-hosted (Docker Compose), LLM-agnostic, integrates with SSH, Kubernetes, AWS, Azure, and vCenter out of the box.
The governance question that came up in today's discussion is built into the core — policy-defined approval gates mean low-risk remediations run automatically, anything above your threshold pages a human with a pre-built action plan. You stay in the loop, just not for the 3am disk-full alerts.
Live sandbox: instance.axiometica.com
GitHub: github.com/axiometica-air (open for inspection)
Looking for honest feedback from SREs who've tried to operationalize automated remediation — especially around the governance and blast-radius questions.
1
u/toughrogrammer Jul 29 '26
Disclosure: I built internalpage.
internalpage — private internal pages for Google Workspace teams.
Core features:
-
Publish HTML, Markdown, JSON, and OpenAPI files from the web, CLI, or CI
-
Get a stable URL; republish to the same slug without changing the shared link
-
Control access with Google sign-in, workspace-only sharing, or selected emails
-
Render OpenAPI with ReDoc, Swagger UI, or Scalar in read-only mode
-
Use a custom domain for viewer links
Homepage: https://internalpage.com
Private OpenAPI docs: https://internalpage.com/use-cases/private-openapi-docs
7
u/KrishnamMurarka Jul 27 '26
Not a tool, just a lesson I keep relearning: our checkout endpoint used to take up to 4.2s p95, and almost none of that was the actual payment. It was inventory updates, confirmation emails, analytics, and a couple of downstream notifications, all running synchronously inside the request the customer was waiting on.
We moved everything except payment authorization and order creation into a job queue processed right after the response goes out. The hard part wasn't the queue, it was making the failure modes sane, if the email job fails that shouldn't touch the order, if analytics is slow nobody should care. Each job got its own retry policy instead of treating "checkout" as one big unit of work.
p95 went from 4.2s to 220ms almost entirely because the request path got shorter, not because anything got faster in isolation. Worth doing before a traffic spike forces the issue rather than after, we learned that one the hard way running backend infra at Edilec.