SSH certificate
- Opens
- api-gateway, and nothing else
- Host key
- Pinned
- Expires in
Every connection gets a certificate of its own. No key to leak, nothing to rotate.
Compute
On-demand compute for agents and cloud workspaces.
Cloud Workspaces run your projects in the cloud and keep their agents working with your Mac closed. When a chat sends out a swarm, its builders run on Cortex Nodes, machines that start for the work and stop when it is done.
Your Mac
Vortex
- Editor
- Review and revert
- Chats
Cloud workspace
User Workspace 8 vCPU · 32 GB
- Files
- Terminals and builds
- The agent, working
Cortex Nodes
- Node 1
- Node 2
- Node 3started for the work
Cloud Workspaces
Your project, running in the cloud. Lid closed.
Switch a folder from Local to Cloud and its chats move to a workspace of its own, history and all. Open it from the Code tab and you are on that machine: the agent's edits land as it makes them, its commands stream in the terminal there, and a job that takes three hours keeps going with your lid closed.
- A machine of its ownStandard: 4 vCPU, 16 GB memory, 64 GB disk. Large: 8 vCPU, 32 GB, 128 GB. Never a slice of someone else's.
- Keeps goingBuilds, tests and the agent carry on with your Mac asleep, and pick up again from the desktop app like any folder.
- Stops on its ownAfter the idle time you choose, from 15 minutes to a day, it stops and keeps its disk.
- Costs nothing archivedUnused for a week, it becomes a snapshot. It comes back as the same workspace, secrets included.
Cortex Nodes
A machine for every builder, the moment it is needed.
Turn Cortex on and the commands a chat's builders run go to Cortex Nodes, isolated Linux sandboxes in the cloud, instead of your Mac. One Architect prompt can become dozens of builders working at once, and your Mac stays free. Architect chats start with it on.
See the Cortex Node →What's different
Not one agent in one sandbox.
A cloud agent is usually one task in one container, handed back as a diff. Here your folder gets a machine of its own, and a chat gets as many as its plan needs.
-
Swarms
48builders at once on the default limits
One Architect prompt becomes a builder for every part of the plan. They are placed six to a Cortex Node, and a node starts whenever the others are full. Raise the limits and it goes further.
-
Chats move
History and all.
Flip a folder between Local and Cloud. Each chat goes with its transcript and the agents it sent, and carries on under the same id. One mid-turn moves when the turn ends.
-
Your folder
Still the source.
Cloud work syncs back into the folder on your Mac, and Revert undoes it. Where you both edited a file the two are merged; where they clash, the agent's version is kept and Revert restores yours.
-
Your editor
On that machine.
Open the workspace from the Code tab and you are on it: its terminals, its files as the agent writes them, and any port it opens at localhost on your Mac.
-
Warm caches
Shared on every node.
Builders on a node share its package store, git objects and build caches, so the second install is quick.
Isolation
Every builder on its own branch.
Each builder works in its own copy of the project, on its own branch, on its node. Weave shows them side by side as they run. Follow one and the rest step back until it lands on main.
Access
Nothing long-lived on your laptop.
Workspace secrets
DATABASE_URL••••••••••••NPM_TOKEN••••••••••••SENTRY_DSN••••••••••••
The secrets your commands need, kept with the workspace and encrypted.
Limits you set
- WorkspacesHow many your account holds at once
- Cortex NodesThe most running, and an hourly spending cap
Compute grows with the work, never past the limits you chose.
Spinoza Labs
Give your agents a computer.
Cloud Workspaces and Cortex Nodes come with every plan, billed from usage.
See pricing