Technical FAQ
Extended technical FAQ for Simulacrum—licensing, adapters, builds, and operations.
Licensing and CLI
How long do CLI updates run? Paid tiers include lifetime updates to the CLI and shipped templates. Generated source code remains yours; see the license for full terms.
Can I use the output on multiple machines? Activation limits follow your tier (1 / 5 / 10 seats). Use simulate deactivate before moving to a new device when required.
Builds and quality
What must pass before I ship? The spec targets clean npm run build, tsc --noEmit, and ESLint baselines on a fresh scaffold. Disable tests only when you intend to add your own coverage strategy.
How do adapters affect typing? Models are aligned per template (e.g. product and order shapes for commerce). Adapter-specific artifacts are generated so you do not fork types by hand.
Operations
Where do I run migrations? See Database overview for the command cheat sheet per stack.
How do I extend the CLI? The plugin registry (see CLI reference) is the supported path for auth, payments, analytics, and content extensions.
For product-level questions also covered on the homepage, see the main FAQ section.