Skip to content

Metros & Regions

KraftCloud continues to bring new locations across the planet, allowing you to provision services daringly close to your users. We use IATA codes to represent metro names.

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-DC Provider Connectivity

For more information on how we connect 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 complaince or for other security, performance or cost-saving reasons, please get in contact for more details on what typical offerings look like and how we can provide the necessary tools to you and your SRE team.

Available Metros

By default, at present, we support the following metros:

IATA CODERegion
dal0๐Ÿ‡บ๐Ÿ‡ธDallas, TX, USA
fra0๐Ÿ‡ฉ๐Ÿ‡ชFrankfurt, DE
sin0๐Ÿ‡ธ๐Ÿ‡ฌSingapore
was1๐Ÿ‡บ๐Ÿ‡ธWashington DC, USA

If thereโ€™s a metro location youโ€™d need, please contact us on Discord or write to [email protected].

Usage

When using kraft, you can set the metro you wish to use by either setting the CLI flag --metro in any kraft cloud subcommand or by setting the environmental variable KRAFTCLOUD_METRO. Use the IATA code descriptor to target the specific metro. For example with fra0:

Terminal window
# Via CLI flag
kraft cloud --metro fra0 run -p 443:8080 nginx:latest
# or via environmental variable
export KRAFTCLOUD_METRO=fra0
kraft cloud run -p 443:8080 nginx:latest

When using the REST API, simply set the IATA code of the metro you wish to connect to as the subdomain suffix to the relevant API endpoint for example with fra0, the API endpoint becomes:

api.fra0.kraft.cloud

And when used with curl:

Terminal window
curl -X GET \
-H "Authorization: Bearer ${KRAFTCLOUD_TOKEN}" \
-H "Content-Type: application/json" \
"https://api.fra0.kraft.cloud/v1/instances/status" \
-d '[
{
"uuid": "7bece402-c36f-457f-a165-0e2d63f1db53"
}, {
"uuid": "d6bb5ad2-402e-4f8d-981d-caf52110426e"
}
]'