Application control plane for Acurast

Liskov.

Release it. Run it. Prove it.

Run private workloads across distributed compute and residential broadband circuits—without owning the infrastructure. Acurast provides hardware-backed execution; Liskov turns each release into an Application you can operate and verify.

Live Deploy and operate Applications on Acurast today.

Already building directly on Acurast? See how Liskov maps to your stack →

Secure compute
on the real edge.

Acurast is a decentralized compute network built from smartphones. It provides the hardware, secure execution, and residential network position where Liskov Applications run.

01 · Distributed compute

Compute without owning infrastructure

Use cost-efficient capacity across the Acurast network without buying servers, provisioning datacenters, or operating a hardware fleet.

02 · Private execution

Run sensitive workloads securely

Run sensitive computation and inputs inside hardware-backed Trusted Execution Environments (TEEs), isolated from ordinary phone software.

03 · Residential vantage

Measure the internet from where people use it

Run web scraping, availability and latency tests, and other network measurements from residential broadband circuits instead of datacenter IP space.

A job ends.
An Application continues.

Acurast jobs are time-boxed. Liskov keeps the release, configuration, deployments, spend, and evidence together as one Application—across every run, update, and renewal.

01 GitHub commit

Repository, ref, workflow, and commit identity.

02 Artifact

Immutable CID, digest, and build attestation.

03 Effective policy

The exact, immutable contract Liskov approved.

04 Acurast job

Schedule, assignment, processor, and chain evidence.

05 Runtime

Signed contact and capability readiness for this process.

Together, these records connect the release you selected to the runtime that reported ready—so provenance is part of daily operation, not a separate audit exercise. Inspect the proof chain →

Keep the code private.
Keep the proof visible.

Liskov protects your application on its way to Acurast, keeps sensitive material inside the job’s secure boundary, and leaves an evidence trail you can inspect from release to runtime.

JavaScript

Encrypted application delivery

Ship an encrypted JavaScript bundle that is released to the assigned job and decrypted inside Acurast’s hardware-backed execution boundary.

Verification

Verified application startup

Verify the encrypted payload, its authentication tag, and its decrypted digest before starting the application.

Secrets & logs

Secrets and logs stay protected

Keep secrets out of source and manifests, release them only to the intended job, and bring encrypted application logs back into the authorized Liskov view.

Proof chain

Evidence from release to runtime

Trace the GitHub commit, encrypted artifact, effective policy, Acurast job, processor, and signed runtime instance behind each release.

Explore the complete model in Security, privacy, and proof →

Three responsibilities.
One place to do them well.

Liskov turns Acurast compute into a product a team can release, operate, and verify together.

01Release

Know what you shipped.

Connect GitHub, choose a source or pinned release, and publish one immutable contract for what should run.

  • No long-lived spend credential in GitHub
  • JavaScript or curated native-image runtime
  • Review scope and spend before launch
02Operate

Know what needs attention.

See whether the Application is ready, progressing, or needs attention, then take the exact supported action.

  • Once, continuous, or interval execution
  • Organization-wide job capacity across Applications
  • Successor-aware updates and renewal
03Prove

Know what the evidence says.

Follow release evidence through the Acurast job and processor to the runtime that reported ready.

  • Signed runtime-instance evidence
  • Organization-scoped processor history
  • Explicit proof limits, not universal claims

The next action is part of the product.

A processor accepting a job is only the beginning. Liskov keeps the Application’s overall posture separate from the deployment, job, and runtime evidence underneath it.

1

Start with posture. See whether the Application is ready, progressing, needs attention, or inactive.

2

Follow the Action Plan. Take the supported action attached to the current decision.

3

Inspect evidence when you need it. Open timelines, logs, charges, processor history, and the proof chain.

Illustrative Console view
APPLICATION

status-worker

Ready
Desired policysha256:84…b1
Current runtimeReady · signed
Service CreditsReserve settled
Action PlanNo action required

Current evidence satisfies the desired Application state.

CommitArtifactPolicyJobRuntime

Use an Application.
Or publish one.

A marketplace for software that makes the real edge useful—private workloads, web automation, monitoring, and network testing delivered as operable Liskov Applications.

For teams

Start with working software.

Choose an attested release, add the settings and secrets it asks for, then launch it into your organization with Liskov handling the lifecycle.

  • No blank repository
  • Guided configuration
  • Proof attached
Explore the Marketplace preview
For publishers

Turn your Application into a product.

Bring an attested release, define the safe choices customers can make, and reach teams that need edge-native software. PROOF-managed offerings come first; third-party publishing follows.

  • Private source stays private
  • Verifiable releases
  • Usage-based revenue
See the publisher model

V5 is live.
See what comes next.

V5 is the current shipped contract. The roadmap advances from private networking to public ingress, then stateful Applications and Application networks, then placement and ownership control.

V5 · Shipped

Release, operate, and prove Applications on Acurast.

  • 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

Explore the scope behind every release on the Liskov roadmap →

Keep the network.
Gain an application lifecycle.

Keep the Acurast model you already know. Liskov adds release management, team operations, spend controls, and proof across the full Application lifecycle.

PROOF Liskov

Operate the Application.
Inspect the proof.

See how Liskov turns a release into a running, verifiable Application—or open Console and operate one now.