ARCHE
FamiliesDocsExamplesBlogGitHub ↗
Documentation

Start

  • Getting started
  • Philosophy

Guides

  • First hour
  • Agent context
  • Verification
  • Package managers
  • Scaffold lifecycle
  • Showcase & portfolio

Walkthroughs

  • TypeScript fullstack
  • Convex product
  • Rust API & fullstack
  • Solana family
  • Customize & experiments
  • Automation (JSON/MCP)

CLI

  • Overview
  • Flags
  • Subcommands
  • Generated output

Presets

  • Preset catalog

Stack

  • TypeScript architecture
  • Convex
  • Rust
  • Solana
  • Authentication
  • Prisma store
  • tRPC

Operations

  • Deployment
  • Environment variables
  • Workers & queues
  • CI & testing
  • Scaling
  • Security
  • Troubleshooting

Reference

  • Stack links
  • Capabilities
  • This source repo
  • Code examples
← Documentation

Customize and experiments walkthrough

Build from capabilities with compatibility validation, or opt into experimental generators.

1 min read

customize preset

Goal: Pick capabilities (database, ORM, bundles, addons) and let the registry reject incompatible combinations before files are written.

terminal
bun run dev:cli -- my-app --yes --preset=customize --dir=../projects

Without --yes, the CLI walks capability groups interactively. With --yes, defaults apply—review arche.json after generate.

Package manager
OptionStatusNotes
BundefaultStableDefault package manager with Bun-native catalogs.
pnpmStableFirst-class package manager with pnpm-native catalogs.
npmExperimentalNot part of the stable generated-project matrix.
TypeScript runtime
OptionStatusNotes
Node.jsdefaultStable—
Bun runtimeRequires validation—
Rust API
OptionStatusNotes
AxumdefaultRequires validation—
Database
OptionStatusNotes
Postgres + SQLxdefaultRequires validation—
NoneStable—
SeaORMExperimental—

Full matrix reference: Capabilities.

experiments preset

Goal: Explicit opt-in for proof-gated or unstable generators. Read prompts carefully—outputs may not match stable presets.

terminal
bun run dev:cli -- my-lab --yes --preset=experiments --dir=../projects

Honesty

Experiments are labeled Experimental in the registry. Do not ship to production without your own verification harness.

Validate before write

terminal
bun run dev:cli -- validate '{"projectName":"my-app","preset":"customize","database":"postgres","orm":"prisma"}'

Pair with Automation walkthrough for CI and agent loops.

Next steps

  • Capabilities reference
  • Verification labels
  • CLI flags