Liskov and Acurast

These products meet at explicit seams; they are not synonyms.

Liskov

Liskov is the customer control plane. It owns organizations, Applications, repository release evidence, effective policies, managed configuration, managed custody, USD Service Credits, posture, Action Plans, lifecycle, and proof views.

The control plane also contains a first-party Marketplace path, but customer launch remains release-gated and limited to internal first-party acceptance.

Liskov does not execute your process on its own servers and does not provide a general hosted HTTP or SSH ingress product in v1.

Acurast

Acurast is the execution network. Its processors are phones that accept time-boxed jobs and run them in trusted hardware. Acurast owns job registration, schedule, market assignment, processor identity, and network settlement facts.

A curated Liskov offering can use an Acurast facility such as WebView or Tunnel. That capability belongs to the offering/network boundary, not every Liskov workload.

External services

GitHub supplies source and workflow identity; IPFS identifies artifact bytes; Telegram and your APIs provide application outcomes. Each remains independently operated, priced, and trusted. Stripe is the intended USD funding processor, but customer checkout and Service Credit issuance remain release-gated.