Stacktora
Define once, run anywhere.
7 followers
Define once, run anywhere.
7 followers
This is developer onboarding infrastructure. The end of configuration drift for every engineer — it’s over. Stacktora isn't a docker-compose generator. It's the workflow that keeps every developer's environment identical, current, and runnable — from the first clone to the hundredth hire. Define your stack — languages, databases, services — and Stacktora generates a production-ready, runnable bootstrap: docker-compose, Makefile, CI, and 15+ files. Clone, to running in minutes.
1/ Shipped every item on the roadmap tonight, and found 7 real bugs along the way. Long one — worth the read if you build alone too.
Zero VCs. Infinite spite. Still shipping. 🧵
2/ Started by actually using Compliance on something real instead of demo repos.
Built a small real project from scratch (pingcheck, a URL uptime monitor) using my own CLI to scaffold it. Real tests. Real CI. Real branch protection. Pushed, wired up, verified live.
Dogfooding your own tool on a throwaway demo isn't dogfooding. This was.
3/ That real usage immediately found a real bug: the Compliance dashboard's own copy-paste CI snippet had the wrong input name. Told everyone to pass token: when the action actually expects stacktora-token:.
The action silently ignores inputs it doesn't recognize instead of failing — so CI ran green while quietly reporting nothing. Anyone who copied that snippet before today was silently broken and had no way to know.
Fixed at the source. Confirmed by fetching the real action.yml directly, not assuming.
4/ Shipped Notifications — Slack + email the moment a repo that was passing starts failing. Not on every failing run after (spam), not on a repo's first-ever report (nothing to compare yet).
Hardened it defensively too: every new query degrades to safe defaults if the migration hasn't run yet, since this fetch sits inside the dashboard's one big data-load call. One migration-ordering mistake here and the WHOLE dashboard breaks, not just this section.
5/ Shipped stacktora mcp — an actual MCP server, built into the CLI you already have. No new service, no new hosting.
10 tools. Read, scaffold, audit, recipes — full parity with the CLI. Published to npm.
The unglamorous detail: stdout IS the MCP transport. Wire the existing print-oriented commands straight in and you corrupt your own protocol the first time anything logs. Every tool is a fresh function returning data instead.
6/ Tonight I actually tested it with a live agent instead of just my own sandbox.
Real find: it correctly refused to guess which project I meant when the path was ambiguous, found the CLI installed via npm on its own, ran stacktora check, escalated to stacktora plan on its own initiative to get the real diff instead of stopping at a summary.
Correctly reported: only drift was a stale timestamp field. Zero actual config drift. That's exactly right, and it said so instead of alarming me over nothing.
7/ Closed 4 real gaps in the recipe catalog: Auth/SSO starter, GraphQL API, LLM Gateway/Proxy, Job Queue & Scheduler. Things every recipe before this assumed you'd build yourself.
Validated every one against the real live schema. Then actually ran them through the real generator — which caught bug #7: two of the four don't need custom env vars (totally normal, schema-valid case), and generating either one crashed the engine outright. config.env has always been optional. Nothing ever guarded for its absence.
Fixed at the source, not patched around.
8/ Pushed the site's own codebase to a real Git repo for the first time tonight too. No more living only on the server.
Small thing. Overdue thing. Done thing.
9/ Bootstrapped. Solo. No committee greenlighting any of this.
Just a long night of building the thing, finding what's actually broken, and fixing it instead of shipping around it.
stacktora.com
#buildinpublic #solofounder #bootstrapped #indiehackers #devtools
1/ Added 9 real recipes to the Vault today, not 9 variations of the same thing:
Multi-tenant SaaS · Webhook ingestion · Ledger/double-entry accounting · Media processing · API gateway/rate limiter · Mobile BaaS · Notification dispatch · Search-as-a-service · Centralized logging/metrics
37 total now. Bootstrapped, solo, still shipping. 🧵
2/ The bar for "does this deserve a recipe": is this a pattern people build from scratch, badly, under time pressure — every single time?
Webhook ingestion is the clearest example. Everyone's first version has no idempotency, no signature check, no retry queue. Then a duplicate Stripe event double-charges someone and it gets rebuilt correctly, in production, on fire.
That's a recipe now. Idempotent, signature-verified, Redis-backed queue + worker.
3/ Ledger & Double-Entry Accounting is the one I'm most opinionated about.
It is NOT a payments recipe. It doesn't touch Stripe. It's for tracking where money actually went once you have it — marketplaces splitting payouts, internal balances, anything that needs to survive an audit.
Different problem than "take a payment." Treated as one for too long, everywhere.
4/ Two brand new categories: Notifications and Search.
Notification Dispatch is the outbound twin to the Webhook recipe's inbound — unified email/SMS/push, queue + worker, retry-safe.
Search-as-a-Service is just: stop bolting a slow ILIKE query onto your main database and calling it search. Meilisearch in front of Postgres, actually fast, actually typo-tolerant.
5/ Every recipe gets schema-validated against the real live schema, then actually run through the real generator before it ships — not just "the JSON looks right."
Caught real bugs doing this before. Won't stop doing it because a batch is bigger.
6/ No roadmap committee decided any of this. Just looked at what's actually missing and built it.
stacktora.com/vault
#buildinpublic #solofounder #bootstrapped #indiehackers #devtools
Spun up a Node Postgres Redis stack in a couple minutes and everything just ran on first try. The Makefile targets are a nice touch, saves a ton of tribal knowledge going to new team members.
@elifeakekep6oh Thanks so much for giving it a spin! That first-run experience is exactly what we obsess over. If a developer can clone, generate, and get running without fighting their environment, we've done our job.
I'm especially glad you called out the Makefile. It's one of those small details that can eliminate a surprising amount of tribal knowledge and onboarding friction across a team. That's ultimately what Stacktora is about—making your stack repeatable, shareable, and consistent from day one.
Really appreciate you taking the time to test it, and if you have any ideas or rough edges you run into, I'd genuinely love to hear them. We're building this alongside the developer community. 🚀
Can you submit a stack recipe on Stacktora?
Yes — stacktora.com/submit lets any signed-in account propose a recipe. It lands as pending review; the Stacktora team approves or declines it before it appears in the public registry. You can track the status of your own submissions right on that page. In the meantime, .stacktora/recipes/ also lets you and your team share recipes internally with zero setup — see stacktora recipes in the CLI docs.
Toggle on Supabase and Stacktora generates a starter supabase/config.toml with project ref, local ports, and (if you enabled seed data) a [db.seed] block pointed at the same docker/init.sql your compose stack uses. It configures a separate Supabase-managed Postgres instance—not the one in your compose file. Use it if you want @Supabase as your Postgres/Auth/Storage provider. A supabase/README.md covers linking and wiring connection strings.
#Supabase #Postgres #DevTools #Backend #Stacktora
https://Stacktora.com
On a paid plan, you can push your generated bootstrap straight to @GitHub as a pull request—no need to download or leave Stacktora.
Connect a repo, and we commit every file on a new branch and open a PR for review. We don't ask for @Vercel
or @Supabase tokens because a live deploy key is a much bigger trust ask than a scoped GitHub PR. Each platform is better placed to own its own credentials.
#GitHub #DevTools #PR #Stacktora #DeveloperProductivity #PullRequest #Vercel #Supabase
https://Stacktora.com
🚀 Big news for our Product Hunt community: Stacktora is now available in 14 languages.
When we launched, developers from around the world asked: "When can I use Stacktora in my language?"
Today, that answer is "now."
We've added full interface support for:
🇺🇸 English · 🇫🇷 Français · 🇩🇪 Deutsch · 🇪🇸 Español · 🇵🇹 Português · 🇮🇳 हिन्दी · 🇮🇳 ਪੰਜਾਬੀ · 🇮🇩 Bahasa Indonesia · 🇯🇵 日本語 · 🇰🇷 한국어 · 🇨🇳 中文 · 🇻🇳 Tiếng Việt · 🇮🇹 Italiano · 🇹🇷 Türkçe
Same Stacktora. Same reproducible environments. Now in your language.
Ship globally. Start locally. → [Stacktora.com]