No. The runtime is local. The only network calls are: model providers you configure (using your keys), MCP servers you install, and our update / license server. The update server only sees your license key + device ID + app version.

No. Most agents work fine through hosted providers. You only need a GPU if you want to run local Ollama models or local video / image diffusion.

We never markup tokens. You bring your own API keys (or run local). We optionally offer per-agent budget caps, daily ceilings, and prompt-cache analytics inside the app.

Skills are local scripts your agents can call (Python or Node). MCP servers are tool servers that follow the Model Context Protocol — agents discover them and use their tools. Power-ups are first-party native integrations (Webull, iMessage, Drive) that wrap platform APIs and store credentials in your vault.

Studio plan supports team workspaces with shared workflows, audit logs, role-based access, and SSO/SCIM. Memory and vaults stay device-local; workspace artifacts sync end-to-end encrypted.

Core runtime is MIT-licensed and on GitHub. Premium components (channels, cloud sync, marketplace) are source-available with paid license.

Yes. With local Ollama models, you can run a fully offline swarm. The license server tolerates 30 days offline without re-check.

No. AgentiqFlow is paid-only — every download, install, and runtime invocation requires a valid, paid license. Plans start at $100/month for Solo and scale to $500/seat/month for Studio. Cancel any time in the Stripe Billing Portal; access stays active through the end of your paid period.

If a payment fails or you cancel, your license flips to past_due (Stripe dunning) then revoked. The local sidecar checks license status with the worker on a 5-minute cache; once revoked, agent dispatch is gated and the dashboard prompts you to reactivate billing.