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 think stacktora.json goes if we're right about this.

Vision

One recipe, the whole project.Not just Docker and CI — runtime, secrets, infra, coding standards, deployment. Edit the recipe, regenerate everything, forever. Think Terraform, but for how a project is put together in the first place.

Vision

An AI context layer.Right now, AI coding tools guess at how your project is set up. If they could read stacktora.json instead, that's fewer hallucinated assumptions and cheaper, more accurate prompts — for any agent, not just ours.

Vision

A recipe marketplace.Installable, opinionated architecture recipes — an official Stripe SaaS starter, a healthcare-compliant stack, a fintech baseline — shared or sold by companies, consultancies, and the community.

Vision

Org-wide standardization.A company.stacktora.json that enforces your team's standards across every developer, every repo, every new hire — and every AI agent touching the codebase.

Vision

Becoming infrastructure, not just a tool.If CI systems, cloud platforms, and AI tools can all read the same recipe format, stacktora.json stops being "a file our tool generates" and starts being foundational — the way Git, Docker, and Terraform became foundational.

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

Tell us what you need