Desktop, web, and mobile

Local projects

Free includes unlimited machine-local projects. Their complete Build/coding loop—tasks, missions, Board, Command center, worktrees, terminal, Preview, Changes, rounds, receipts, context, memory, rules, work-context files, local Assets, and verbose engine logs—stays on the Mac and remains available offline. Local projects do not use normal Iterel cloud delivery, hosted analytics, or Iterel-funded models.

Cloud projects

Free may activate one collaborative cloud project. Design, Whiteboard, Project Map collaboration, membership, comments, review targets, and normalized execution receipts live in Iterel Cloud so collaborators and any signed-in desktop client can open them—phones open the companion surfaces (see Mobile below). Paid plans add more simultaneous cloud projects and longer continuity. Choosing a cloud-only surface from a local project explicitly offers Create collaborative cloud copy. Nothing uploads automatically; the local project remains, and local Asset bytes stay on the Mac until selected.

Portable exports preserve compatible older Design and Whiteboard fields so a cloud transfer does not lose data. The allowlisted cloud projection transfers tasks, bounded rounds and Changes, missions, Chats, artifacts, context metadata, rules, and language; it removes machine paths, credentials, raw engine logs, and local Asset bytes. Iterel does not promise offline canvas authoring in a local project.

Machine-backed work

Working-tree edits, installed Build engines, git credentials, gates, package scripts, local preview, terminal, folder binding, and machine-local design-system extraction require a Mac. The machine is the trust boundary; source and vendor CLI credentials do not move into Iterel Cloud.

Remote session

When your signed-in Mac is online, web and mobile can drive it through a same-user RemoteBridge: start a round, steer supported engines, run gates, review, Accept or Discard, and create a pull request. Project membership never grants authority over another member's machine.

Mobile

Mobile is the same responsive, installable renderer—not a React Native fork or /m/ tree. A phone is a companion, not a smaller Iterel: projects, tasks, and continuing a task, plus notifications, comments, Command center, Chats, and Assets.

The making and orientation surfaces—Design, Whiteboard, Project Map, Architecture, and Ideation—are absent on a phone, not degraded. No entry point renders, and a deep link to one resolves to that project's tasks. Local projects, terminal, folder binding, local preview, and machine settings stay unavailable.

Honest degradation

If machine-backed work has no local or remote host, the composer says host offline or offers the Mac app. It never silently queues code work or swaps in a managed model without a working tree.