Vision

The problem

Rust is an excellent language for backend services: fast, safe, and predictable. But starting a real-world backend in Rust is slow: you pay a high “day-one tax” before the first line of business logic.

The result: teams either avoid Rust for CRUD-heavy products, or spend days on boilerplate before writing a single line of business logic. Gize targets exactly this pain: initial productivity. From gize new shop to a running, organized, production-shaped API in minutes, without hiding the architecture and without magic.

Who it is for

• Teams adopting Rust for web/backend who want batteries-included velocity without giving up Rust's guarantees.
• Rust developers tired of copy-pasting the same project skeleton.
• Startups and product teams that need CRUD APIs, an admin and auth quickly, but keep the option to drop to raw code.

Differentiators

• Transparent codegen: everything is normal Rust you can read, diff and edit.
• Batteries, but detachable: admin, auth and OpenAPI are opt-in crates.
• Manifest-driven, not manifest-locked: gize.toml powers gize sync, but hand edits are respected.
• Rust-native ergonomics: DTO validation, typed errors and async-first design.

Success criteria

Gize succeeds if a developer can:

• Scaffold a new project and have it compile and serve in minutes.
• Generate a full CRUD resource with one command and immediately hit its endpoints.
• Read every generated file and understand it, with no hidden behavior.
• Delete Gize from the project and still have a working, idiomatic Rust codebase.