Skip to main content

Deploy like a cloud. Verify what actually ran.

Liskov helps you run an application on the Acurast network without managing the deployment machinery yourself. Acurast supplies phones with trusted execution environments (TEEs): hardware-isolated places where your code can run away from a conventional cloud server.

Start with Deploy from GitHub when you are bringing your own repository and want a verifiable release trail. Publication is enabled only for eligible organizations, so check the availability note before preparing a release.

Release boundary

Marketplace launch, Uptime Prober, plan and terms acceptance, and Stripe USD checkout are still release-gated. Their current production use is limited to internal first-party engineering acceptance. Do not enter payment details or offering secrets until the capability matrix classifies the path as supported customer behavior.

A supported launch creates a Liskov Application. The Application keeps your desired configuration, immutable artifact evidence, deployments, logs, billing, and lifecycle together. Liskov manages the Acurast jobs needed to keep that intent running over time.

What v1 gives you​

  • A proof trail from a GitHub commit to the artifact, effective policy, Acurast job, processor, and runtime evidence.
  • Managed variables and secrets, with job-bound delivery.
  • Read-only visibility into available, reserved, and used USD Service Credits. Customer checkout is not yet a supported way to add credit.
  • Clear Application status and an Action Plan when your input is required.
  • Time-boxed jobs, deliberate updates, pause/resume, bounded retry, and safe retirement.

Liskov coordinates execution; Acurast owns the external processor network and job schedules. Existing Acurast jobs are not ordinary virtual machines that Liskov can stop instantly. The docs call out this boundary whenever an action has a delayed or limited effect.

Find your next step​