iPolloWork Docs

Deploy iPolloWork

Choose the deployment boundary that matches a local desktop workflow, a packaged client, or a private control plane.

iPolloWork has three deployment levels. Use local development for the project workspace, package an Electron client for a desktop verification or release artifact, and add a private control plane only when the organization needs identity, policies, hosted workers, or shared services.

System flowiPolloWork deployment boundary

Agent execution remains on the Work path. Cloud services are optional and are not required for a local desktop workspace.

  1. 01Desktop or web UI

    The local person-facing workspace and editable work surfaces.

  2. 02iPolloWork server

    Local API, workspace state, and runtime integration.

  3. 03OpenCode

    Independent agent runtime used by the local server.

  4. 04Optional Cloud

    Identity, organizations, hosted workers, policy, and administration.

Choose the smallest useful level

NeedRecommended path
Build or contribute locallyLocal development
Verify a native desktop buildDesktop packaging with package:dir
Produce local native installer artifactsDesktop packaging with package
Run a CLI-first host or isolated sidecarsOrchestrator and sandbox
Operate a private organization control planeSelf-hosted topology
Define release, health, and recovery ownershipProduction operations

Keep the boundary clear

The Work client and its local runtime integration are contained in the iPolloWork repository. Accounts, organization administration, hosted worker management, payments, and mobile Apps belong to iPolloCloud capabilities. A local user can run iPolloWork without those capabilities.

Do not treat a browser UI or a static website as a replacement for the desktop runtime. The correct deployment choice depends on whether the task needs local files, Electron integration, or a headless server.

Before a private or organization rollout, use Production operations and Observability and recovery to map health checks, credentials, release evidence, and recovery responsibilities to the actual layer that owns them.