Latitude.sh- and Akash-compatible APIs for containers
Our European providers run on Akash today — deploy to them from the official Akash Console. Our own Latitude.sh-compatible API, on our renewable-powered EU edge, is in preview with an open-source Python SDK that drops straight into existing code.
The resources you already know.
Our Latitude.sh-compatible API (in preview) mirrors the Latitude.sh surface — each resource below is designed to behave the way the upstream SDK and docs describe it.
Create, list, restart and destroy containers across our edge regions.
Group servers, keys and billing into isolated projects — the same model as Latitude.sh.
Register and rotate the SSH keys injected onto a server at provisioning time.
Discover available edge locations and their live capacity before you deploy.
The container configurations you can provision, with pricing.
OS images available to deploy onto a fresh server at first boot.
from edge_provider_sdk import EdgeClient client = EdgeClient( provider="digital-frontier", base_url="https://api.digitalfrontier.so/v1", bearer="df_...", ) # provision a container — identical to the Latitude SDK container = client.servers.create(...) # the catalog accessor lists what you can deploy client.catalog.sites() # edge regions client.catalog.plans() # hardware plans client.catalog.os() # operating systems
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.
The constructor picks the backend. Everything downstream stays the same.
Already on Akash? Point it here.
The Latitude.sh dialect isn't the only door in. If you already deploy on Akash, nothing changes: keep using console.akash.network and pick a Digital Frontier provider when you choose where to run.
- Our European providers are live on Akash today — select one in the official Akash Console.
- A Latitude.sh workflow targets our edge without code changes — only the API endpoint moves.
- One renewable-powered edge cloud, reachable through whichever dialect your stack already speaks.
Same edge cloud either way — Latitude.sh clients switch by pointing at our endpoint; Akash users just pick us as their provider.
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.
Keep your code
Your existing calls to servers, projects and ssh_keys stay exactly as they are.
Swap the client
Replace the Latitude constructor with EdgeClient — point it at our endpoint with your token.
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.
Deploy to our providers from the official Akash Console today, or talk to us about moving an existing Latitude.sh integration.