Roadmap

18 months, six gated phases. Time horizons are indicative and assume a small core team. A phase starts only when the previous one meets its acceptance criteria.

Phase 1

MVP

✓ DoneMonths 0–4

Prove initial productivity. From gize new to a running CRUD API in minutes, with readable generated code.

  • gize new, make app, make model, make crud
  • make migration, migrate (Postgres only)
  • gize serve, gize doctor
  • gize.toml parsing; safe file writer with --force/--dry-run
  • Snapshot + integration tests; base CI
Phase 2

Alpha

✓ DoneMonths 4–8

Make Gize usable on a real side-project. Round out the developer loop and introduce the manifest-driven workflow.

  • gize sync: reconcile app from gize.toml (idempotent, drift detection)
  • make migration diffing (model change → migration diff)
  • gize-auth MVP: session/JWT scaffolding, password hashing, guards
  • Relationships in models (FKs, one-to-many)
Phase 3

Beta

In progressMonths 8–12

Feature-complete for the productive CRUD backend story. Introduce the Admin and API docs.

  • gize-admin: make admin → List/Create/Edit/Show/Delete, filters, search, pagination
  • gize-openapi: spec generation from handlers/DTOs
  • Second database consideration (MySQL/SQLite)
  • Plugin API v0
  • Docs site scaffold
Phase 4

RC

PlannedMonths 12–15

Stabilize. Freeze public APIs and generated-code contracts. Harden.

  • API/codegen stability guarantees and deprecation policy
  • Upgrade/migration guide between Gize versions
  • Performance benchmarks + regression gates in CI
  • Security review (auth, generated SQL, admin)
  • Complete docs: Getting Started, Architecture, Cookbook, FAQ
Phase 5

v1.0

PlannedMonths 15–18

Production-ready 1.0 with a stability promise.

  • SemVer stability guarantee for CLI + generated-code contracts
  • Published crates on crates.io; installable CLI
  • Polished website, examples gallery, contribution guide
  • LTS-style support statement
Phase 6

v2.0

FutureBeyond 18 months

Ecosystem expansion, with each candidate behind its own ADR and demand signal.

  • Alternative framework target (Actix) via gize-core seam
  • Additional databases as first-class (MySQL, SQLite)
  • Background jobs & events as first-class generators
  • gRPC / GraphQL surfaces
  • Marketplace of community plugins and templates