Pricing
Commercial pricing is not frozen yet. The product boundary is: local capability should not require a managed relay, while cloud-operated remote-provider features can carry the recurring infrastructure cost they create.
Arc Local
For people who want Arc's local control surface and local/provider-native integrations without making Orqara Cloud part of the normal machine-access path.
- Arc desktop app and Arc MCP.
- Explicit local workspace permissions.
- Agent activity and Agent Bus collaboration.
- Local provider adapters.
- Direct provider-native connection paths where available.
- Bring-your-own remote infrastructure for advanced users.
Arc Cloud
For managed remote-provider connectivity and account/device features that require Orqara-operated infrastructure.
- Orqara account and device registration.
- Managed remote-provider relay.
- Managed OAuth and connector lifecycle.
- Remote connector and device revocation.
- Future managed integrations that cannot use a better direct/native transport.
No forced cloud detour
Local clients should remain local, and provider-native transport should be preferred where it is the better route. Arc Cloud is not intended to proxy local traffic merely to make the architecture look uniform.
Before launch
Final prices, licence terms, included devices, billing cadence, and any early-access offer will be published after production packaging and managed-relay operating costs are measured.