# Choose your setup Source: https://docs.ideharmony.com/getting-started/choose-your-setup Harmony sells one local product and one optional hosted-compute plan. Model access is never bundled. **Outcome:** you know which surface to install, whether you need an account, and who bills inference. ## The two products | Product | What you get | Account | Money | |---|---|---|---| | **Harmony Core** | Desktop, terminal agent, and `harmony` CLI on **your** computer | No | Free. Not a trial of Core. | | **Harmony Pro** | Cloud: optional hosted Linux workspaces (Agent Hours) | Yes, for Harmony Pro only | One paid plan. Figures live only on [pricing](/pricing). | The one paid plan is **Harmony Pro**; "Cloud" is what it buys. Harmony-routed model credits are **not** for sale. A Harmony Pro subscription does not include tokens: agents in a workspace use your own Claude Code or Codex subscription. ## Where the agent runs | Surface | Where work runs | Typical use | |---|---|---| | Harmony desktop | Local machine | Multi-pane control, approvals, fleet | | `nala` TUI / CLI | Local machine, same daemon | Focused session in a repo, scripts | | This website / optional web app (PWA) | Browser talking to Harmony's cloud | Watch or steer **hosted** jobs away from the development machine | | Native iPhone / Android apps | — | **In development.** Not an App Store or Play Store download. Not desktop parity. | The website is the same Harmony account as Cloud on desktop. It is not a fourth local daemon and it does not run local terminals, MCP, or on-device voice. ## Who pays the model Harmony launches **your** agent CLI. That CLI authenticates with **its** provider, on the machine where the agent is running: - **Core:** sign in on your laptop (`claude`, `codex login`, or that vendor's equivalent). Network use and token spend go to that provider. - **Cloud:** sign in **inside the workspace** after it starts. Spend still goes to that provider. Harmony meters Agent Hours for the VM, not tokens. Installed is not authenticated. Authenticated is not entitled. Harmony can see the binary; it cannot see your plan. Core never stores those CLI keys. Cloud may store **other** secrets you add on [Account → Secrets](/docs/security/credentials#optional-cloud-secret-storage-not-core-not-byok) (clone URL / deploy key), encrypted with an operator key — not customer BYOK and not a model-key vault. ## Pick a path | If you want… | Do this | |---|---| | Local coding workspace, no Harmony account | [Install](/docs/getting-started/installation) → [first workspace](/docs/getting-started/first-workspace) → [connect a provider](/docs/getting-started/connect-a-provider) | | A first reviewed change | [Your first agent session](/docs/getting-started/first-agent-session) — Claude implements, Codex reviews, you approve the diff | | Hosted compute while the laptop is closed | [Cloud](/docs/cloud) with Harmony Pro, after Core works locally | | Watch Cloud from a phone or another computer | [Use Harmony in a browser](/docs/getting-started/web-app) | Cloud trial and paid checkout happen on the website, not by visiting a URL. [Cloud quickstart](/docs/cloud/quickstart) covers `/cloud/start` (routing only) versus the explicit trial control and separate monthly/annual checkout. ## Related - [Overview](/docs) - [Quickstart](/docs/getting-started) - [Core vs Cloud](/docs/cloud/core-vs-cloud) - [Pricing](/pricing) — the only place Cloud prices are stated