Digital Frontier
//platform

Latitude.sh- and Akash-compatible APIs for cloud VMs

Digital Frontier exposes two API dialects — Latitude.sh and Akash Console — on our own renewable-powered EU edge, paired with an open-source Python SDK that drops straight into existing code.

Open ConsoleSee the infrastructure
//api surface

The resources you already know

Digital Frontier implements the Latitude.sh API surface. Every resource below behaves the way the upstream SDK and docs describe it.

servers

Create, list, reboot and destroy virtual machines across our edge regions.

projects

Group servers, keys and billing into isolated projects — the same model as Latitude.sh.

ssh_keys

Register and rotate the SSH keys injected onto a server at provisioning time.

regions

Discover available edge locations and their live capacity before you deploy.

plans

The virtual-machine configurations you can provision, with pricing.

operating_systems

OS images available to deploy onto a fresh server at first boot.

quickstart.pyPython
1from edge_provider_sdk import EdgeClient
2
3client = EdgeClient(
4 provider="digital-frontier",
5 base_url="https://api.digitalfrontier.so/v1",
6 bearer="df_...",
7)
8
9# provision a VM — identical to the Latitude SDK
10vm = client.servers.create(...)
11
12# the catalog accessor lists what you can deploy
13client.catalog.sites() # edge regions
14client.catalog.plans() # hardware plans
15client.catalog.os() # operating systems
//edge-provider-sdk

A Python SDK that's a drop-in replacement

One client, modelled on LiteLLM's 1-API-N-providers approach — adapted for stateful cloud compute.

  • Wraps latitudesh-python-sdk 3.0.5 — the operations are upstream code, not a re-implementation.
  • The constructor is the only API difference; servers, projects and ssh_keys are untouched.
  • Catalog enums are relaxed to permissive type aliases, so our region, plan and OS slugs pass through.
  • Apache-2.0 licensed and developed in the open on GitHub.
//akash

Already on Akash? Point it here.

The Latitude.sh dialect isn't the only door in. Digital Frontier implements the Akash Console API too — so an Akash workflow runs on our edge unchanged.

  • Digital Frontier also exposes an API compatible with Akash Console.
  • An Akash-native deployment workflow targets our edge without code changes — only the endpoint moves.
  • One renewable-powered edge cloud, reachable through whichever API dialect your stack already speaks.

Same edge cloud, two front doors — switch by pointing your client at our endpoint.

api.latitude.shapi.digitalfrontier.so
console.akash.networkconsole.digitalfrontier.so
//compatibility

Why migrating is a one-line change

The Latitude.sh API is the contract. We implement it; the SDK simply chooses which server to talk to.

01

Keep your code

Your existing calls to servers, projects and ssh_keys stay exactly as they are.

02

Swap the client

Replace the Latitude constructor with EdgeClient — point it at our endpoint with your token.

03

Deploy to the edge

Requests now hit Digital Frontier's renewable-powered edge instead of Latitude.sh. Nothing else changes.

Point your SDK at the edge

Create an API token in the console, or talk to us about moving an existing Latitude.sh integration.

Open Console