Optimize & Predict

Search multi-cloud deployment strategies

Analyze a workload profile and generate optimized multi-cloud deployment strategies. The system evaluates different provider combinations across AWS, GCP, Azure, OCI, and DigitalOcean based on cost, latency, and vendor lock-in considerations.

DigitalOcean as a candidate provider: DigitalOcean is a first-class candidate in every exploration run. It is particularly well-suited for cost-optimized workloads — Droplets and Managed Databases typically produce the lowest monthly spend in the comparison report. Set a high cost weight (e.g. 0.7+) and a moderate budget to see DigitalOcean-primary strategies appear at the top of topStrategies in the results.

Request body fields: The request body has two top-level fields that are independent of each other. workloadProfile describes the workload being evaluated (compute/database instances, traffic, latency requirements, and primary region). optimizationWeights is a separate top-level object — not nested inside workloadProfile — that controls how strategies are ranked: cost (default 0.4), latency (default 0.4), and vendorLockIn (default 0.2). Weights need not sum to 1.0; the engine normalises them during scoring. A cost-heavy weight (e.g. cost: 0.9) surfaces the cheapest strategies at the top of topStrategies; a latency-heavy weight (e.g. latency: 0.9) surfaces the lowest-latency strategies instead.

post/multi-cloud/explore

Request

  • Base URL: https://www.cloudworldmodel.ai/api
  • URL: https://www.cloudworldmodel.ai/api/multi-cloud/explore
  • Auth: one of:
    • HTTP bearer
    • API key in header X-PAYMENT
    • API key in header PAYMENT-SIGNATURE

Request body

maxCostPerHournumber

Optional hard budget ceiling (USD/hr). Strategies whose totalCostPerHour exceeds this value are ranked last in the results rather than filtered out, so you can see what is available within and outside your budget in a single response.

errorBudgetPctnumber

Optional SLO error-budget constraint (%). Strategies whose implied error rate (derived from provider-count redundancy: single-provider ~0.5%, two-provider ~0.15%, three+ ~0.05%) exceeds this threshold are ranked last. For example, setting 0.1 means any single-provider strategy is demoted below multi-provider alternatives.

webhookUrlstring uri

Optional HTTPS URL to receive webhook notification when job completes

webhookSecretstring

Optional secret for HMAC-SHA256 webhook signature verification

Example request

{
  "workloadProfile": {
    "computeInstances": 8,
    "databaseInstances": 2,
    "storageGB": 500,
    "trafficRPS": 2500,
    "latencyRequirementMs": 100,
    "primaryRegion": "us-east-1"
  },
  "optimizationWeights": {
    "cost": 0.4,
    "latency": 0.4,
    "vendorLockIn": 0.2
  }
}

Response

Multi-cloud exploration job started

messagestring

Example response

{
  "job": {
    "id": "job-abc123",
    "type": "multicloud_exploration",
    "status": "running"
  },
  "message": "Multi-cloud exploration started. Use GET /multi-cloud/jobs/{id} to check status."
}

Changes

No recorded changes to this operation across all 1 revision of this API.