repogen

A pure-stdlib Python CLI that scaffolds a large, original enterprise-style monorepo from three answers: project name, organization name, and website.

It generates 4000+ files by default: frontend (web / admin / crm / mobile), multiple backend services, a database layer with per-entity migrations, shared SDK / UI / config packages, feature modules, infra (docker / k8s / terraform / CI), docs, and .env files (real + .example + dev + prod) at every level.

• No network access. Nothing is downloaded or copied from the internet.
• No third-party dependencies. Standard library only.
• Original templates. Every emitted file is produced from templates authored inside this package — generic scaffolding, not code lifted from anywhere.
• Any tech stack. Choose from several stacks; the generators dispatch to the right language and framework.

Install

cd repogen
pip install -e .        # exposes the `repogen` command
# or run without installing:
python -m repogen

Usage

Interactive (prompts for name, org, website, stack):

repogen

Non-interactive:

repogen \
  --name "Acme Cloud" \
  --org "Acme Inc" \
  --website "https://acme.example" \
  --stack fastapi-next-postgres \
  --output ./acme-cloud \
  --yes

Preview the file count without writing anything:

repogen --name Acme --org "Acme Inc" --website acme.example --dry-run --yes

List stacks:

repogen --list-stacks

Stacks

What gets generated

apps/         web · admin · crm · mobile clients (per-entity pages/screens)
services/     domain backend services (per-entity model/service/router/tests)
packages/     shared sdk · ui · config · pyshared · feature modules
db/           schema · per-entity migrations · seeds · alembic config
infra/        docker-compose · k8s manifests · terraform · nginx gateway
docs/         architecture · runbook · ADRs · OpenAPI stubs
.env*         real + example + development + production, at every level

Flags

Notes on secrets

Generated .env files contain locally-generated random secrets for development convenience. .env.example / .env.production ship placeholder values, and the generated .gitignore excludes real .env files from version control. Rotate before any real deployment.