⚡ SiliconPin Developer Suite

SiliconPin CLI (sp)

Fast, rootless container deployment, instant public HTTPS tunneling, and managed database orchestration directly from your terminal or CI/CD pipelines.

📥 Install sp CLI 📖 Command Reference 🤖 Onboard AI Agent →

1-Line Automated Installation

Install or update sp on Linux, macOS, or Windows with automatic PATH detection.

🐧 🍎

Linux & macOS (Bash/Zsh/Fish)

Auto-detects architecture (x86_64 or ARM64 / Apple Silicon), installs binary to /usr/local/bin, and configures shell auto-completion.

curl -fsSL https://siliconpin.com/install.sh | bash
🪟

Windows (PowerShell)

Downloads sp.exe, sets up execution in %USERPROFILE%\.sp\bin, and appends to User PATH.

irm https://siliconpin.com/install.ps1 | iex

CLI Command Reference

Full syntax and examples for managing cloud workloads, tunnels, sidecars, and automated backups.

🔑 Authentication & Session Management

Login to SiliconPin via interactive browser OAuth or non-interactive token for headless servers.

# Authentication Commands sp auth
# Interactive OAuth browser login
sp login
# Headless / CI/CD non-interactive token login
sp login --token=$SP_TOKEN
# Inspect authenticated user session
sp whoami
# Sign out and purge local tokens
sp logout

🚀 Workload & Pod Deployments

Deploy container images, local directories, static site builds, or Git repositories.

# Pod Deployment Commands sp deploy
# 1. Deploy pre-built container image
sp deploy my-service --image=docker.io/library/nginx:alpine --port=80
# 2. Deploy static website folder (./build/ or ./dist/)
sp deploy ./dist/ --template=static
# 3. Deploy Git repository with automated container build
sp deploy https://github.com/org/my-api.git --port=3000
# 4. Trigger rolling update on active deployment
sp update <deploymentId>

🌐 Instant Public Tunnels

Expose any local service port to a secure, public HTTPS endpoint with zero firewall setup.

# Live Public Preview sp tunnel
# Expose local dev server on port 3000
sp tunnel 3000
✓ Tunnel live: https://tunnel-xyz.siliconpin.net -> localhost:3000

🗄️ Managed Database Sidecars

Attach high-performance database containers sharing a private network bridge with your pod.

# Database Sidecars sp deployments attach db
# Attach MariaDB container
sp deployments attach db mariadb <deploymentId>
# Attach MongoDB container
sp deployments attach db mongodb <deploymentId>
# Attach Valkey (Redis) caching container
sp deployments attach db valkey <deploymentId>
# List all attached database services and credentials
sp my dbs

📊 Logs, Filesystem & Snapshot Backups

Stream live logs, inspect container filesystems, and create full snapshot backups.

# Monitoring & Management sp manage
# Follow live container logs in real time
sp log <podId> -f
# List directory contents inside pod container
sp fs ls <podId> /var/www/html
# Create complete snapshot backup (DB + volumes + state)
sp backup <deploymentId>
# Auto-update CLI binary to latest version
sp self-update

CI/CD Integration Recipe

Deploy automatically on git push using GitHub Actions and SiliconPin non-interactive mode.

.github/workflows/deploy.yml YAML
name: Deploy to SiliconPin Pod
on:
push:
branches: [ main ]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install SiliconPin CLI
run: curl -fsSL https://siliconpin.com/install.sh | bash
- name: Deploy Workload
env:
SP_TOKEN: ${{ secrets.SP_TOKEN }}
run: |
sp login --token=$SP_TOKEN
sp deploy . --port=3000

Frequently Asked Questions

Common questions about the SiliconPin CLI and container environments.

Do I need Docker installed locally to use `sp`?
No. When deploying workloads to SiliconPin, container orchestration runs on cloud servers using isolated rootless Podman containers. You do not need Docker running locally to deploy images, static directories, or git repositories.
Where does `sp login` store credentials?
Authentication tokens are stored securely in your user directory at ~/.sp/config.json with restricted user-only file permissions (0600).
How does `sp tunnel` compare to deployed pods?
`sp tunnel` creates a secure reverse-proxy tunnel to expose a local development server (e.g., localhost:3000) to the public internet with a temporary HTTPS URL for rapid testing. A deployed Pod, by contrast, hosts your application code on high-availability cloud servers with persistent NVMe storage and optional database sidecars.
Can autonomous AI agents run `sp` commands?
Yes! `sp` has full support for non-interactive execution flags (--token, --template, --json), enabling Claude Code, Cursor, and AGY to deploy and manage pods without manual prompts. See our AI Agent Onboarding Guide for details.

Ready to Deploy Your First Pod?

Deploy directly from your browser with 1-click WebApps or connect your terminal with the `sp` CLI.

Launch Web Deploy Studio → 🤖 Onboard AI Agent