Provision a virtual machine on AWS, DigitalOcean, or Akamai with the exact same request. Switch the tab to see what changes.
# 1. Exchange your provider token for a kopernik.us tokencurl -X POST https://api.kopernik.us/v0/auth/authorize/aws \-d '{ "accessToken": "<your-provider-pat>" }'# 2. Create a VM — identical request for every providercurl -X POST https://api.kopernik.us/v0/resource/machine/aws \-H "Authorization: Bearer $TOKEN" \-d '{ "regionUid": "...", "machineTypeUid": "...", "imageUid": "..." }'
Only the highlighted provider name changes. Same endpoints, same request body, same response model — across every cloud.
kopernik.us acts as a unified API gateway that abstracts the differences between cloud providers, allowing you to manage resources across multiple platforms using a consistent interface.
Use a single REST API to interact with all supported cloud providers. No need to learn different APIs for each platform.
Each request maps to a provider-agnostic resource — machine, volume, vpc, cluster — which kopernik.us translates into the native AWS, DigitalOcean, or Akamai API call.
Manage compute, storage, networking, and container resources across all providers with the same operations and data models.
Get started with kopernik.us in just a few simple steps
Create a Personal Access Token at your cloud provider
Exchange it for a kopernik.us authentication token
Start managing your resources via API or Web Console
Your provider token is exchanged for a scoped kopernik.us token — choose read-only or read-write to control exactly what the API can do on your behalf.
Everything you need for efficient multi-cloud management
AWS EC2, DigitalOcean Droplets, and Akamai Linodes all become the same machine resource. The request path differs only by the provider name.
Provider-agnostic resource models mean moving a workload to another cloud is a one-word change in the request — not a rewrite.
List, create, and delete machines, volumes, networks, and Kubernetes clusters across every provider from one console or API.
Described by an OpenAPI 3 spec with auto-generated TypeScript types and interactive, browsable reference docs.
Support for all major cloud resource types
Accounts, SSH Keys
Machines, Kubernetes Clusters, Container Apps, App Templates
Block Storage Volumes, Buckets
Domain Zones, Firewalls, VPCs
Images, Machine Types, Regions