Live Infrastructure Across Europe • Portugal • Finland • Bulgaria
Digital Frontier
Sovereign EU or global placement · Akash-compatible

Sovereign European, or global. You choose.

Tag a workload sovereign and it’s pinned, fail-closed, to EU infrastructure we own — we refuse to provision rather than place it outside the jurisdiction you set. Or run it globally on our Akash-compatible edge. Same platform, same deploy, your call — with the performance, software-defined reliability and low cost of infrastructure we operate.

Open Console→
—
Deployments
—
Customers
0
Regions
0
Countries
0
API dialects
EU LAW
Based
//compatibility

Two API dialects. One edge cloud.

Digital Frontier doesn't ask you to learn a new API. It speaks two dialects you already know — Akash today, Latitude.sh in preview — so your existing code, SDKs and tooling keep working.

Live
Akash-compatible

Your Akash workflow, on our edge

Our European providers are live on Akash today — deploy to them from the official Akash Console at console.akash.network and pick a Digital Frontier provider. Our own console is coming.

Explore the platform→
Latitude.sh
Preview
Latitude.sh-compatible

Your Latitude.sh code, unchanged

A faithful implementation of the Latitude.sh API — provision workloads, manage projects and SSH keys with a drop-in Python SDK. Currently in preview.

See the one-line switch→
//products

One edge cloud. Composable products.

Explore all products→

Orchestration, Python-native workflows and zero-trust networking — each built on the same high-performance, geo-redundant EU edge, reachable through the API dialect your stack already speaks.

Live

Cloud

Sovereign European cloud — deploy today, Akash-compatible

Learn more
Preview

Core

Declarative multi-backend orchestration from one manifest

Learn more
Preview

Flow

Distributed Python pipelines — no YAML DAGs

Learn more
Preview

Flow Scripts

Zero-credential execution boundary for workflow code

Learn more
Preview

Flow Sandbox

Isolated microVM workspaces for untrusted code

Learn more
Preview

Gateway

Declarative multi-region public gateways with edge policy

Learn more
Preview

Mesh

Multi-region service mesh — peered, authorized, mutually encrypted

Learn more
Preview

Sentinel

AI-driven penetration testing with triaged, verified findings

Learn more
Preview

Redoubt

Witnessed, non-bypassable channels between untrusting parties

Learn more
//how it works

Declare the workload. We run it, in Europe.

A single manifest describes your compute, placement, GPUs and telemetry. The same spec deploys to any Digital Frontier region.

Declarative by default

Describe an entire workload in a single manifest — image, resources, networking and TLS. Version it, review it in a pull request, ship it. The same spec deploys to any Digital Frontier region.

One manifest. Boot, scale, destroy — no console clicking required.

deploy.yaml
YAML
version: "2.0"

services:
  api:
    image: myapp:latest
    cpu: 2
    memory: 4Gi
    replicas: 3
    expose:
      - port: 443
        as: 443
        proto: https
        tls: auto

European by default

Pin workloads to the regions you choose — Portugal, Bulgaria, Finland — with data residency declared in the manifest, not promised in a policy PDF. Every byte stays under EU law.

Data residency is part of the spec, and we favour renewable-powered regions.

placement.yaml
YAML
placement:
  regions:
    - pt-lisbon
    - fi-helsinki
    - bg-sofia

  data_residency: EU
  jurisdiction: eu-only

  power:
    prefer: renewable

GPUs on demand

Attach a GPU to any service and scale it from zero. Pay for the seconds you use, on renewable-powered European hardware — no reservations, no idle bill.

T4A100
gpu.yaml
YAML
services:
  inference:
    image: vllm/vllm:latest
    gpu:
      model: A100
      count: 1
    autoscale:
      min: 0
      max: 64
      target_gpu_utilization: 80

Observability included

Logs, metrics and traces ship out of the box — export to Prometheus, keep what you need, drop the rest. Debug production in real time instead of guessing.

Every deployment instrumented from the first request.

observability.yaml
YAML
observability:
  logs:
    level: info
    retention: 30d
  metrics:
    export: prometheus
  traces:
    enabled: true
    sampling: 0.1
//runs on itself

We run on what we sell.

See it live

No customer logos yet — we’re early. But every service you’re evaluating already runs our own company on our own European edge. Here’s what’s live today.

This website

Served from our own European nodes across three regions — not a third-party host.

Our console & API

The same console and Latitude-compatible API we hand customers runs our own deployments.

Pentested every release

An automated security gate scans each release, backed by a daily self-scan — before anything ships.

