Upcloud

et-upcloud

UpCloud infrastructure skills for Claude Code — provision and deploy full-stack apps with the upctl CLI.

When to use et-upcloud: Setting up servers, databases, object storage, and secret management on UpCloud. Deploying apps with Docker Compose + Caddy auto-SSL. For AWS/GCP/Azure, use other tooling.

Workflow

  0. START (optional)     1. SETUP                    2. DEPLOY                 3. MANAGE
  /upcloud:start          /upcloud:setup              /upcloud:deploy push      /upcloud:deploy status
  ┌────────────────┐      ┌────────────────┐          ┌────────────────┐        ┌────────────┐
  │ Discover needs │      │ Create server  │          │ rsync code     │        │ Health     │
  │ Recommend arch │─────▶│ Provision DB   │──config─▶│ Inject secrets │──live─▶│ Logs       │
  │ Show plan      │      │ Setup secrets  │          │ Docker Compose │        │ Rollback   │
  │ Generate scrpts│      │ Generate config│          │ Caddy auto-SSL │        │ Secrets    │
  └────────────────┘      └────────────────┘          └────────────────┘        └────────────┘
   interactive wizard      writes .deploy.json         reads .deploy.json        scripts/ too

Architecture

  ┌─────────────────────────────────────────────────────┐
  │ UpCloud Cloud Server (Docker + Caddy + Infisical)   │
  │                                                     │
  │  ┌─────────┐  ┌─────────┐  ┌──────────────┐       │
  │  │ Your App│  │  Caddy  │  │  Infisical   │       │
  │  │ :8080   │◀─│ :443    │  │  (secrets)   │       │
  │  └─────────┘  └─────────┘  └──────────────┘       │
  └─────────────────────────────────────────────────────┘
           │                              │
           ▼                              ▼
  ┌─────────────────┐          ┌───────────────────┐
  │ Managed         │          │ Object Storage    │
  │ PostgreSQL      │          │ (S3-compatible)   │
  │ + pgvector      │          │                   │
  │ + pg_cron       │          │                   │
  └─────────────────┘          └───────────────────┘

Skills

Skill	Command	Description
start	/upcloud:start	Interactive onboarding wizard (guided setup from zero)
setup	/upcloud:setup	Direct provisioning (for users who know what they want)
deploy	/upcloud:deploy push	Sync code + rebuild containers
	/upcloud:deploy migrate	Run database migrations
	/upcloud:deploy status	Health check + container status
	/upcloud:deploy logs	Stream service logs
	/upcloud:deploy rollback	Revert to previous version
	/upcloud:deploy secrets	Manage secrets (list/add/update)

Secret Management — Low Risk Only

Provider	Risk	Effort	Rotation	Audit Trail
Infisical (self-hosted)	Low	Medium	Automatic	Full
Docker Secrets	Low	Low	Manual	None
S3 Bundle (encrypted)	Acceptable	Low	Manual	S3 logs

Encrypted .env in containers is never supported — high risk, no rotation, no audit trail.

Installation

Prerequisites

1. Claude Code — Install Claude Code
2. upctl — UpCloud CLI tool:

   # macOS
   brew tap UpCloudLtd/tap && brew install upcloud-cli
   
   # Linux (deb)
   # Download from https://github.com/UpCloudLtd/upcloud-cli/releases
   
   # Verify
   upctl version
   

3. Authenticate upctl:

   upctl account login --with-token
   # Or set: export UPCLOUD_TOKEN="your-token"
   

Install the plugin

In Claude Code:

# Add marketplace (GitHub format)
/plugin marketplace add Emerging-Tech-Visma/et-upcloud

# Install
/plugin install upcloud@et-upcloud

Restart Claude Code after installation.

Verify installation

# In Claude Code, run:
/upcloud:start

Claude should start the onboarding wizard, asking about your project.

Quick Start

Starting from zero? Use the wizard:

/upcloud:start

The wizard walks you through everything:

1. Asks about your project, tech stack, data needs, and scale
2. Recommends an architecture with cost estimate
3. Shows the exact commands for your approval
4. Provisions the infrastructure
5. Generates standalone scripts (scripts/deploy.sh, scripts/migrate.sh, etc.)
6. Shows a "what's next" checklist

Already know what you want?

/upcloud:setup

Jumps straight to provisioning — provide project name, zone, plan, and features.

Deploy your app

/upcloud:deploy push

Or use the generated script:

./scripts/deploy.sh

Syncs code via rsync, injects secrets, rebuilds Docker containers, and runs a health check.

Check status

/upcloud:deploy status

Shows container health, endpoint status, and resource usage.

File Structure

et-upcloud/
├── .claude-plugin/
│   └── marketplace.json              ← marketplace manifest
├── et-upcloud-plugin/                ← plugin directory
│   ├── .claude-plugin/
│   │   ├── plugin.json               ← plugin identity + version
│   │   └── settings.json             ← permissions + deny list for deletes
│   ├── CLAUDE.md                     ← instructions loaded when active
│   ├── commands/
│   │   ├── start.md                  ← /start — onboarding wizard
│   │   ├── setup.md                  ← /setup — direct provisioning
│   │   ├── deploy.md                 ← /deploy — deployment commands
│   │   └── server-status.md          ← /server-status — quick health check
│   └── skills/
│       ├── upcloud-start/
│       │   ├── SKILL.md              ← onboarding wizard (6 phases)
│       │   └── templates/scripts/    ← deploy.sh, migrate.sh, rollback.sh, etc.
│       ├── upcloud-setup/
│       │   ├── SKILL.md              ← setup skill definition
│       │   ├── references/           ← provisioning playbooks
│       │   └── templates/            ← docker-compose, Caddyfile, etc.
│       └── upcloud-deploy/
│           ├── SKILL.md              ← deploy skill definition
│           └── references/           ← deploy, migrate, rollback playbooks
├── CLAUDE.md                         ← project overview
├── CHANGELOG.md
├── RELEASING.md                      ← release checklist
└── README.md

Cost Estimate

Minimal viable setup per project:

Resource	Plan	~EUR/month
Cloud Server	2xCPU-4GB	~22
Managed PostgreSQL	1xCPU-2GB-25GB	~16
Object Storage	250GB	~5
Total		~43

Multiple projects can share one server and one PG instance (separate databases).

Supported Database Types

Type	--type	Notes
PostgreSQL	pg	Primary — includes pgvector, pg_cron, pg_trgm
MySQL	mysql	Supported via upctl database create --type mysql
OpenSearch	opensearch	Full-text search and analytics
Valkey	valkey	Key-value store (replaces Redis, which is deprecated upstream)

Note: Redis is not supported. UpCloud deprecated Redis in favor of Valkey (upctl v3.27.0+). Use --type valkey instead.

Principles

1. No secrets on disk — everything through the configured provider
2. No secrets in images — injected at runtime only
3. No deletes without approval — always confirm destructive operations
4. EU data residency — fi-hel1 default
5. Least privilege — three DB roles, scoped storage keys
6. Idempotent — safe to run setup twice
7. Observable — every deploy reports health

License

MIT