Where the work runs: local execution, Sync and Korps Cloud

What this is

An AI worker is software that has to run somewhere. In Korps that "somewhere" is a machine you pair with the app, and the organisation around the workers is kept by Korps. This page explains the arrangements, in the order you are likely to meet them.

Who it helps

Anyone deciding whether to start on their own PC, rent a server, or wait for hosted execution; and anyone confused by the words Sync and Cloud on the pricing page.

The three arrangements

1. Local execution: the free app

You install the Korps app, and your workers run on your own computer. The app pairs the machine, and the runtime (Hermes Agent comes bundled) runs there. Your workers think with an AI model account you connect: your own key or subscription with a provider such as Anthropic, OpenAI, xAI, Google, OpenRouter or a local Ollama server. Provider credentials for agents on your connected machine stay on that machine. Credentials added through Korps Cloud compute connections are encrypted and stored by Korps.

Good for: trying it out, small teams, work that only needs to happen while you are at your desk. When the PC is off, the workers stop.

If the team should keep working while your laptop is shut, the machine you pair can be a server you rent. You install the agents on it and pair it with a one-time code from the app. From then on it reports its health to your workspace, and every worker on it says which machine it is on.

2. Sync: one account, every device

Sync carries your setup between devices: supported agent configurations, personalisation and settings. Sign in on your desktop and your phone and the same organisation is there. Sync does not run the workers anywhere; it keeps your setup in step. Sync is a small paid add-on and is included in every Cloud plan.

3. Korps Cloud: the organisation, hosted

Today Korps Cloud keeps the organisation: accounts, workspaces, workers, teams, rooms and messages, approvals that wait across devices, routines on a schedule, the Activity record, and usage in dollars against a ceiling you set. Running the workers still happens on a machine you pair.

Hosted execution, where Korps runs the machine in your isolated workspace so the team keeps working with your computer off, is the next step and is not available yet. Cloud plans are described by how many agents can be running tasks at the same time; today they are in early access and cannot be purchased.

What each one costs you, in plain terms

• Local: the app is free. You pay your AI provider for what the workers think with, and whatever your own server costs if you rent one.
• Sync: a small monthly fee. Same AI costs as local.
• Cloud: a monthly plan by capacity, Sync included, when it is sold. AI usage stays separate; today you bring your own provider, and a Korps-managed AI option is planned but not decided.

The current figures are on the pricing page, which is the only place they are stated.

Requirements and availability

• Available in Korps: local execution on a paired machine, pairing a rented server, Sync, and the hosted organisation (Cloud as it works today).
• Planned for Korps: hosted execution, Korps-managed AI usage, purchasable Cloud capacity.
• The free account is open now. The Korps app for Windows and Android opens at launch.

Limitations and approval points

• Local execution means your machine's resources and uptime are the limit. A closed laptop is a stopped team.
• Sync moves configuration, not conversations or running tasks. It does not migrate live work between machines.
• Hosted execution is not a promise of a date. Plan with what is available today, and treat what is planned as planned.
• Wherever the worker runs, approvals work the same way, because approvals are held by the organisation, not by the machine.