Skip to main content
pxxl init --new creates a deploy-ready project from the official Pxxl boilerplates. Each starter includes a README.md, a pxxl.boilerplate.json manifest, and deploy defaults that the CLI uses to write pxxl.toml. Interactive init shows clean framework names first, then asks for the package manager when a framework has multiple variants. 
pxxl init --new
pxxl init --new express-bun --name my-api --domain pxxl.pro
pxxl init --new vite-react-npm --name web-app --domain pxxl.pro

​
Flow

  1. Choose a framework.
  2. Choose a package manager when multiple variants exist.
  3. Enter a project name.
  4. Pick an eligible Pxxl domain suffix.
  5. Choose whether to create a new folder or use the current folder.
  6. Optionally deploy immediately.
The CLI validates the project name and selected suffix before writing files.

​
Included Starters

StarterVariants
Expressnpm, pnpm, Bun, Yarn
Vite Reactnpm, pnpm, Bun, Yarn
Static HTMLstatic gallery
PHPbasic PHP
HonoBun
Fastifypnpm
Next.jspnpm
Astronpm
Node TypeScriptnpm
PythonFastAPI, Flask, Django
Gostandard-library HTTP
RustAxum
SvelteKitpnpm
Vue Vitepnpm
Dockerfile NodeDockerfile-based Node service

​
Manifest

Each boilerplate has a pxxl.boilerplate.json manifest: 
{
  "id": "express-bun",
  "family": "express",
  "displayName": "Express",
  "packageManager": "bun",
  "framework": "express",
  "port": 3000,
  "installCommand": "bun install",
  "startCommand": "bun src/server.js"
}
The manifest keeps init consistent across frameworks, package managers, and runtimes.

​
Deploy After Init

cd my-api
pxxl deploy
If you pass --deploy, init creates the project and immediately uploads the first deployment: 
pxxl init --new express-bun --name my-api --domain pxxl.pro --deploy
Boilerplate README files link back to Pxxl docs and the Pxxl deploy flow, so generated repos already explain how to ship the project.