Send a small program to Bob’s provider. Get its result and check the signed exchange in your browser.
The hosted demo uses a real Froglet node. The separate playground runs both sides locally in your browser.
Your browser compiles the program and signs the request. Bob’s native runtime executes it with fuel, memory and time limits. Your browser checks his receipt against the returned result.
Try new numbers. You can also change the program before sending it.
This AssemblyScript function compiles in your browser. Bob runs the compiled WebAssembly program. Try replacing a + b with a * a + b.
Use sample data. Your compiled program and input go to the demo server, which keeps job records.
Query a tiny catalog of invented terminology. The blood label has two targets, so you can inspect the ambiguity.
Run an infinite loop. Bob stops it within the execution budget and signs a failure receipt.
Connecting to the public demo…
This JSON can also be pasted into the standalone record verifier. It contains public signed records, not a private signing key.
The request stays in this browser session so an interrupted job can be recovered.
An already submitted job may still have completed. Discarding its reference does not cancel it or replenish the shared allowance. A new run requests new work.
Each program has at most 2 seconds, 8 MiB of memory and 50 million fuel. The public beta has a finite shared allowance. Calls may be refused when capacity is busy or spent.
The program can change for one question. The host keeps its admission rules, resource limits and signed records.
| You can try | What happens |
|---|---|
| Your program and JSON input | The browser compiles the function. The remote node runs its exact bytes and reports their hash. |
| A selected terminology query | The provider returns only the published synthetic snapshot and selected fields. |
| An infinite loop | The execution budget stops it. You can inspect the signed failure record. |
| A network interruption | Retry the saved job. Recovering an accepted result does not request another deal. |
| The signed evidence | The browser verifies the provider’s commitments and the result hash. Signatures do not establish scientific truth or physical execution. |
This beta demonstrates free Wasm jobs and a synthetic catalog. Paid operation, GPU work, arbitrary containers and sustained production capacity are separate work.
The same native Froglet runtime is available for MCP clients and HTTP integrations. Providers choose their own access policy; invitation-only hosting is an option, not a requirement of Froglet.