Compute capacity
The decentralized substrate where work runs.
- Phone processors
- Hardware-backed TEEs
- Residential circuits
- Open compute market
Liskov features
Compute is the raw material.
Applications are the product.
Acurast supplies distributed processors, hardware-backed execution, and residential broadband circuits. Liskov adds the release, operation, placement, networking, state, billing, and lifecycle layers that make them useful to a team.
From capacity to product
Silicon is only
the beginning.
Raw compute competes on supply and price. The durable value sits in everything that lets a customer release, connect, recover, pay for, and trust an Application.
The application layer
The controls and evidence that turn capacity into a product.
ReleaseSecure deliveryPlacement
NetworkingStateSecrets
LogsBillingLifecycle
Applications
Workloads people can deploy, operate, and depend on.
- Private workers
- Web intelligence
- Data services
- Agents and clusters
High-value enablers
Everything between code
and a reliable product.
Available
Advancing
Roadmap
Available01
Release authority
Bind source or a pinned artifact to one immutable release, then retain the commit, workflow, digest, policy, job, processor, and runtime trail.
Know exactly what shippedAvailable02
Private execution
Deliver encrypted JavaScript and native workloads into hardware-backed execution, with managed secrets released only to the intended job.
Protect code and inputsAvailable03
Managed operation
Replace raw job state with Application posture, Action Plans, logs, Runtime SSH, renewal, updates, and safe retirement.
Know what needs attentionAvailable04
Teams and spend
Share organization-wide job capacity, set spend bounds, use USD Service Credits, and inspect reserves, final charges, and billing history.
Operate without token plumbingAdvancing05
Processor intelligence
Liskov qualifies processor evidence and improves selection automatically. You describe the workload—not an internal reliability score.
Better decisions without more knobsRoadmap06
Placement and spread
Express real resource, geography, and distribution needs; let Liskov choose and spread jobs at the last responsible moment before spend.
Put work where it performsRoadmap07
Durable state
Keep Application-scoped encrypted data, run bounded snapshots, and restore before serving so a replacement does not mean starting empty.
Let data outlive a jobRoadmap08
Cohorts and private networks
Give every member stable identity, peer discovery, private connectivity, and lifecycle hooks for joining, draining, and replacement.
Turn parallel jobs into a systemRoadmap09
Provider-backed ingress
Attach named HTTP, TCP, and UDP endpoints while access providers carry public traffic and Liskov keeps the Application lifecycle coherent.
Make edge services reachableAvailability is deliberate: green capabilities are in the current platform; advancing and roadmap capabilities ship only with their complete contract, runtime, operating path, and proof. See the release sequence →
Application patterns
The feature matters when it
changes what you can run.
These patterns are drawn from the application shapes Liskov is being designed and tested against. Some run on today’s foundation; others depend on the roadmap capabilities named on each card.
Build now
Residential web intelligence
Scraping, availability checks, screenshots, price monitoring, and regional network tests from residential broadband circuits.
Puppeteer · Uptime probes · Web testing
- Scheduling
- Parallel jobs
- Residential vantage
Build now
Private workers and pipelines
Fetch-transform-deliver jobs, bots, media conversion, WebAssembly, and sensitive automation protected through delivery and execution.
Video transcode · HEIC conversion · Bots
- Encrypted code
- Managed secrets
- Proof chain
Expanding
Long-running agents
Autonomous assistants and local model services with private inputs, durable memory, operator access, and a recoverable control surface.
OpenClaw · Hermes · Local LLM services
- State
- Runtime SSH
- Ingress
Expanding
Search, vectors, and metrics
Data services that persist or rebuild safely, restore before serving, and use placement to match memory, storage, and network needs.
Qdrant · ClickHouse · VictoriaMetrics · InfluxDB
- Durable state
- Restore
- Placement
Expanding
Distributed data systems
Quorum, primary-standby, and self-restoring databases that keep stable member roles while processors and jobs are replaced.
CockroachDB · rqlite · PostgreSQL · Typesense
- Cohorts
- Private peers
- Lifecycle hooks
Expanding
Edge services and storage
Replicated object storage, APIs, content systems, and multiplayer services spread across independent processors and reachable through providers.
Garage S3 · PostgREST · WordPress · Game servers
- Spread
- Cohorts
- Ingress
Why Liskov matters
The value compounds
above compute.
Cloud platforms became valuable by making infrastructure programmable, connected, observable, billable, and dependable. Liskov applies that lesson to decentralized compute.
- 01Execute
A job can run code on a processor.
- 02Operate
An Application persists across time-boxed jobs.
- 03Coordinate
Placement, state, and cohorts turn jobs into systems.
- 04Distribute
The Marketplace turns working systems into products.
PROOF Liskov
Bring the workload.
Skip the infrastructure team.
Start with today’s application platform, or see the complete capabilities we are building next.