Market & Wedge

The shift

Three curves are bending at once:

• MCP is standardizing the tool layer. Connecting models to external tools used to be bespoke; it is becoming a protocol. Whoever owns the substrate those tools plug into owns the integration surface.

• Agents are moving from demo to daily. A reasoning model with no durable place to hold context or act is a party trick. The bottleneck is no longer intelligence — it is a coherent operating surface.

• Creators and brands want to build on AI, not around it. They need a place to publish, run tools, and operate that is native to how agents work.

The wedge

We do not try to be everything on day one. The entry point is the workspace primitives people already understand — pages, tasks, memory — but made fully agent-native and exposed over MCP. That gets users and agents onto the substrate. Studio then turns the substrate into a place where software gets built and shipped, which is where the moat compounds: every app deployed makes the platform more valuable as a place to operate.

Why a substrate, not an app

Apps compete feature-by-feature and get unbundled. A substrate gets more defensible as more is built on it — objects, apps, memory, and tool connections accumulate and raise switching costs. The Cloud is positioned one layer below the app fight.

Competitive landscape

The space is filling with agent and workspace plays — note-and-doc tools adding AI, agent runtimes, and MCP-adjacent tooling. The honest read: most are either an app adding an AI feature, or an agent with no substrate to stand on. The Cloud is the rare attempt at the layer underneath both. (Direct competitor names and a feature-by-feature comparison are maintained in our internal competitive analysis and can be shared in diligence.)

← Back to This is The Cloud — Seed Overview