You've built the app.
Now let's reveal the stack.
I document how small and medium products are put together—hosting, frameworks, APIs, and integrations—inferred from public signals only. Read the write-ups to compare stacks, or book a human-led review when you need judgment on your own architecture.
$ analyze --from public-signals
project: sample-saas.dev
✓ frontend: Next.js (React)
✓ edge: Cloudflare
✓ payments: Stripe
✓ analytics: PostHog
Public-source recon
DNS, TLS, HTTP headers, and static fingerprints—no access to your repo or prod required for the public write-ups.
Stack signals
Hosting, edge, framework hints, payments, analytics, and email auth—summarized so you can see what others actually ship.
Builder communities
Projects from micro-SaaS, side projects, and build-in-public circles—the same places you’re shipping and learning.
How a review works
From something live on the web to a structured picture of how it’s wired—so you can steal ideas responsibly and pick tools with intent.
You ship & share
Founders post builds on Reddit, X, and other communities. I prioritize products that are visible and interesting—not hidden behind NDAs.
I observe in public
I collect what the internet already exposes: infrastructure, client bundles, and behavioral signals. No pentesting and no formal security audit.
You get clarity
Structured reports with inferred architecture and stack notes—plus optional deep-dive sessions when you book a paid review.
Latest public write-up: inferred stack and architecture from observable signals.
feedbackqueue.dev
April 3, 2026
4 products documented·0 stack tags surfaced·No source access · Not a security audit
Latest architecture write-ups
Each card links to a full report—stack lines are pulled from the executive summary so you can scan before you dive in.
Featured deep dives
Start with a recent report—same rigor across every project.
Architecture report
feedbackqueue.dev
External observation of publicly visible signals. Not a security audit — no active testing, no source access.
Read reportArchitecture report
h1bpulse.com
External observation of publicly visible signals. Not a security audit — no active testing, no source access.
Read reportArchitecture report
httpsornot.com
External observation of publicly visible signals. Not a security audit — no active testing, no source access.
Read reportWhat we offer
Public teardowns plus optional paid reviews—aligned with how indie builders actually ship.
Stack breakdown
Languages, frameworks, edge, DNS, payments, and analytics—organized so you can compare against your next project.
Architecture snapshots
Diagrams and narrative when the report calls for it—how requests flow and which vendors show up in the chain.
Public-source analysis
Everything is inferred from what’s already visible. I don’t need your keys, repo, or production access for the standard write-ups.
Tooling you can copy
See which combinations repeat across real launches so you can pick boring, proven stacks—or experiment on purpose.
Benefits
Learn from real launches. Skip hypotheticals—see what founders shipped under real constraints.
Choose the right stack. Match tools to the product you’re building, not to last year’s hype cycle.
Know the boundaries. These are architecture and stack observations—not pentests or compliance-ready security reviews.
Get started
Book through Buy Me a Coffee for a deeper, human-led architecture review. Browse the reports above for free public analysis.
Book an architecture reviewWhere we look
Reddit: r/micro_saas, r/entrepreneur, r/SideProject, r/buildinpublic. X: @buildinpublic, Startup Community. Questions: @builtbygio or about.