Live Infrastructure Across Europe • Portugal • Finland • Bulgaria
Digital Frontier
Products
Digital Frontier CloudLive

The sovereign cloud, on infrastructure we own

Sovereign European container compute — reached through the Akash and Latitude APIs you already use, in EU-only regions. No rewrite.

deploy.yaml
yaml
# Your existing Akash SDL, unchanged — runs in the EU.
version: "2.0"
services:
  web:
    image: myorg/api:1.4.2
    expose:
      - port: 8080
        as: 80
        to: [{ global: true }]
profiles:
  compute:
    web:
      resources:
        cpu: { units: 2 }
        memory: { size: 4Gi }
        storage: { size: 8Gi }
  placement:
    dc:
      pricing:
        web: { denom: uakt, amount: 1000 }
deployment:
  web:
    dc: { profile: web, count: 1 }

Digital Frontier Cloud features

Akash SDL

Akash-compatible

Bring your existing Akash SDL — it deploys unchanged, no rewrite.

version: "2.0"
services:
  web:
    image: myorg/api:1.4.2
    expose:
      - port: 8080
        as: 80
        to: [{ global: true }]

GPU and CPU compute in one catalog

One catalog of instance families — every plan a versioned template.

GPU
ct.g.*

NVIDIA GPU families for training and inference.

committed SDL template per plan

Latitude REST

Latitude-compatible

A JSON:API dialect existing bare-metal-cloud clients already speak — point them at the endpoint.

POST /api/v1/servers
{ "data": { "type": "servers",
  "attributes": {
    "project": "proj_8f2a…",
    "plan": "ct.c.medium",
    "site": "global",
    "hostname": "web-1" } } }

Europe, end to end

Compute runs in EU regions — and the console and API you reach it through, on .so and .network, are European-hosted too.

Lisbon
Portugal
Sofia
Bulgaria
Helsinki
Finland
.so · .network — European-hosted endpoints

Python SDK

one client

Point edge-provider-sdk at Digital Frontier and your Latitude tooling just works.

from edge_python_sdk import EdgeClient

client = EdgeClient(
    provider="digital-frontier",
    base_url="https://api.digitalfrontier.so/v1",
    bearer="df_…")

server = client.servers.create(
    data={"type": "servers", "attributes": {
        "project": "proj_8f2a…",
        "plan": "ct.c.medium",
        "site": "global",
        "hostname": "web-1"}})

One identity across console, API and SDK

Single sign-on ties every surface together. Your token is forwarded downstream, never exchanged for a platform-held credential, and stripped from logs and traces.

Console
REST API
Python SDK
Single sign-on
one identity
European regions onlyAkash-compatible APILatitude-compatible dialectGPU + CPU catalogKey-only SSHSingle sign-on

Deploy today

Our providers are live on Akash now — deploy from the official Akash Console and run on our European regions.

Key-only SSH

Register an SSH key and launch. No passwords, and keys never leave your control.

One API, two dialects

Akash SDL or the Latitude REST shape — the same platform answers both, so your existing tooling ports over.

Typed, permissive catalog

client.catalog.plans()/sites() list what's deployable — our slugs pass through without SDK-side enum rejects.

Build on Cloud.

Open the console and deploy to the sovereign EU edge in minutes.