Liskov, Acurast, and Baran

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

Liskov

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

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.

Baran

Baran is a separate ingress product. It can route inbound work to supported Acurast jobs through its own contracts and trust model. Baran is not the Liskov v1 HTTP/SSH hosting layer, and adding Baran is not a hidden prerequisite for either Liskov quickstart.

Use the Baran documentation when your independent task is ingress. Do not copy Baran configuration into a Liskov manifest unless a supported integration guide explicitly joins the two.

External services

GitHub supplies source and workflow identity; Stripe processes USD funding; IPFS identifies artifact bytes; Telegram and your APIs provide application outcomes. Each remains independently operated, priced, and trusted.