Roadmap

What's next

Where we're headed — the near-term work and the longer-term bet.

This is a direction, not a promise. No fixed dates, no guarantees on order — priorities shift based on what you tell us you actually need. If something here matters to you, let us know.

Right now

What we're actively exploring for the near term.

Exploring

Broader locale coverage.Arabic is the next big swing on our radar — but it means real right-to-left layout support, not just translation, so it's a proper project rather than a quick add.

Exploring

More datastores and backing services added to the wizard, based on what people actually request.

Exploring

A larger template gallery — more battle-tested starting points to fork from instead of building a stack from zero.

Exploring

Deeper drift detection in the CLI — catching more of what can silently diverge between your recipe and your working files, not just the basics.

The bigger bet

Where we said stacktora.json was headed — and how much of it is already real.

Shipped

One recipe, the whole project.stacktora plan shows a real line-by-line diff before anything changes, doctor and status keep a live project healthy, and --json makes all of it scriptable. Not vaporware — this is what stacktora sync actually does today.

Shipped

An AI context layer.A published JSON Schema gives every stacktora.json real editor autocomplete. stacktora/audit-action and stacktora-vscode let CI and your editor read and enforce the format natively — no CLI install required.

Shipped

A recipe marketplace.A real, database-backed registry, browsable at stacktora.com/vault — reachable via stacktora recipes --remote and install --remote from the terminal. Anyone signed in can propose a recipe at stacktora.com/submit; it goes live once reviewed.

Shipped

Org-wide standardization.A company.stacktora.json next to any project lets stacktora audit enforce allowed runtimes, tooling, datastores, services, secret-handling, and required outputs — across every developer, every repo, every AI agent touching the codebase.

Vision

Becoming infrastructure, not just a tool.This one is never really "done" — it grows by adoption, not by a feature shipping. What's real so far: a GitHub Action and a VS Code extension that read stacktora.json on their own, without our CLI. The bet is that more outside systems keep doing the same.

Got a feature that would actually move the needle for you? We'd rather hear it now than guess.

Tell us what you need