Private zero-trust mesh

Internal traffic rides an encrypted mesh. No public SSH, no exposed control plane.

Single sign-on

One self-hosted identity provider secures every internal tool we run.

Live status page

Every service's uptime is published and independently checkable — see for yourself.

status.digitalfrontier.so
//launch partner
Kahea AI
“We’re moving our voice infrastructure onto Digital Frontier’s European edge — EU data residency and multi-region failover in one platform, without the hyperscaler bill.”
Sergio Charrua · Founder, Kahea AI
//migration
Preview

Switch from Latitude.sh in one line

Like changing the base URL on an LLM client — our Python SDK is built as a drop-in replacement for the Latitude SDK. Keep your code; just point it at Digital Frontier. The Latitude.sh-compatible API and SDK are in preview.

  • Wraps the upstream latitudesh-python-sdk — servers, projects and SSH keys behave exactly as before.
  • The constructor is the only difference: pick the provider, point at our endpoint, pass your token.
  • Catalog enums are permissive, so our regions, plans and OS images pass straight through.
View the SDK on GitHub →Read the API docs
migrate.py
Python
# pip install edge-provider-sdk
 
- 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 is identical to the Latitude SDK
instance = client.servers.create(...)
//why digital frontier

An edge cloud you can actually reason about.

One operator, one jurisdiction, renewable power, and the APIs you already know. No abstraction layers between you and your workloads.

Renewable

Powered by renewables

Where the local grid allows, we favour datacenters running on 100% renewable energy — lower-carbon compute, with the cost savings passed through to pricing.

Jurisdiction

European by default

Every workload runs in an EU region — Portugal, Bulgaria, Finland — governed entirely by EU law.

Compatible

APIs you already know

Our Latitude.sh-compatible API is in preview, so there's no new SDK to learn. Already on Akash? Deploy to our providers from the official Akash Console today.

Capacity

Compute sized for real work

Generous vCPU, memory and storage — the capacity you'd provision on Latitude.sh, greener.

Transparent

Live network status

Real capacity, uptime and region health — published openly, not buried in a status page.

Surface

See the full API surface

Both dialects, the SDK, and the catalog model behind every workload you provision.

Explore the platform →
Europe at night from space

Regions in Portugal, Bulgaria & Finland

Run by us, not resold. Three independent European regions, each operated end to end by our team — from rack to API.

//infrastructure

Our own edge — not someone else's cloud.

Digital Frontier Cloud is not a reseller. We run our own edge across Europe — independent regions in Portugal, Bulgaria and Finland, governed entirely by EU law.

View live status →Explore the infrastructure
//the economics

High performance, priced to move.

European, renewable-powered infrastructure — priced below the hyperscalers, with no egress toll. Real figures from our pricing, not a teaser rate.

Edge vs. hyperscaler
3×cheaper compute

Edge compute at $0.047/CPU-hr versus $0.142 on hyperscaler on-demand — a third of the price, on renewable power.

No egress toll
Free
egress

On Akash & DigitalFrontier Edge. Hyperscalers bill $0.12–0.16 per GiB.

Renewable
100%

Our Portugal & Finland regions run on renewable energy — shown per region, not offset accounting.

Billing
Per-second

Scale to zero and pay for the seconds you use — no idle bill, no minimum commitment.

Jurisdiction
EU law

One operator, one jurisdiction — end to end, outside the reach of non-EU data-access regimes.

See the full pricing→
//console

Everything the API does, with a UI on top.

Prefer to click? Our web console gives you the full platform — no API call required. Pick the complete Digital Frontier console or the Akash-compatible one; both use the same account.

Provision workloads

Spin up workloads across our regions, pick a plan and OS image, and watch them boot.

Tokens & SSH keys

Mint API tokens, manage SSH keys and organise work into projects — the same model the API exposes.

Usage & health

Track capacity, billing and region health from one place, without leaving the dashboard.

//company

Performance-first cloud,
engineered in Europe.

Digital Frontier Unipessoal LDA designs and operates Digital Frontier Cloud — a sovereign, EU-operated neocloud — alongside the renewable-powered edge and developer tooling that runs on it.

The platform speaks the dialects teams already know — Latitude.sh- and Akash-compatible APIs and an open-source SDK — so there's nothing new to learn.

Renewable-poweredCloud computeLatitude.sh-compatibleAkash-compatible

Provision your first workload.

Deploy a workload to our renewable EU edge from the official Akash Console — or talk to us about migrating a Latitude.sh or Akash workload.

Open Console →