For Acurast builders
You already ship to Acurast.
Hohmann makes it a deploy.
You run jobs inside TEEs on real phones, on residential broadband — you know the destination. Hohmann turns the raw path to it — extrinsics, funding, sealed secrets, encrypted logs, a public front door — into one policy you declare once and repeat from CI.
Early access The Hohmann plugin is rolling out now. APIs and pricing may change.
New to Acurast? Start with what makes this possible →
01 — The gap
You can register a job by hand. Running it as production — repeatable, with secrets that arrive sealed, logs you can read, and a public front door — is a fresh ceremony every time:
01 · orchestration
Pin the artifact, fund the job, match processors, pass admission — every launch is a string of extrinsics, wallet prompts, and failure modes.
02 · observability
Your code runs on a phone you'll never meet — you need its logs. Pull them in the clear and your sealed app leaks through its own diagnostics; Acurast won't encrypt them to you for free.
03 · secrets
The job needs its API keys at runtime — but Acurast gives you no sealed path to deliver them. Roll your own, or let credentials ride in the open.
02 — Raw Acurast vs Hohmann
Everything you'd hand-roll on top of Acurast — declared once, and handled for you.
hand-rolled · every launch
acme-api · one policy, from CI
03 — The policy
One JSON file in your repo declares the whole launch — runtime, schedule, secrets, logging, ingress. Hohmann turns it into a plan you can read before a single token moves — and backs it with preflights, replacement holds, and post-mortem diagnosis.
acme-api · read it before you pay
04 — The platform
Each piece replaces a manual ceremony with something declared, auditable, and repeatable — what it takes to run TEEs on home internet like production infrastructure. Eight are live today; the ninth is on the slips.
One commit declares the deployment — reviewable, repeatable, OIDC-pinned. No key files.
Encrypted to the job's enclave before they leave you — no “store now, decrypt later”.
Encrypted end-to-end, from inside the seal to your terminal — readable by you alone.
A public HTTPS front door — one line of policy.
Your bundle is plaintext in exactly two places: your repo and the TEE. Ciphertext everywhere between.
Replicas, windows, durations, rolling replacements — declared once, kept on time.
Budgets, quotes, and settlement in USDC — Hohmann does the token dance, your books never see it.
Caps, preflights, and explicit --yes-spend gates — nothing spends while you're not looking.
Bring a full proot image — your CI builds it, Hohmann serves it straight to the phone.
05 — Speaks Acurast
No new mental model. The policy compiles down to the Acurast concepts you already reason about — Hohmann just stops you hand-tuning them per launch.
01 · processors
minReputation, replica counts and matching live in policy — declared, not negotiated by hand each time.
02 · quota
Set the job's network-request quota in policy; Hohmann provisions the job to match, so admission doesn't surprise you.
03 · custody
Every job is tied to a consumer wallet — Hohmann runs one custody identity for your deploys, so matching, admission and settlement all line up. No per-launch key juggling.
06 — Migration
No rewrite, no new SDK. Hohmann imports your existing app straight from GitHub, pins the artifact, and stands the launch up as a policy you can review before a single token moves.
07 — Launch
Install the PROOF CLI, publish your policy, preflight, launch. Artifacts, secrets, logs, and routing are handled for you.
acme-api · application-policy.v3
The full walkthrough, policy reference, and concepts live in the docs.
Read the docs →