Solutions
One machine.Eight teams, eight kinds of work.
Same project, same connectors, same memory. Underneath, eight very different jobs. Each team writes the skills for its own work, and nobody has to build a second system.
Pick the team whose week you want back
- Every session
- Its own cloud computer, on its own branch
- Work lands
- As a change request
- Merge
- Default-deny for agents
- Approval gates
- Off until you set them
01By team
Start with the work. Not the platform.
Each page is about one team's real week: what it can hand off, which connectors matter, and what the output looks like when it comes back.
- 01SalesResearch, drafts and CRM cleanup, held for your yesOpen
- 02MarketingProduction work in your voice, because the voice is a fileOpen
- 03ProductFeedback turned into specs, with the evidence attachedOpen
- 04EngineeringReproduce it, patch it, open the change requestOpen
- 05FinanceThe close, the reconciliation and the variance note, with the working shownOpen
- 06PeopleScheduling, kits and onboarding, never the hiring decisionOpen
- 07ITRunbooks that run, and a platform that passes your reviewOpen
- 08Data ScienceA real machine, a real query, an analysis you can re-runOpen
8
Teams, one project
1
Machine per session
1
Branch per session
3,000+
Apps in Easy connect
02What never changes
Eight kinds of work. One set of rules.
The pages differ because the work differs. The rules underneath are identical, so you only need to read them once.
01
A session is a machine
Every session boots its own disposable Linux computer and cuts its own branch. Thousands can run side by side on one configuration without touching each other. The machine is real: the agent gets a shell, a filesystem and the network.
02
Work lands as a change request
Anything an agent means to keep is committed on the session branch and proposed back toward main. Merge is default-deny for agents. An admin can grant project.cr.merge in your project config, and widening that grant is itself a reviewed change.
03
Approval gates are off until you set them
The shipped default is permissive: an action runs unless you said otherwise. Set Ask on what should pause and Block on what should never happen, per action or with a pattern rule that can read the arguments of the call.
04
Connector credentials stay out of the machine
The sandbox carries one project-scoped Machine token and no third-party keys. The real credential is decrypted server-side and attached to the outgoing call. A runtime secret you choose to grant is different: it is a real environment value the agent can read.
05
Everything is a file you own
Agents, skills, connectors, triggers and memory are text in a git repo. You can read the whole company, diff what changed, and roll it back. Machine keeps the way you operate visible and reviewable.
Get started
Start with one team.The rest is the same project.
One governed platform for every team. Any model, your keys. Every action recorded.
- One machine per session
- Lands as a change request
- Every action recorded