What Jetsyn is
Jetsyn is an AI employee that does the work, plus an AI workspace it works in: your own secure Jetsyn Cloud cell, where your company's data, memory, and AI workers live, reached from the CLI and the web app.
Two things, inseparable: an AI employee that does real, revenue-focused work, and an AI workspace where you and that employee build your company on one shared store. An employee with no workspace is a chatbot. A workspace with no employee is just storage. Together they are your company, run by AI.
An AI employee and an AI workspace#
The employee is an autonomous AI worker. It does the job end to end, on request and on its own, and pulls in specialist sub-agents when a task needs them. The workspace is the shared place your people work with it: your company's memory and IP, your team, and the surfaces you reach it through.
You do not buy a pile of features. You hire a worker and give it a place to work. Everything else in these docs is how that place is built and how you reach into it.
Your secure Jetsyn Cloud cell#
The workspace is delivered as a cell: a private, isolated container in the cloud that holds your data as files, your memory, and your employee. Each customer gets their own cell. Nothing is shared across tenants, and each cell has its own database, so one company's data can never bleed into another's.
Inside a cell, everything is plain files: a Brain/ memory vault, a .claude/ tree of employee definitions, and your working folders. Because a cell is built from standard Claude Code files, the hosted layer is strictly additive: your workspace is never locked to Jetsyn.
One tenant, one cell
A cell is the isolation boundary and the unit of the product. Your employee runs inside your cell, on your files, reached through whatever surface you use. Your credentials for outside tools never live in the employee's hands (see Gateways).
How you reach it#
You reach your cell through gateways: connections your employee holds. Most are conversational, how you talk to your employee: the CLI and the web app. Others are integrations, how your employee acts in your tools: ClickUp, a CRM, Sheets. It is the same cell either way, just a different way in.
| Surface | What it is | Who it's for |
|---|---|---|
| Web app | The /agent workspace: talk to your employee, watch it work, review what it produced. | Everyone. The default way in. |
| CLI | A full product in the terminal. Sign in once and reach your cell directly, or talk to your employee with jetsyn agent. | Operators and developers who want to work the files themselves. |
| Channels & tools | Your employee reaches out through Slack, Telegram, or email, and acts inside ClickUp, a CRM, or Sheets. | Teams who want the employee inside the tools they already use. |
One store, reached many ways#
The cell's files are your data. The CLI edits them directly; the web app renders them as a workspace. It is the same store, never a second database. Edit a file raw from the CLI and it shows up in the web app immediately, because the web app is reading the exact same files.
Note
Solve this once and the tiers below fall out of it. Starter, Business, and Pro are not three products. They are how much you have unlocked over the same cell and the same data.
The three depths#
| Depth | What you unlock | Over the same cell |
|---|---|---|
| Starter | The web app and the CLI, plus the pre-made AI employees doing real work. | Your cell, your data. |
| Business | Your channels and your tools and data (ClickUp, CRM, Sheets, custom), plus custom workflows and a team-shared company store. | Your data plus the shared company store, by permission. |
| Pro | The full command-line product: work the files yourself, live, fully custom. | The same files, raw. |
Where to go next#
Architecture
How a cell is built: the isolated container, the spawn-per-event employee, durable resume, and credential isolation.
Read →The CLI
The command-line product. Install it, sign in once, and reach your cloud cell from the terminal.
Read →Build an AI employee
Author a new employee as plain Claude Code files, then deploy it for any business by pointing it at a config.
Read →Gateways
How connections work and how to add a channel or an integration your employee can act through.
Read →