My
✨ Onboard your agent to SiliconPin

SiliconPin Pod
Autonomous Cloud Engine

Instant rootless container pods, managed database sidecars, and live public tunnels—orchestrated seamlessly by developers and AI agents using the fast Go-native sp CLI.

🤖 Onboard Your Agent What is a Pod? ↓
AI Agent Integration

Onboard Your AI Agent

AGY Claude Cursor ChatGPT
Step 1
Copy Agent Setup Prompt
Copy the instruction prompt. It tells your AI assistant how to fetch and execute sp CLI setup.
Step 2
Paste in AI Assistant
Paste the prompt directly into your AI assistant chat window.
Step 3
Automatic Cloud Pods
Your agent will automatically install tools, attach database sidecars, and manage deployments.
https://siliconpin.com/siliconpin-pod/agent-setup/prompt.md
View prompt.md
Core Infrastructure Definition

What is a SiliconPin Pod?

A SiliconPin Pod is a high-performance, containerized execution environment engineered for autonomous agent workloads and microservice applications. Powered by rootless Podman execution, each pod operates inside an isolated Linux network bridge with automatic HTTPS domain routing and managed sidecars.

⚡

Instant CLI Deployment

Deploy container images or source applications in a single command using sp deploy <name> --port=3000.

🗄️

Database Sidecars

Attach MariaDB, MongoDB, or Valkey (Redis) pods to your deployment network using sp deployments attach db mariadb <id>.

🌐

Zero-Config Tunneling

Instantly expose local web servers on port 3000 to public HTTPS endpoints using sp tunnel 3000 for live previewing.

🛡️

Rootless Isolation

Containers execute inside non-privileged namespaces without root host permissions, guaranteeing maximum cloud multi-tenant isolation.

💾

Snapshot Backups

Take complete snapshots of your application volumes, database state, and pod metadata with sp backup <id>.

🤖

Agent Ready Protocol

Built with non-interactive flags (--token, --method) designed specifically for LLM execution loops.

How SiliconPin Pod Orchestration Works

Four simple steps from local code generation to active public cloud pod.

1

1. Agent Prompting

Pass the onboarding instruction prompt to AGY, Claude Code, or Cursor Agent in your workspace.

2

2. CLI Verification

The agent verifies sp CLI installation and authenticates via API token.

3

3. Pod Orchestration

sp deploy launches rootless Podman containers and links database sidecars.

4

4. Live HTTPS Link

Caddy reverse proxy issues instant SSL and routes public traffic to your active deployment domain.

sp CLI Reference Guide

Direct terminal commands for manual developers and automated scripts.

# SiliconPin CLI Core Cheat Sheet sp CLI v1.0.0
# 1. Install CLI
curl -fsSL https://siliconpin.com/downloads/sp/install.sh | bash
# 2. Update CLI binary
sp update
# 3. Non-interactive Login
sp login --token=$SP_TOKEN
# 4. Deploy static site or build folder (./build/, ./dist/)
sp deploy ./build/ --template=static
# 5. Deploy Git repository with auto stack template
sp deploy https://github.com/user/repo --template=nodejs
# 6. Attach MariaDB Database
sp deployments attach db mariadb <deploymentId>
# 7. Expose local port 3000
sp tunnel 3000

Frequently Asked Questions

Everything you need to know about SiliconPin Pods, AI agent onboarding, and deployment security.

What is a SiliconPin Pod?
A SiliconPin Pod is an isolated, lightweight container execution environment running on SiliconPin Cloud infrastructure. Pods are orchestrated via rootless Podman technology and can be managed directly through the fast Go-based `sp` CLI or by AI agents.
How do AI agents (AGY, Claude Code, Cursor) interact with SiliconPin Pods?
AI agents use the `sp` CLI non-interactive mode. By providing the prompt from the onboarding guide, agents learn the exact commands to authenticate, deploy, and manage sidecars without needing human terminal interaction.
Can I attach database sidecars (MariaDB, MongoDB, Valkey) to my Pod?
Yes. You can instantly provision and attach isolated database containers that share a secure, private network bridge with your application pod using the `sp deployments attach db` command.
What is `sp tunnel` and how does it compare to a deployed Pod?
`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. It's meant for live previewing. A deployed Pod, however, hosts the actual application code on cloud servers permanently.
Is container isolation and security guaranteed?
Yes. All workloads are executed as rootless containers, meaning the processes inside the pod cannot gain root access to the host server. Network bridges are also isolated per-deployment.