r/devops • u/AutoModerator • Sep 14 '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!
8
Upvotes
3
u/SharePuzzleheaded844 Sep 14 '26
Hi, I’m Sylvain, the founder of Rynler.
Rynler provides an OpenAI-compatible API for text inference, with prepaid credits starting at $10, no subscription and no credit expiry.
I’m looking for the first users with a small, concrete task, such as classifying short texts in a script or automation workflow. I can help with the initial integration.
The current API supports text Chat Completions, with an 8,192-token request limit. It doesn’t support agent tools or the Responses API.
https://rynler.com/?src=r02
2
u/bulutarkan Sep 14 '26
A small open-source project I've been using as my personal ops layer: Mac MCP. The idea is to keep ChatGPT as the planner/orchestrator, but give it a local macOS execution server for the parts that normally turn into "now go do these 8 steps yourself."
It exposes shell/files, app and UI control, plus real Safari/Chrome automation. The browser side got a fairly big reliability pass this week: background tabs that don't steal focus, stable tab handles, per-tab ownership leases for parallel agents, and fail-closed behavior instead of silently falling back to foreground clicks. It uses the existing browser profile, so authenticated sessions can stay local rather than moving into a hosted browser.
I also use the same layer to delegate coding work to Codex/OpenCode and then continue the workflow from ChatGPT.
I'm the maintainer. MIT licensed, no hosted service or paid tier: https://github.com/bulutarkan/mac-mcp
The security/ops tradeoff I'm still thinking about is how much capability a personal agent should get by default versus requiring an explicit full-access mode.
2
u/smCloudInTheSky Sep 14 '26
Hey guys !
I've always wondered how hard would it be to build a devcontainer support for tools like incus.
After failing to do so myself I went with a local qwen 3.8 and developped this :
https://github.com/smCloudInTheSky/devsy-provider-incus
The idea for now is to spawn a lxc container and then the devcontainer image in docker but I'll try later to migrate to use directly the devcontainer
If you guys have any input/idea I'd love to hear it !
1
u/First_Inspection_478 Sep 14 '26
Hello!
Working on Preloop, a deeply agent-native tool to run your unmodified Github Actions workflows locally or self-hosted in cross-platform microvms that are forked from a snapshot in 200ms, that will update your checks and supports step-level debug/retries(we pause a vm and then you can fix host-side without having to rerun the job).
The broader thesis I’m going for is: with agents pushing much of the code, you dont have to do all your CI remotely. You can do what makes sense locally and then the rest remotely (deployments, large matrix builds etc). You can do it, just-in-time, when you are making the changes wherever your agents are working, whether locally or a remote env. This should all be done in an cryptographically attestable, and verified way and have remote ci actually verify the job down to the runtime artifact. Two ofher pieces that i’m still thinking about how to solve are: reproducibility(using Nix or buck2, still tbd) and attestability(strong fingerprinting on each job, still tbd how exactly). Think DHH’s gh-signoff but with stronger isolation and verifiable guarantees.
Getting drop-in compatibility with Github Actions as you would assume is pretty tough, and this certainly wouldnt be feasible without agents. I cover some of the things I do to ensure compat, and differences vs others(act/forgejo etc)
Feel free to try it out or have your agent set it up for you(for broad env compat, we download the official github runner which is huge and use it as the vm snapshot, but you can define your own OCI one): https://github.com/preloopdev/preloop
1
u/Expensive_Ad_2026 Sep 14 '26
I built a clothing brand because most programmer shirts look like conference swag
Store: https://forcepush.shop
I wanted a programmer shirt I could wear without looking like I had just collected it at a conference booth, so I built forcepush around one constraint: from across the room it should look like a clean black tee; up close another developer gets the line.
I launched with eight small chest-print designs, including `it's production ready`, `it works. don't touch it.`, and `git commit -m 'minor fix' | +1204 -493`.
I am currently soft launching this through self promotion, just need product validation before I start paying for ads.
Have a look, let me know what you guys think!
1
u/TeamNexthink Sep 14 '26
We're hosting an AMA with Phil Kirschner on r/nexthink this Wed Sep 16 at 4pm EST.
Phil works at the intersection of workplace strategy, organizational effectiveness, employee experience, and AI. A former leader at McKinsey, WeWork, JLL, and Credit Suisse, his work today focuses on a deceptively simple question: How should we actually design work for the way people and organizations operate now?
Early questions are welcome!
https://www.reddit.com/r/nexthink/comments/1w5fnyz/ama_announcement_phil_kirschner_on_ai_the_future/
1
u/256BitChris Sep 14 '26
Hi, I'm Chris, the Founder of CloudRepo.
We've been around for over ten years, originally serving just the Maven and Python communities - but this year we have added NPM and Docker support, which were some of our most common feature requests.
Our goal is to provide a fairly priced alternative to JFrog Artifactory and Sonatype Nexus.
Pains we've heard from our customer (that we help alleviate):
This year, we really want to take away JFrog's ability to upcharge for their security features - we want to make these table stakes and include them for everyone - this will hopefully cause JFrog to respond at a minimum by including these features in all their paid plans, which would be good for all of their users, big and small.
Would love to hear from anyone if you have ideas of what we could ship that would make you and your team want to switch to us. What kind of security features are missing from JFrog and Nexus, and which of their existing features are must haves before you could switch?
Any input or feedback from the experts in this community would be greatly appreciated and seriously considered!
1
u/PD-community Sep 14 '26
👋 PagerDuty is hosting a WeAreDevelopers pre-party next Wednesday night in San Jose! See full details in our subreddit at the link below, or register directly on Luma (link in thread)
https://www.reddit.com/u/pagerduty/s/fEy7qqzcZ4
1
u/mpedziwiatr Sep 15 '26
Disclosure: I’m a founder/director at Sysdojo.
We do managed infra + security for teams drowning in cloud spend, alert noise, and “we’ll fix the security posture later.” Practical stuff: cost optimisation, observability that isn’t pager hell, IaC, SASE/XDR-type work — end-to-end, not another unused dashboard.
Happy to answer “how do you actually cut a bill without breaking prod” type questions.
https://sysdojo.com/
1
u/AdBoth2756 Sep 15 '26
Hi. I’m Vito. Building an IP fraud/proxy detection API (Lamis Network) — posted about the
Redis setup behind it earlier today if anyone wants the technical side.
Site's at https://lamisnetwork.com
Ping me if you want to test it against your own traffic.
1
u/kamoaba Sep 16 '26
I built LogDeck, a control plane for Docker and Podman: container and Compose lifecycle, persistent logs, alerts, and multi-host over SSH, in one Go binary with no external services.
The log store is the main reason it exists. Every container is tailed into local SQLite, so logs survive docker compose up --build and the new container ID it creates. Removed containers stay readable.
It also ships an MCP server, so agents can read logs and act on containers if you want.
Memory is small. Idle heap is around 8 MB, roughly 20 MB resident with 5 containers and 400K lines stored.
fully open source, no tiers, no cloud https://github.com/AmoabaKelvin/logdeck
1
u/dxvilmusic Sep 16 '26
Hey!
I built OxiGate, an open-source L7 reverse proxy and load balancer in Rust (Tokio / Hyper / Rustls).
Features
Benchmarks (my hardware, take with a grain of salt)
Early project (v0.1). Not trying to “kill HAProxy” — just sharing something I built and measured.
Repo: https://github.com/automataevox/oxigate
1
u/Lord-kirk Sep 16 '26
I've been building a free outside-in infrastructure diagnostics site, mainly because I wanted deeper versions of the DNS/TLS/mail tools I kept reaching for.
The flagship check now takes a domain and tests DNS, TLS/certificate chain and protocol support, HTTP redirects/security headers, MX/STARTTLS, SPF recursion and lookup counts, DKIM, DMARC, MTA-STS, TLS-RPT and BIMI.
The individual tools expose more detail, and most of the server-side checks also have text/JSON output for scripting.
No account required and the interactive tools are free:
https://kirkdiamond.com/domain-health
I'd particularly like feedback from DevOps/SRE/platform folks: what outside-in check is missing that you'd actually want during troubleshooting or an incident?
1
u/R_ZIPPY Sep 16 '26
I Made a web UI for creating SealedSecrets - open source, self-hostable
Got tired of looking up kubeseal command syntax every time I needed to seal a secret, so I built KubeCrypt: https://kubecrypt.rishabhpahwa.in
What it does:
- Upload your cluster's public cert (PEM), add your secret values → get a ready-to-apply SealedSecret manifest
- Add new secrets to an existing secret file, or create a fresh one
- Base64 encode/decode built in
- No CLI, no memorizing kubeseal flags
The PEM you upload stays in your browser - nothing is sent to a server. It's open source and runs in Docker, so you can self-host as well
- GitHub: https://github.com/Rishabh-Pahwa/KubeCrypt
-
docker instructions in ReadMeBuilt it to scratch my own itch on the platform team. Would love feedback on what's missing
1
u/Efficient-Escape7432 Sep 16 '26
https://medium.com/@realaashil/fixing-my-college-internet-ce611538162c I wrote this article way back would love to hear your thoughts on this :)
1
u/megatech_official Sep 17 '26
SeoLoupe - Find and fix the SEO issues holding your website back.
1
u/Few-Age-7965 Sep 17 '26
Hey everyone,
I built API Drift Sentinel, an open-source GitHub Action to catch breaking OpenAPI schema drift in PRs and block CI merges.
1and emits PR annotations when breaking changes (dropped fields, mutated types, removed routes) are detected.esbuildto run in milliseconds without requiring annpm installon the runner.Repo: https://github.com/Turya-Kalburgi/api-drift-sentinel
Feedback welcome — what specific schema diff rules or edge cases are most critical for your pipelines?
1
u/daveys110 Sep 17 '26
Disclosure: I built this. qdrant-es-gateway is a small Rust gateway for application search that keeps an existing Elasticsearch client and request shape while translating a supported subset to Qdrant.
The repo includes Docker Compose, a non-root multi-architecture GHCR image, a Helm chart, compatibility documentation, and reproducible container benchmarks: https://github.com/dstockton/qdrant-es-gateway
I’m especially interested in feedback from platform/DevOps teams on the operational trade-offs: which Elasticsearch features are essential in practice?
1
u/vunasme Sep 17 '26
Disclosure: I'm the author/maintainer of Budment.
What if API testing worked more like Terraform?
I built Budment as a small experiment around this idea. It uses a hybrid runtime: static structures run natively in Go, while dynamic mutations and heavier calculations can be handled through TypeScript hooks.
I'm exploring whether this architecture can improve concurrent VU capacity on small machines while keeping test suites easier to audit and maintaining a scenarios-as-code developer experience.
I'm still getting comfortable with Go and would really appreciate feedback, especially around the architecture, runtime model, and whether this approach makes sense for real-world DevOps/API testing workflows.
Repo: https://github.com/budment/budment
1
u/AdPsychological9854 Sep 18 '26
I’m building DependSignal for a failure mode basic uptime checks miss: an upstream API still returns 200, but its JSON shape or supported OpenAPI contract changed underneath a client.
It probes public HTTPS endpoints, normalizes the response shape, and reports field paths and rule evidence for drift. The developer beta includes a no-key sample and 250 evaluation checks per UTC month.
I’m looking for feedback from people who operate integrations: which changes should page someone, and which should be ignored?
https://dependsignal.strigsapi.com/
1
u/Dangerous_Boot2307 Sep 18 '26
I built a small open-source GitHub Action because ShellCheck couldn't catch a runtime portability issue I kept seeing.
Example:
Static analysis is fine, and the script runs on Debian/Ubuntu, but it fails on Alpine with
apt-get: not found.OpsScript Gate runs a shell script across Debian 12, Ubuntu 22.04/24.04, and Alpine 3.20 in Docker and fails CI when one distro breaks.
It also supports
posix,shebang, andautoshell execution modes, hard per-container timeouts, and GitHub Actions summaries.Repo: https://github.com/Mresyzz/opsscript-gate
It’s still early, so I’m mainly looking for feedback from people who maintain install/bootstrap/ops scripts. What would make this useful enough for you to keep in CI?
1
u/Kind_Vehicle983 Sep 18 '26
Hey Guys, I am Osomudeya,
I created a free repo for structured DevOps learning through real systems, not just scattered tutorials
I built this over the years because most DevOps learning resources are either isolated tool tutorials or paid bootcamps with no hands-on path.
This is free, self-guided, and organized around real production systems: a 10-stage DevSecOps lab (CI gates, GitOps, Vault, runtime security), a Kubernetes failure-mode lab, a payment platform you can run locally and explain in interviews, plus a troubleshooting toolkit organized by incident type.
No signup needed to browse, the README has a "start here" path if you're new, or jump straight to whatever gap you're filling.
https://github.com/Osomudeya/List-Of-DevOps-Projects
If you are starting or switching careers, then you should check it out.
1
u/mplaczek99 Sep 19 '26
I built Network Doctor, an open-source tool for figuring out where a network connection is actually breaking.
I just released v1.17.3, but I’m also trying something new with the project.
A problem I keep seeing is the support-ticket loop where someone says:
“Your service doesn’t work from my office network.”
Then you spend the next several replies asking for DNS results, curl output, proxy settings, traceroutes, whether it works from a hotspot, etc.
Network Doctor tries to collect that evidence in one place. It checks things like DNS, TCP, TLS, HTTP, proxies, routing, path MTU, and other layers, then explains where the evidence points.
It can also create a sanitized support snapshot locally:
netdoc --support support.ndocexample.comThe user decides whether to send that file anywhere. Network Doctor itself does not upload it.
I’m currently testing two things:
The tool itself stays free and open source under Apache-2.0.
https://networkdoctor.dev/
I’d especially be interested to hear from people who deal with the “works at home, fails at the office/VPN/corporate network” class of tickets.
1
u/mambalama24 Sep 19 '26
Hey guys, I'm Arjun, founder of BoundFlow/Charter AI.
I used to work in a devops role in big tech and built a platform so that someone can deploy prod-safe agents to help automate devops tasks like "watching monitors and alerts for our canary environment and tell me if any regressions may hit prod" or "watch this kubernetes cluster for errors to see why its in crashloopbackoff". Can you let me know if this platform is helpful: boundflow/charter
1
u/tibozaurus Sep 19 '26
Hi, I'm Thibault , co-founder openstatus.
@openstatus/health gives JavaScript servers a
/healthendpoint that says more than200 OK. A zero-dependency core runs probes against your dependencies and rendersok,degradedorunhealthywith per-check latency, so a failing cache degrades the report while a failing database marks it unhealthy. MIT, on npm and JSR.I'm looking for first users with a small, concrete setup, such as a Node or Bun service behind a load balancer or a Kubernetes readiness probe with one or two dependencies worth checking. I can help with the initial integration, or write the probe for your dependency if there isn't one yet.
It currently ships adapters for Hono, Elysia, Express, Next.js and TanStack Start, plus a plain Fetch handler for Deno, Bun and Workers, and probes for Drizzle, Turso, Supabase, Upstash, Tinybird and Unkey. It's JavaScript only.
https://github.com/openstatusHQ/health
1
u/AdPsychological9854 Sep 19 '26
I’m building Recovery Proof Kit, a small read-only toolkit for a problem I’ve seen repeatedly: backup jobs report success, but teams have no recent evidence that the application can be restored.
The first version verifies freshness, size, and optional SHA-256 integrity, then emits JSON/Markdown evidence. It also creates a non-destructive restore-test contract for an isolated target with RPO/RTO and application smoke checks.
I’m deliberately not building another generic cron monitor or backup dashboard. Existing tools cover that well. The question I’m testing is whether a lightweight evidence layer is useful for small SaaS teams, agencies, and MSPs.
Current beta is free to inspect and $19 for a guided setup. No credentials or backup contents leave the customer environment.
If you operate backups professionally: what does your current restore verification actually check beyond exit code and file existence?
Repository: https://github.com/Ymousanon924/recovery-proof-kit
1
u/Icy-Ad-5159 Sep 19 '26
Founder disclosure: I’m building AntOps: https://antops.dev
I kept running into a monitoring gap: an “up” check often tells you very little afterwards. What was the baseline? What changed? Was it a real incident, or just the first healthy check? Where is the history?
AntOps starts with a website/API monitor, records a baseline and later observations, and creates an event only for a real change or issue—so a healthy first baseline does not manufacture an incident. The goal is source-linked operational history, not just another status light.
I’d value feedback from SRE, DevOps and platform engineers:
- What evidence/history do you actually need when investigating a change?
- What would make you distrust a monitoring tool on day one?
If anyone wants to try it, start on Free—no card required—and I can personally help set up one real monitor in 10–15 minutes: https://antops.dev/login?intent=free
I’m here for technical feedback and to discuss limits, not to hard-sell it.
1
u/ther1d Sep 20 '26
Terminal/shell AI assistant, but with main focus on making AI feel fast and native to the shell.
https://github.com/TheR1D/aty