Each plan includes monthly Morpheus credits for premium planning, execution, and verification. If an already-running task goes beyond the remaining balance, Morpheus can allow it to complete within a controlled overrun allowance, then recover the overrun from the next renewal, top-up, or credit grant.
Credits are consumed when Morpheus uses premium execution routes for planning, reasoning, tool use, and verification. More complex tasks consume more credits. If credits run out before a new paid task starts, Morpheus may pause the task until renewal, top-up, BYOK routing, or admin action is available. If a task already started with credits available, controlled overrun can allow it to finish within the account’s allowance.
All plans include BYOK support, credit top-ups, and controlled overrun protection for already-running tasks.
For exploring Morpheus, daily AI assistance, and light technical tasks.
For professionals and builders doing serious technical work.
With Pro credits, users can typically build or modify websites, generate documentation, run server tasks, investigate bugs, or create small web applications — depending on task complexity.
Shared workspaces, infrastructure connectors, multi-agent orchestration, and audit logs.
For technical teams running operational workflows.
For IT companies managing multiple clients and environments.
For large organisations with specific requirements.
Controlled overrun is designed to prevent abrupt mid-task stops for work that started with credits available. BYOK is available separately for supported model usage through customer-provided keys.
If your balance is exhausted before starting a new paid task, Morpheus may pause the task until renewal, top-up, BYOK routing, or admin action is available. If a task already started with credits available and runs beyond the remaining balance, Morpheus can allow it to complete within a controlled overrun allowance. The overrun is recovered from the next renewal, top-up, or credit grant.
Morpheus is designed to avoid abrupt mid-task stops, not to provide unlimited usage. Already-running tasks can be protected by controlled overrun. New paid tasks may pause when credits and overrun headroom are exhausted.
Local/private AI compute is available through custom private, dedicated, or sovereign deployment discussions. It is not the shared SaaS credit fallback.
Credits are consumed when Morpheus uses premium execution routes for planning, tool use, reasoning, verification, document/media work, and other billable platform actions. BYOK-routed usage does not consume Morpheus plan credits. Overrun usage is billable usage and is recovered from future credits.
Yes. Credit top-ups are available: 5,000 credits for $29, 10,000 credits for $59, 25,000 credits for $149, and 50,000 credits for $299. Top-ups can also recover outstanding overrun usage.
No. Overrun credits are billable usage credits. They are recovered from future renewals, top-ups, credit grants, or other account credit events.
Team-level usage controls are available on Business plans and above. This allows administrators to set credit budgets per user or per project, and to review usage across the team.
Multi-agent orchestration is available on Business plans and above. Individual Starter and Pro plans use a single agent per task. Business plans support up to 3 concurrent agents; Agency/MSP plans support up to 10.
Yes. Private cloud, dedicated infrastructure, and on-premises deployment options are available for Enterprise and Government tiers. These options provide dedicated data handling, regional data residency, and stricter data control for organisations that require it.
The Remote Gateway is a small Linux agent installed inside your network. It connects outbound over TLS to Morpheus Cloud and executes private-system tool calls locally — SSH, WinRM, Proxmox, vSphere, firewalls, storage, backup, databases, internal HTTP APIs. The cloud stays the planner, billing, audit, and approval layer; the execution moves on-prem. No inbound ports need to be exposed. Included from Pro plan upwards (1 gateway on Pro, 5 on Business, 25 on Agency, unlimited on Enterprise).
No. Gateway-routed calls are billed at exactly the same rate as cloud-routed calls during the pilot programme and the v1 release. We may revisit per-call pricing once we have steady-state usage data, but any change will be announced publicly before it lands.
Yes. From Settings → Connections you can mark any private/on-prem connector as Private and select which gateway it routes through. SSH connectors get a per-server gateway dropdown; vendor REST connectors inherit the page-level default. SaaS connectors stay cloud-routed and ignore the setting. Per-client (workspace-pinned) gateways are a Business+ feature.
Tool calls against connectors pinned to the offline gateway return a clear gateway_offline error with the last-seen timestamp. The cloud doesn't silently fall back to a different execution path. The agent reconnects automatically with exponential backoff; once it's online, the next call goes through. Cloud-routed tool calls are unaffected.
Yes. Toggle Dry-run on the gateway's detail page in the console. The agent accepts every tool call, runs policy + argument checks, and returns a structured "would have executed" payload instead of invoking vendor code. The flag is pushed live to the connected agent — no restart needed. We strongly recommend pilot customers run their gateway in dry-run for the first week.