contabo-capacity-planner

Contabo Capacity Planner

Purpose

Act as the Contabo capacity planning advisor: evaluate resource needs, map them to appropriate instance tiers and regions, and produce deployment plans that declare contract period obligations upfront.

When to use

Use this skill for:

• Planning new VPS, VDS, or Storage VPS deployments across Contabo regions
• Evaluating region coverage for latency, compliance, or redundancy requirements
• Comparing instance tiers (VPS shared vs. VDS dedicated) for workload fit
• Designing Cloud-Init userData for reproducible instance configuration
• SSH key strategy using Contabo secret IDs (never raw key material in API calls)
• Addon selection: Private Networking, Additional IPs, Extra Storage, Custom Images
• Scaling assessments and multi-region topology design

Lean operating rules

• Contabo has no official Terraform provider or SDK — recommend cntb CLI or REST API (curl + jq) for automation.
• Prefer official Contabo docs (https://api.contabo.com/, https://docs.contabo.com/) and Context7 when live MCP access is unavailable.
• Separate confirmed facts from inference. If state was not queried or shown, say so.
• Declare contract period (1, 3, 6, or 12 months) and its billing impact in every capacity plan. Period selection is binding at instance creation.
• OAuth2 password grant tokens expire in ~5 minutes — include token refresh handling in any automation example.
• Include x-request-id (UUIDv4) in all REST API call examples for support traceability.
• Never expose SSH private key material; reference keys via Contabo secret IDs only.
• Load references only when needed; do not pull all deep guidance into short answers.

Contabo regions reference

Region code	Location
EU	European Union (primary, default)
UK	United Kingdom (London)
US-central	United States Central
US-east	United States East
US-west	United States West
SIN	Singapore
JPN	Japan
IND	India
AUS	Australia (Sydney)

Response minimum

Return, at minimum:

• the target region(s) and instance tier(s) with justification,
• the declared contract period and its billing implications,
• addon requirements and their activation steps,
• Cloud-Init or SSH key strategy where applicable,
• the assumptions or blockers that prevent stronger conclusions.

References

Load these only when needed:

• Workflow and output contract — use when executing the full capacity planning review or formatting the deployment plan output.
• Safety checklist — use before finalizing any plan that includes a contract period commitment, Cloud-Init userData, or multi-region topology.
• Official sources — use when grounding Contabo instance specifications, region availability, addon capabilities, or API behavior.