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
V6 Next

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
V7 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
  • Placement spread and topology controls
  • Lifecycle hooks for joining, draining, and recovery
V8+ Horizon

More edges, more control

Open Applications to more networks and ownership models.

Later complete releases expand how Applications are reached, placed, accessed, funded, and composed—without folding every idea into one oversized version.

  • Provider-backed HTTP, TCP, and UDP ingress
  • More Runtime SSH and access providers
  • Advanced processor placement and intelligence
  • Bring-your-own custody and secret authority
  • 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