Stacktora
Define once, run anywhere.
Start new thread

Stacktora - Define once, run anywhere.

by•
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.

Add a comment

Replies

Best
Maker
You can now set a username in Settings.
Maker
You can now include your GitHub, X and LinkedIn handle in your Stacktora account.
Maker

Recently we shipped which currently serve to attribute those that submit to the Vault.

Also, you can now attach your #GitHub, #X and #LinkedIn to your account. This is a feature that will prove more useful once we have rolled out public profile pages.

Come reserve your username today!

Build like a boss.

#DevEnvironment #Bootstrapping #Tech #SoftwareEngineering #Startup #Saas #DeveloperProductivity #AI #VibeCoding #FullStack #Git #GitHub #GitRepo #GitLab #TechStack #ProductHunt #Stacktora #DevTools #Localization #GlobalDev #I18n #DeveloperProductivity #ShipIt

Maker

CLI & stacktora.json

Every project includes a stacktora.json — a small, secret-free record of your stack (runtime, datastores, services, ports, options). The official Stacktora CLI reads that file and regenerates your project's files locally, using the exact same engine as this site — no account, no network, fully offline.

# run without installing
npx stacktora sync     
# regenerate all files from stacktora.json

npx stacktora check    
# show which files would change, without writing

npx stacktora plan     
# like check, but the actual line-by-line diff

npx stacktora doctor   
# Docker, port conflicts, missing .env keys, runtime mismatch

npx stacktora status   
# live container health (docker compose ps) for the stack running here

npx stacktora recipes  
# list curated starting recipes bundled with the CLI

npx stacktora install  
# write one as your stacktora.json — e.g. `stacktora install nextjs`

npx stacktora audit    
# check stacktora.json against company.stacktora.json policy, if one exists

npx stacktora init     
# create a starter stacktora.json here

This keeps a project's dev environment from drifting — when you change a port or add a service inside stacktora.json and re-run sync, your local files update to match without touching .env or any other untracked file. Add --json to check, plan, doctor, status, recipes, or audit for structured output built for CI pipelines and AI agents, rather than parsing colored terminal text.

Each custom environment variable can also carry a source — a plain-text pointer to where the real value actually lives (a vault path, a 1Password item, wherever your team keeps it). Stacktora never stores the secret itself, only where to find it, and prints it as a comment above the variable in your generated .env and .env.example.

If your formatter is Prettier, an optional tools.codeStyle block (semicolons, quote style, line width) generates a real .prettierrc.json matching your preferences — leave it out and nothing changes from the default output.

Every stacktora.json Stacktora writes includes a $schema field pointing at a real — most editors (VS Code included) pick this up automatically for autocomplete and inline validation while you hand-edit the file, catching typos like an invalid datastore id before you ever run sync.

stacktora recipes and stacktora install <id> pull from the same curated stack list as the . Teams can also drop their own recipe files in .stacktora/recipes/*.json — these are listed first and take priority over the bundled ones, so a repo can standardize on its own baseline without waiting on anything server-side.

For enforcing standards rather than just suggesting them, a company.stacktora.json next to the recipe lets stacktora audit check allowed/banned runtimes, tooling, datastores, and services, require a source note on every secret, and require specific output files to be enabled — no server needed, just a file committed to the repo.

Prefer to enforce this in CI without installing the CLI at all? runs the same schema and policy checks as a GitHub Action — add uses: stacktora/audit-action@v1 to a workflow and every pull request gets validated automatically.

Want the same checks live in your editor instead of waiting for CI? The validates stacktora.json against company.stacktora.json as you type — inline warnings on the exact field, plus a status bar summary.

Everything above is fully offline by default. Add --remote to recipes or install to also reach the public registry at — a curated, admin-reviewed list of community recipes served from a real database. This is opt-in only; neither command ever touches the network without it. Any signed-in account can propose a recipe at .

Maker

We’ve made shipping a cakewalk.

New: an animated walkthrough of exactly what happens when you generate a stack with Stacktora and let it go.

→ Pick a runtime, add Postgres + Redis + Kafka, hit generate

→ Push straight to — a real commit, a real PR, no copy-pasting files

→ l imports the repo and reads vercel.json automatically — install command, build command, output directory, zero dashboard clicking

→ base links via its own CLI, picks up supabase/config.toml, provisions Postgres + Auth + Storage

→ Live URL.



One generated stack. Four tools. Each one doing exactly the part it's built for — Stacktora isn't trying to be your deploy platform, it's trying to make configuring one by hand unnecessary.


#buildinpublic
 #devtools
 #webdev

Maker

Stacktora is now available as an npm package. That means you can pull the CLI directly into your workflow—no separate install, no account required to start.

npm publish got it live. npm view stacktora version shows what’s ready. One command and you’re syncing your stack from the terminal.

Same stacktora.json. Same 15+ files. Same reproducible environments. Just faster to get going.

Stacktora.com

Maker

Vercel is a toggle. Flip it on and Stacktora generates a root-level vercel.json with installCommand, buildCommand, and outputDirectory pre-configured for web/. Push to and reads it automatically—zero dashboard config. Frontend deployed. Backend stays as-is. One toggle, one less thing to think about.



Maker

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 as your Postgres/Auth/Storage provider. A supabase/README.md covers linking and wiring connection strings.



Maker

On a paid plan, you can push your generated bootstrap straight to 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

or 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.



Maker

Our Five Pillars

1. Stack Definition Engine

stacktora.json widens from “recipe for the initial generate” into the single source of truth for the whole project over its life: runtime, datastores, CI, references to where real secrets live (never the secrets themselves), deployment targets, and team coding standards. Edit the recipe, regenerate everything, forever — and, see the diff before it touches anything already running.

2. AI Context Layer

AI coding agents — Claude Code, Codex, and whatever comes next — read stacktora.json directly instead of inferring a project's setup by scanning files and guessing. Fewer wrong assumptions, cheaper and more accurate prompts, and it works for any agent, not just tooling Stacktora builds itself. This is no longer a bet on where the industry might go — it's the exact ground Vercel and Supabase are actively fighting over this quarter.

3. Recipe Marketplace

Installable, opinionated starting recipes — an official Stripe SaaS starter, a healthcare-compliant stack, a fintech baseline — shared or sold by companies, consultancies, and the community. This is the same instinct behind the Terraform Registry or Vercel's integrations marketplace: real network effects come from other people building on top of your format, not just from what you build yourself.

4. Enterprise standardization

A company.stacktora.json that enforces an organization's standards across every developer, every repo, every new hire — and every AI agent touching the codebase. Internal platform teams already build this by hand, badly, at every company that reaches a certain size. Stacktora could ship it as a product instead of leaving every company to reinvent it.

5. Becoming a standard

The long game. If CI systems, cloud platforms, and AI tools can all read the same recipe format, stacktora.json stops being “a file our tool happens to generate” and starts being infrastructure — the way Git, Docker, and Terraform's own HCL became infrastructure.

#supabase #vercel #json #cli #git #docker

First
Previous
1234
Next