Quickstart
Get a full-stack app live in under two minutes. No config files, no Docker, no cloud console.
1 — Authenticate
2 — Deploy
Pillar will detect your frontend and backend frameworks, ask you to confirm, and return a live HTTPS URL.
Install the CLI
Download the binary for your platform and move it onto your PATH.
macOS (Apple Silicon)
macOS (Intel)
Linux (x86_64)
CLI Reference
Every command Pillar exposes, with flags and examples.
Deploy a full-stack app from your local directory.
Usage
Flags
--frontend <path>Path to frontend directory (default: auto-detect)--backend <path>Path to backend directory (default: auto-detect)--env <file>Env file to inject (default: .env)--region <region>Deployment region: us-east-1 | eu-west-1 (default: us-east-1)Example
List all of your active deployments.
Usage
Example
Show details about a specific deployment.
Usage
Example
Stream live logs from a running deployment.
Usage
Flags
--tail <n>Number of historical lines to show (default: 50)--followKeep streaming (default: true)--service <frontend|backend>Filter to one serviceExample
Permanently delete a deployment and free its resources.
Usage
Flags
--forceSkip confirmation promptExample
Save your API key locally so every command is authenticated.
Usage
Example
Your key is stored in ~/.pillar on disk.
You can also set PILLAR_API_KEY as an environment variable — it takes precedence over the stored key.
Run pillar whoami to confirm which account you're authenticated as.
Supported Frameworks
Pillar auto-detects these frameworks. No config required.
Frontend
Backend
Environment Variables
Pillar injects your .env file into the deployed service at build time. Variables are encrypted at rest and never logged.
You can also set PILLAR_API_KEY in your shell environment to authenticate without running pillar auth. This is useful for CI pipelines.
Regions
Choose the region closest to your users with the --region flag.
us-east-1US East (N. Virginia)eu-west-1EU West (Ireland)ap-southeast-1Asia Pacific (Singapore)