A Latitude.sh-compatible API, in one import
Switching providers usually means a rewrite. Our API mirrors the Latitude.sh surface, so the move is a base URL and a key — your existing tooling keeps working.
Provider lock-in is mostly an API problem. Once your deploy scripts, SDKs and CI are written against one vendor's surface, "just switch" turns into a rewrite.
So our API is built to mirror the Latitude.sh surface. In practice the migration is two lines:
- from latitudesh_python_sdk import Latitudesh
- client = Latitudesh(bearer="lt_...")
+ from edge_provider_sdk import EdgeClient
+ client = EdgeClient(
+ provider="digital-frontier",
+ base_url="https://api.digitalfrontier.so/v1",
+ bearer="df_...",
+ )
# every operation below is identical
instance = client.servers.create(...)
Your call sites don't change — only where they point.
The Latitude.sh-compatible API is currently in preview. For production workloads today, use the Akash Console — that's the live path. We'll move this notice the moment the compatible surface is production-ready.
What "compatible", not "affiliated", means
To be clear: we're an independent provider. We're not affiliated with, endorsed by, or sponsored by Latitude.sh or Akash — we implement API-compatible interfaces so existing tooling works unchanged. The trademarks belong to their respective owners.
Why bother mirroring someone else's API
Because the best migration is the one you barely notice. If trying us costs a base URL and a token instead of a sprint, the decision gets a lot easier — and you keep the freedom to leave the same way you arrived.
Want early access to the preview? Try it today.