News for hackers. Stuff that matters.
Re:Show HN: Pollen – distributed WASM runtime, no control pl... by sambigeara on Sunday May 03, 2026 @02:20AM (#47993937)
Hypothetically, yes! If your workloads are bounded and can compile to WASM, break them into logical units which would benefit from individual scalability, and `pln seed` them into the cluster. Ingress can be from any node. Any workload that doesn't suit the WASM seeds can be `pln serve`d on dedicated hosts.

You could also establish a dev cluster (/environment) where all devs run a local instance. You can iterate on services quickly, expose ngrok-like capabilities by exposing a local dev instance of a server with `pln serve 8080 test_server` for your colleagues to consume with `pln connect test_server`, etc, etc.

A more whacky idea I've not been able to get out of my head which might become possible as the access story solidifies: imagine a customer could access a controlled subset of your companies offering by having a delegated node, running in their own infrastructure, that ultimately you can delegate and revoke at any given time.

Re:Show HN: Pollen – distributed WASM runtime, no control pl... by ivere27 on Sunday May 03, 2026 @05:45AM (#47995260)
good to hear that. there are plenty of idle cpus in a company. then, we can use it safely in sandboxing wasm.