Welcome to Link Loom Cloud
Why we built an infrastructure platform around an open-source runtime — and what you can do with it today.
Every product team we know has built the same five systems at least twice: a boot sequence, a config loader, a background job runner, a file store, an identity layer. None of those systems were the product. All of them delayed it.
Link Loom Cloud is our answer to that repetition. It is infrastructure as a platform: a deterministic Node.js runtime you can read on GitHub, thread-isolated workers for the heavy and the untrusted, secrets resolved at runtime through Cloud Vault, backbone services for identity, notifications, storage and observability — and an App Engine that stores, builds, versions and serves real React apps.
The parts, briefly
The Runtime SDK is the foundation and it is Apache-2.0. One loom.ignite() call boots your service the same way every time: dependencies resolve, infrastructure connects, adapters load, then traffic. No global singletons, no decorator magic — an explicit dependency graph handed to every module.
Workers run in dedicated V8 isolates with a strict lifecycle state machine. When a worker terminates, the operating system reclaims all of its memory — we call it the Guillotine, and it means the ten-thousandth job runs like the first.
Cloud Vault keeps your repositories free of secrets. Environments are versioned trees fetched at ignite time, held in memory, audited on every read.
App Engine and App Studio close the loop: real React source trees edited in a cloud IDE, built with Vite server-side, frozen as immutable versions, served to any host surface.
Where this is going
The platform already runs the StoneOS family of Blackwood Stone Holdings products in production — identity, retail, fintech rails, IoT. This site, this blog and the cloud console are the start of opening that backbone to every team that would rather build their product than their plumbing.
Install the SDK, ignite a service, and tell us what you are building.
npm i @link-loom/sdk
