CanopyRig · preview

The platform that builds and runs platforms, for the agentic web.

Software is about to be written, shipped and operated by agents working beside people. The clouds we have were made for people clicking. CanopyRig is a service that takes a platform's blueprint and builds it from source, runs it as WebAssembly, and gives every agent and every person one identity, one line of consent, and one record of who did what for whom.

From source, every timeNo images to trust. Rig builds each release from the commit, tests it, and only then places it.

Gears, not containersEvery service is a WebAssembly gear. A whole gearbox for a customer costs a spin-up, not a fleet.

Agents are people hereAn agent signs in, is bound by consent, and can stand for a person only as far as that person allows, retractable at any time.

How it works

Canopy holds the blueprint. Rig reads it, builds every component from source and places it. Spindle runs the gears in gearboxes, one per platform, and the core is each platform's own identity: people, agents and services alike.

Canopy: The blueprint. Organisations, components, who holds what. Infrastructure as code for the whole estate, including the approvals.
Rig: The builder. Watches the forges, builds from source, runs the lane, checks what each build ships against published advisories, deploys through the host, and asks for every principal on the record.
Spindle: The runtime. Wears WebAssembly gears in gearboxes; a gear's callers are resolved against its own platform's core.
Core: The identity provider each platform owns. Passkeys for people, keys for agents and services, features by consent, delegation with a line the human draws.

Already true

It runs itself. CanopyRig's own core, head, builder and blueprint are built and placed by Rig from their repositories, with no hand on a server.
A platform is live on it. DCC Platform, the first platform, runs in its own gearbox with its own core, and reads its blueprint from Canopy as a customer would.
Built with an agent, not just for agents. The stack is written by the founder working with an AI agent that holds its own principal, bound by consent and recorded on every act.
Nothing hidden. Every key is asked for, approved by a person, short-lived at bootstrap and rolled after deploy. There is no admin back door by design.
Dependencies watched. Rig checks the crates each build ships against published security advisories. It is a best-effort report, not a guarantee.

Why now

Agents can already write most of a service. What they cannot do on today's clouds is be trusted with one: hold an identity, ask for permission in the open, act for a person within a line that person can move, and leave a record a company can stand behind. The platforms that win the next decade will treat agents as accountable actors, not as scripts with a token. That is the whole of CanopyRig's design, and it is the reason it was built from the identity outward rather than from the container inward.

Who is building it

Syamasundara Mishra, founder. Built DCC Platform for a production studio's pipeline, then the stack under it when nothing existing would let an agent and a person share one deployment honestly. CanopyRig is a Multi Threaded Pty Ltd company.

The round

CanopyRig is opening conversations for its seed round, with a path to Series A once the first outside platforms are running. The product is live, the first platform is on it, and the next step is the team to take it to many. If you invest in infrastructure for the agentic web, join the list as an investor and the founder will be in touch.

Join as an investor