Zudoku
Cloud Platform

Metros

By default, at present, Unikraft Cloud supports the following metros:

IATA codeRegion
dal🇺🇸Dallas, TX, USA
fra🇩🇪Frankfurt, DE
sfo🇺🇸San Francisco, USA
sin🇸🇬Singapore
was🇺🇸Washington DC, USA

You can list the metros available to your account via the CLI:

TerminalCode
unikraft metros list

One client, every metro

The SDKs treat the metros in scope as one namespace: reads ask each of them at once and merge the answers, tagged with where they came from, so no list of endpoints is kept in your code.

TypeScriptCode
for await (const inst of ukc.instances.list()) console.log(inst.metro, inst.name);

Name a metro — ukc.metro("fra"), or UKC_METRO — to pin a client to one. See the JavaScript and Python SDKs. The Go SDK targets one metro per client, so group results across metros yourself.

Old metros such as fra0 are nearing end of life, and aren't available for new deployments.

Unikraft Cloud continues to add new locations worldwide so you can provision services close to your users. If there's a metro location you'd need, please contact Unikraft Cloud on Discord or write to support@unikraft.cloud. The list of potential metros is:

IATA codeRegion
ams🇳🇱Amsterdam, Netherlands
atl🇺🇸Atlanta, GA, USA
bom🇮🇳Mumbai, India
dal🇺🇸Dallas, TX, USA
dub🇮🇪Dublin, NI
fra🇩🇪Frankfurt, DE
hel🇫🇮Helsinki, Finland
hkg🇭🇰Hong Kong
lon🇬🇧London, GB
lax🇺🇸Los Angeles, CA, USA
mad🇪🇸Madrid, Spain
man🇬🇧Manchester, UK
mel🇦🇺Melbourne, Australia
mia🇺🇸Miami, FL, USA
ord🇺🇸Chicago, IL, USA
osa🇯🇵Osaka, Japan
par🇫🇷Paris, France
sao🇧🇷Sao Paulo, Brazil
sea🇺🇸Seattle, WA, USA
sel🇰🇷Seoul, South Korea
sjc🇺🇸Silicon Valley, CA, USA
sin🇸🇬Singapore
sto🇸🇪Stockholm, Sweden
syd🇦🇺Sydney, Australia
tyo🇯🇵Tokyo, Japan
was🇺🇸Washington DC, USA
yul🇨🇦Montreal, QC, Canada
yyz🇨🇦Toronto, OT, Canada

Intra-data center provider connectivity

For more information on how Unikraft Cloud connects metros together, and for more information about how to reduce in/egress costs with existing deployments at other IaaS providers, please get in touch.

Self-hosted/on-premise metros

If you require running solutions in-house or on-premise, either for SOC/ISO/HIPPA compliance or for other security, performance or cost-saving reasons, please get in contact for more details.

Usage

You can set the metro you wish to use by setting the --metro flag. Use the IATA code descriptor to target the specific metro. For example with fra:

TerminalCode
unikraft run --metro fra \
  -p 443:8080/http+tls \
  --image <my-org>/nginx:latest

For on-premise or enterprise users, you need to set the API endpoint of the metro you wish to use. To do this, define a custom profile and give an identifier to the metro you wish to use:

TerminalCode
unikraft profile use <custom-profile>
unikraft run --metro <custom-metro> ...
Last modified on
AnnotationsInstances