Providers
Multi-cloud provider configuration and selection
Providers
Fugoku supports multiple cloud providers for compute, storage, and networking. Each provider offers different capabilities, pricing, and regional availability.
Overview
Fugoku acts as a unified control plane across multiple cloud providers. You can configure providers in the Console or via the API, and switch between them when creating resources.
Provider Types
SkyPilot
SkyPilot provides multi-cloud access through a single interface, supporting AWS, GCP, Azure, Lambda, and RunPod.
Best for:
- GPU workloads across multiple clouds
- Spot instance bidding
- Cost optimization across providers
- Rapid prototyping
Supported regions: All regions where SkyPilot has coverage (AWS, GCP, Azure, Lambda, RunPod)
Pricing: SkyPilot handles billing directly with each cloud provider. Fugoku does not add markup.
Latitude.sh
Latitude.sh provides bare metal servers with direct API access.
Best for:
- Dedicated hardware workloads
- GPU clusters (A100, H100)
- High-performance computing
- Persistent storage on bare metal
Supported regions: New York (NYC), Chicago (CHI), Dallas (DAL), Los Angeles (LAX), Miami (MIA), San Jose (SJC), Toronto (TOR), London (LON), Frankfurt (FRA), Amsterdam (AMS), Singapore (SGP), Tokyo (TYO), Sydney (SYD)
Pricing: Hourly, monthly, or yearly billing. Volume discounts available.
AWS
Direct AWS integration for EC2 and related services.
Best for:
- Existing AWS workloads
- Deep AWS feature access
- Enterprise AWS agreements
Supported regions: All AWS regions
Pricing: Standard AWS pricing; Fugoku does not add markup.
Provider Selection
When creating a resource, you choose a provider based on:
- Workload type — GPU workloads may benefit from SkyPilot spot instances; bare metal workloads need Latitude
- Region — Choose a provider with capacity in your target region
- Cost — Compare pricing across providers for your workload
- Features — Some features are provider-specific (e.g., IPMI for Latitude bare metal)
Setting Up Provider Credentials
Via Console
- Navigate to Account → Providers
- Click Add Provider
- Select provider type (SkyPilot, Latitude, AWS)
- Enter API credentials
- Choose default region
- Click Save
Credentials are encrypted at rest and never displayed in plain text after creation.
Via API
curl -X POST https://api.fugoku.com/v1/providers \
-H "Authorization: Bearer $FUGOKU_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "latitude",
"apiKey": "lat_sk_abc123",
"region": "NYC",
"enabled": true
}'Provider Health
Each provider has a health status indicator in the Console:
- Connected — Provider is active and responding
- Degraded — Provider is experiencing issues
- Disconnected — Provider credentials are invalid or unreachable
Check provider health via API:
curl https://api.fugoku.com/v1/providers/prov-abc123 \
-H "Authorization: Bearer $FUGOKU_API_TOKEN"Cost Differences
| Provider | Compute Pricing | Storage Pricing | Networking |
|---|---|---|---|
| SkyPilot | Varies by cloud | Varies by cloud | Varies by cloud |
| Latitude | Hourly/monthly/yearly | Per-GB/month | Included |
| AWS | Standard AWS rates | Standard AWS rates | Standard AWS rates |
Troubleshooting
Provider Connection Failures
- Verify API credentials are correct
- Check that the provider is enabled
- Ensure the region has capacity
- Review provider health status in the Console
Credential Errors
- 401/403: Check API key validity
- 404: Provider not found or not associated with your project
- 422: Invalid configuration (unknown region, plan, or OS)
Next Steps
- Create a Server — Learn about bare metal servers
- API Reference — Provider API endpoints