{"slug": "alloy", "name": "Alloy", "category": "observability", "category_name": "Monitoring and analytics", "description": "", "recommenders": 3, "commenters": 5, "warners": 1, "score": 2.158, "rising": 1.67, "first": "2026-01-17", "latest": "2026-10-23", "why": "Credit goes to agentic coding tools for making it a reality.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 1, "compare": 1, "warn": 1}, "spark": [0, 0, 0, 0, 0, 1, 0, 0, 0, 1, 0, 1], "listed": true, "loved": [], "caveat": "", "short_quote": "Credit goes to agentic coding tools for making it a reality.", "icon": true, "domain": "alloytools.org", "github_repo": null, "official_url": "https://alloytools.org", "pricing": "", "aliases": ["Alloy"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 803276609, "item_id": 50204788, "url": "https://news.ycombinator.com/item?id=50204788", "by": "svcrunch", "date": "2026-10-23", "stance": "recommend", "quote": "Credit goes to agentic coding tools for making it a reality.", "excerpt": "Along these lines, we used Codex to collaboratively build an alloy model for verifying the authorization model of GoodMem. After building the model, we implemented the code based on it, and, while there could be a gap in the translation process, several hours of red-teaming the server (w/attacker source code access) to try and produce a privilege escalation attack using GLM 5.3 failed. Alloy is a tool I tried to lear", "context": "", "use_case": "formal verification of authorization model", "switched_from": "", "story": "LLMs are making formal software verification feasible at a much larger scale"}, {"id": 790428836, "item_id": 49401802, "url": "https://news.ycombinator.com/item?id=49401802", "by": "losingthefight", "date": "2026-08-22", "stance": "recommend", "quote": "I use an Alloy sidecar taking in OTEL and scraping logs.feom my Go services", "excerpt": "I run OSS Grafana with Loki, Prometheus, and Tempo. I use an Alloy sidecar taking in OTEL and scraping logs.feom my Go services and selfhost the stack. Once you need to scale it gets a bit more complicated but it's all still OSS. The biggest challenge I have is that each data source needs it's own query language, which DD and the like don't. That's why at my day job they went with DD despite the costs. Still OTEL but", "context": "", "use_case": "collecting telemetry and logs", "switched_from": "", "story": "OTel isn\u2019t going well"}, {"id": 767336054, "item_id": 47958503, "url": "https://news.ycombinator.com/item?id=47958503", "by": "faangguyindia", "date": "2026-04-29", "stance": "recommend", "quote": "alloy picks up log and drops it graphana which has all alerts there", "excerpt": "These days I just use a few languages: 1. Go, when I first saw code I wrote almost a decade ago still compiles and runs in Go, I decided to use Go for everything. There were some initial troubles when I started using it a decade ago, but now it's painless. 2. Haskell, I use it for DSL and state machines. 3. Bash for all deployment scripts and everything. 4. TypeScript, well for the frontend. Lately, I\u2019ve been using G", "context": "", "use_case": "log collection", "switched_from": "", "story": "Functional Programmers need to take a look at Zig"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 793775552, "item_id": 49610972, "url": "https://news.ycombinator.com/item?id=49610972", "by": "lmeyerov", "date": "2026-09-08", "stance": "warn", "quote": "alloy for gfql fell on its face relative to fuzzing, even with guidance.", "excerpt": "Wonderful data point! It's been interesting investing into different classic verification & testing methods for gfql (CPU/GPU graph queries on dataframes) and Louie (agentic investigation harness) over the last couple of years with different model & harness generations. The ones below are fewer but more longitudinal efforts compared to the shallower ones Dan worked through, and seem largely consistent: Overall, my ta", "context": "builds gfql and Louie", "use_case": "formal verification of graph query engine", "switched_from": "", "story": "How well do agents use test/verification techniques?"}]}], "who": [], "tags": [], "use_cases": ["log collection", "formal verification of authorization model", "formal verification of graph query engine", "collecting telemetry and logs", "model checking query/graph space"], "compared": [{"slug": "loki", "name": "Loki", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "prometheus", "name": "Prometheus", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "grafana", "name": "Grafana", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "docker", "name": "Docker", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 787308688, "item_id": 49206793, "url": "https://news.ycombinator.com/item?id=49206793", "by": "simonkubica", "date": "2026-08-06", "stance": "recommend", "quote": "I'm the founder of Alloy (YC W23) and we recently pivoted into Cloud Agents", "excerpt": "Lots of activity in this space right now, I'm the founder of Alloy (YC W23) and we recently pivoted into Cloud Agents (https://alloy.app/cloud-agents). My honest take is that Cursor is leading, but their video / desktop stream isn't really practical for frontend development. Us and the the other YC startups innovating in the space and trying to push this forward with running your frontend directly so it feels more li", "context": "founder", "use_case": "cloud agents for frontend development", "switched_from": "", "story": "Ask HN: What cloud agents do you use?"}], "threads": [{"url": "https://news.ycombinator.com/item?id=50202217", "title": "LLMs are making formal software verification feasible at a much larger scale", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49605246", "title": "How well do agents use test/verification techniques?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49391553", "title": "OTel isn\u2019t going well", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49209921", "title": "The web server deployment model breaks at hobby scale", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49145307", "title": "Ask HN: What cloud agents do you use?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47957624", "title": "Functional Programmers need to take a look at Zig", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"compare": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"neutral": 1, "recommend": 1}, "2026-09": {"warn": 1}, "2026-10": {"recommend": 1}}, "quotes": [{"id": 803276609, "item_id": 50204788, "url": "https://news.ycombinator.com/item?id=50204788", "by": "svcrunch", "date": "2026-10-23", "stance": "recommend", "quote": "Credit goes to agentic coding tools for making it a reality.", "excerpt": "Along these lines, we used Codex to collaboratively build an alloy model for verifying the authorization model of GoodMem. After building the model, we implemented the code based on it, and, while there could be a gap in the translation process, several hours of red-teaming the server (w/attacker source code access) to try and produce a privilege escalation attack using GLM 5.3 failed. Alloy is a tool I tried to lear", "context": "", "use_case": "formal verification of authorization model", "switched_from": "", "story": "LLMs are making formal software verification feasible at a much larger scale"}, {"id": 793775552, "item_id": 49610972, "url": "https://news.ycombinator.com/item?id=49610972", "by": "lmeyerov", "date": "2026-09-08", "stance": "warn", "quote": "alloy for gfql fell on its face relative to fuzzing, even with guidance.", "excerpt": "Wonderful data point! It's been interesting investing into different classic verification & testing methods for gfql (CPU/GPU graph queries on dataframes) and Louie (agentic investigation harness) over the last couple of years with different model & harness generations. The ones below are fewer but more longitudinal efforts compared to the shallower ones Dan worked through, and seem largely consistent: Overall, my ta", "context": "builds gfql and Louie", "use_case": "formal verification of graph query engine", "switched_from": "", "story": "How well do agents use test/verification techniques?"}, {"id": 790428836, "item_id": 49401802, "url": "https://news.ycombinator.com/item?id=49401802", "by": "losingthefight", "date": "2026-08-22", "stance": "recommend", "quote": "I use an Alloy sidecar taking in OTEL and scraping logs.feom my Go services", "excerpt": "I run OSS Grafana with Loki, Prometheus, and Tempo. I use an Alloy sidecar taking in OTEL and scraping logs.feom my Go services and selfhost the stack. Once you need to scale it gets a bit more complicated but it's all still OSS. The biggest challenge I have is that each data source needs it's own query language, which DD and the like don't. That's why at my day job they went with DD despite the costs. Still OTEL but", "context": "", "use_case": "collecting telemetry and logs", "switched_from": "", "story": "OTel isn\u2019t going well"}, {"id": 787382949, "item_id": 49211434, "url": "https://news.ycombinator.com/item?id=49211434", "by": "SlavikCA", "date": "2026-08-07", "stance": "neutral", "quote": "My Alloy & Loki logging system got loaded heavily.", "excerpt": "I have 5Gbps fiber at home. LAN is mostly 10Gbps. I'm hosting few hobbyist public websites. One is the library of hymns, songs, ... - mostly PDF, MP3, MIDI. OpnSense router -> Traefik -> Docker container. That Docker container runs on NAS, which is connected via 1Gbps port. Suddenly, last week I started to get over 1000 RPS. Was it scanner, parser, crawler, DDOS? I can't tell, as user agent was default Mac OS. It was", "context": "", "use_case": "log collection", "switched_from": "", "story": "The web server deployment model breaks at hobby scale"}, {"id": 767336054, "item_id": 47958503, "url": "https://news.ycombinator.com/item?id=47958503", "by": "faangguyindia", "date": "2026-04-29", "stance": "recommend", "quote": "alloy picks up log and drops it graphana which has all alerts there", "excerpt": "These days I just use a few languages: 1. Go, when I first saw code I wrote almost a decade ago still compiles and runs in Go, I decided to use Go for everything. There were some initial troubles when I started using it a decade ago, but now it's painless. 2. Haskell, I use it for DSL and state machines. 3. Bash for all deployment scripts and everything. 4. TypeScript, well for the frontend. Lately, I\u2019ve been using G", "context": "", "use_case": "log collection", "switched_from": "", "story": "Functional Programmers need to take a look at Zig"}, {"id": 746534033, "item_id": 46658377, "url": "https://news.ycombinator.com/item?id=46658377", "by": "lmeyerov", "date": "2026-01-17", "stance": "compare", "quote": "Alloy hasn't really found anything.", "excerpt": "I've had an interesting comparative experience so far using Alloy, which is a 'simpler' formal method approach that you can think of as smarter exhaustive fuzzing for your properties of interest. We have been building GFQL, an open source graph query language that can run at the compute tier seperate from whatever existing storage system (splunk, SQL, cs , ..), making graphs easy for interactive notebooks/dashboards/", "context": "building GFQL", "use_case": "model checking query/graph space", "switched_from": "", "story": "Lies, Damned Lies and Proofs: Formal Methods Are Not Slopless"}]}