01 · WorkspaceFour shells. Always running. Never leaves the window.
Quad terminal is the center of zyan. Each pane holds a persistent shell — branch-aware, per-project, and alive across reloads. Dev server in one, git in another, deploy logs and tasks in the third and fourth.
~ dev-server
$ pnpm dev
▲ Ready in 1.2s
Local: http://localhost:3000
~ git
$ git status
On branch avid/hero-polish
nothing to commit
~ deploy
$ zyan deploy --env=preview
✓ Built · 2.1s
→ https://preview-avid-1.zyan.app
~ tasks
[ ] Design review @riley
[x] Ship mobile carousel
[ ] Client call 4pm
- Persistent shells survive reloads and laptop-lid closes
- Up to 10,000 lines of scrollback per pane
- Branch-aware command context — switch branches, shells follow
- One project, one shell set — no leakage between client workspaces
02 · ComputeBurst when the build needs it. Idle when it doesn’t.
Compute is billed per minute, not per task. Workspaces scale up automatically for big installs, type checks, and image pipelines — and drop back down when idle. Preview environments are spun per branch and live on disposable domains.
0.1 vCPU idle8 vCPU burst$0.05/hr overage
- Automatic bursting — no “pick a machine size”
- Preview environments per branch, auto-expire after 14 days idle
- Rollback-ready release history with deployment metadata
- Enterprise: dedicated single-tenant compute pools, pinned region
03 · ReviewPRs and comments stay attached to the code.
Drop a comment on any line in any file and it becomes a thread — assignable, resolvable, and auto-converted to a task with file context and branch history attached. No more Linear ↔ GitHub ↔ Slack gymnastics.
Hero.tsx · line 14
13 <h1>
14 The cloud IDE for web design agencies.
15 </h1>
Riley2m ago
Should this be the cloud IDE, or your cloud IDE? Thinking about launch copy.
Jamiejust now
Going with “the” — assigned to Clement to confirm before ship.
✓ Task created · avid/hero-polish
- File-level review threads, branch-scoped so comments don’t leak across PRs
- One-click convert any comment to a task with file + branch context
- Client review portals (Agency+) — clients comment without workspace access
- Full commit · prompt · deploy timeline per branch
04 · Components & integrations240+ components. 1000+ integrations. Ready to drop.
The workspace ships with an accessibility-audited component library. Agency plans layer in a private component library scoped to your team. And every major SaaS you pass through client projects — Stripe, Salesforce, HubSpot, Segment — is already on the shelf.
~ library/240+ components · 1000+ integrations
Button
Hero
Pricing
Nav
Form
Card
Gallery
Footer
Modal
Table
Tabs
Toast
// integrationsStripe · Salesforce · HubSpot · Segment · Mailchimp · Twilio · Intercom · GA4
- Each component shipped accessible, tested, and license-tagged
- Private component library on Agency+ — your team’s reusable kit
- Fork public components into private ones with one command
- Integrations include auth, webhooks, and ready-to-run snippets
05 · AI & activityEvery prompt, every commit, every deploy — one live feed.
zyan is the first IDE that treats AI prompts as first-class workspace events. Every prompt is logged, attributable, and replayable. Activity feeds surface commits, prompts, deploys, and feedback together — so the whole team sees the delivery picture.
Clementdeployedavid/hero-polish → preview2m
Rileyran prompttighten hero subhead (47 tokens)4m
Jamieresolved threadHero.tsx:14 · 3 messages6m
Clementpushed5 commits to avid/hero-polish8m
- Prompt library — shared, versioned prompts per team
- Prompt history attached to every branch and every commit
- Activity feed filterable by person, project, or event type
- Your code is never used for model training — full opt-out per workspace
06 · Admin & accessIdentity, audit, and infrastructure controls that actually scale.
SSO from day one on Agency plans, SCIM provisioning on Enterprise, per-workspace audit log, and optional dedicated compute regions. Everything security review committees ask for — shipped before they ask.
sso_providersOkta · Azure AD · Google Workspace · OneLogin · JumpCloud
scim_provisioningEnterprise
audit_log30d · 1y · custom retention
dedicated_regionEnterprise · single-tenant compute pool
data_residencyus-east-1 default · eu on request
- SAML SSO on Agency — self-serve in workspace admin
- SCIM + role-based workspace scopes on Enterprise
- Immutable audit log of every workspace, deploy, and admin action
- Trust packet, SOC 2 posture, and subprocessors all at /security