aspenx

Parallel feature workspaces for your monorepo.

Some apps are six services in one repo. A feature usually changes two of them, but testing it means running all six, and running them three times over when three features are in flight. AspenX gives each feature its own folder where the whole stack runs on the feature's own database. The two services it touches run from worktrees with hot reload. The other four start from prebuilt images of main.

All six run inside the feature. Main images are built once per pinned commit and shared by every feature, so the four untouched services cost almost nothing to start.

• Hostnames, not ports. Each feature gets its own domain, so logins and cookies stay put.
• Databases cloned in seconds. One shared Postgres and Redis, with every service's database cloned per feature.
• Any base, stackable. Pin untouched services to a release ref, or point one at another feature's branch.
• One Claude session per feature. Started at the feature root with every service in view.
• Drop it and it's gone. No stray worktrees, branches, databases, containers or tunnels.