Neutron CLI
One 21 MB Go binary that handles scaffolding, dev servers, database migrations, builds, deploys, Studio, and MCP. Auto-detects your project's language and delegates to the right sub-toolchain.
One binary. Seventeen commands. Every language.
Install once. Run anything.
A single neutron binary handles every SDK in the ecosystem. It detects your project's language from neutron.config.* and invokes the right tool underneath — Vite for TypeScript, Cargo for Rust, Go's build system for Go, setuptools for Python, zig build for Zig, and so on. You don't learn seven command-line surfaces; you learn one.
$ neutron new my-app # scaffold from 20+ templates
$ neutron dev # HMR dev server
$ neutron build # production build, all targets
$ neutron preview # serve the built output
$ neutron db migrate # apply pending migrations
$ neutron db studio # launch visual database manager
$ neutron db reset # wipe and re-seed
$ neutron deploy --target cloudflare # deploy to any configured adapter
$ neutron studio # standalone Studio server
$ neutron mcp --stdio # MCP server for AI clients
$ neutron desktop dev # Tauri desktop dev
$ neutron native run ios # build + run on iOS sim
$ neutron native run android # build + run on Android emulatorneutron new with 20+ templates: web app, API, full-stack, mobile (Expo Go), desktop (Tauri), worker, static site, documentation.uvicorn --reload for Python. Same neutron dev in each.neutron studio boots the visual database manager against your local Nucleus. Browse all 14 data models; no install step.neutron mcp exposes 17 tools over stdio or HTTP. OpenAI-compatible, --dump-schema for AI context priming.Built in Go for a reason.
One static binary, cross-compiled to every OS and arch we support. No Node runtime to bring. No Python interpreter to pin. Install with a single curl, or grab a release from GitHub. The CLI is the same size and shape on Linux, macOS, Windows, and ARM — and it's how your CI servers will talk to Neutron too.
# macOS / Linux
curl -fsSL https://neutron.build/install.sh | sh
# Homebrew
brew install neutron-build/tap/neutron
# Windows
winget install neutron.neutron
# Or grab a release binary from GitHub
What it's for
Every day of working with Neutron. Local dev, CI pipelines, deploy scripts, one-off migrations, Studio sessions, MCP integrations with Claude or ChatGPT. If it's Neutron-shaped, it runs through neutron.
Why one CLI?
Because a language-agnostic ecosystem needs a language-agnostic front door. If every SDK had its own CLI you'd be memorizing seven sets of flags; instead, the Go binary delegates to whatever the underlying language expects, and you only learn one surface.
Part of a bigger system
The CLI knows about every other Neutron component: it can scaffold a Rust service that talks to a Nucleus cluster via neutron-nucleus, spin up Studio against it, and deploy both through the same build pipeline. One tool for the whole stack.