Liskov roadmap

One useful capability.
One complete release.

V5 is live. Each version that follows adds one coherent customer outcome across policy, runtime, Console, CLI, proof, and rollback—without quietly changing what an existing release means.

V5 shipped Release it. Run it. Prove it.

Explore the roadmap ↓ Open Console

Release sequence

What is live.
What comes next.

Versions describe durable product contracts, not quarters on a calendar. The sequence is intentional; exact timing follows complete evidence.

V5 Shipped

The application control plane

Release, operate, and prove Applications on Acurast.

V5 establishes the complete path from source or pinned artifact to a running, observable, spend-bounded Application.

  • JavaScript and curated native-image runtimes
  • Once, continuous, and interval execution
  • Organization-wide job slots with simultaneous or phased starts
  • Managed secrets, logs, Service Credits, and proof chain
  • Managed Runtime SSH for native workloads

Runs todayBatch jobs, bots, scrapers, converters, and benchmarks in eleven languages.

V6 Next

Private networking

Reach your own service, on your own fleet, privately.

Publish a service to your own Tailscale tailnet and reach it — or its shell — without exposing anything to the public internet. Aim the deployment at processors you already own, and pay for it from your own account. V6 leads because the provider lifecycle it needs is the one Liskov already runs.

  • Private HTTP endpoints on a customer-owned Tailscale tailnet
  • Bring-your-own Tailscale Runtime SSH
  • Allow or exclude processors by manager and by operator
  • Every placement explains which processors it admitted, and why
  • Fund deployments from your own ACU account, through your own signer

Becomes possibleA private ClickHouse on your own network, reachable by your own tools, paid for from your own wallet.

V7 Planned

Public ingress

Publish a service to the internet.

Give an Application a public HTTP, TCP, or UDP endpoint through a managed tunnel provider. Liskov owns the integration, attachment, evidence, and teardown; the provider carries the traffic.

  • Acurast Tunnel and Cloudflare Tunnel endpoints
  • HTTP, TCP, and UDP services
  • Endpoint protection stated honestly — public, provider-gated, or application-authenticated
  • One stable public identity across job replacement

Becomes possibleA web server, a static site, or an LLM behind a public URL.

V8 Planned

Stateful Applications

Keep durable data with the Application lifecycle.

Move beyond explicitly stateless execution so databases, queues, durable agents, and long-lived services can recover safely across jobs.

  • Application-managed durable volumes
  • Bounded snapshots and restore
  • State-aware update, recovery, and retirement
  • Clear custody, retention, and spend boundaries

Becomes possibleWordPress, a Minecraft server, a time-series store, or an AI agent that remembers.

V9 Planned

Application networks

Let related jobs discover and trust each other.

Give clustered Applications a first-class identity and private network model rather than leaving peer discovery and membership to each workload.

  • Named cohort identity and membership
  • Authenticated private peer connectivity
  • Lifecycle hooks for joining, backup, and restore
  • Served peer addresses — never a hard-coded one

Becomes possibleA three-node CockroachDB, Postgres with standbys, a replicated object store or search cluster.

V10+ Horizon

Placement and ownership

Choose where jobs run, and who holds the keys.

Later complete releases give an Application finer control over its processors and its custody — each one its own version, none folded into an oversized release.

  • Country and region placement
  • Spread across distinct operators, networks, and locations
  • Liveness requirements and preferred processors
  • Signer-mediated application secrets
  • More Runtime SSH and access providers
  • Marketplace and agent-native workload surfaces

How a version ships

Complete means
more than code merged.

A release is real only when the entire customer path moves together.

01

One outcome

A version starts with one customer capability, not a bag of unrelated fields.

02

Exact contract

Manifest, effective policy, defaults, digests, and rejected inputs are frozen together.

03

Full proof

Publication, execution, failure, closeout, restart, rollback, and live canaries all pass.

04

Every surface

Runtime, Console, CLI, examples, and public docs become usable in the same release.

The release promise

Old versions stay
exactly what they were.

When a new capability changes what an Application may declare or how it behaves, it gets a new integer version. Existing Applications keep their original contract and can be read, operated, and rolled back safely.

That makes future releases smaller, easier to verify, and less likely to surprise a running workload.

V5 is live

Build on what
has already shipped.

Start an Application today, then follow complete capabilities as they join the platform.

Deploy an Application → See pricing