| Plori | Plori operates the agent. Use the web app, or let your own agent (Claude Code, Cursor, Codex) drive Plori's agents over MCP. | Only Workspace files persist, with saved revisions, the conversation, and run history. Software installed outside the Workspace and running processes do not carry over to the next run. | Credits, a prepaid balance in US dollars, pay for model usage and run time ($0.01 per minute, billed by the second). Each run gets its own VM; in our measurement, VMs stopped a median 1.739 s after run end and idle windows incurred $0 in charges. Include subscriptions and extra disk. Idle billing measurements. | Replies in the conversation, files in the Workspace. Several workers can run in one Workspace at once, each on its own copy of the files. Plori merges changes and handles conflicts. Scheduled runs and agent-built workflows. Irreversible actions outside the agent's environment wait for the owner's approval in the web app. |
| Sandbox APIs (E2B, Daytona, Modal) | The provider operates code execution. You build the agent and the application around it. | Depends on the vendor and mode. E2B pause can keep files and memory. Daytona container stop keeps files, not memory. Modal snapshots keep files for a later sandbox. | Compute, storage, any plan fee, and your model and tool providers. | Your application connects execution output to users, schedules, credentials, and approvals. |
| A VPS you manage | You install and operate your own agent on a rented server. | Disk follows the server and its backups. | Server rental, storage, models, tools, and your time. Check whether a stopped server still bills. | You build result delivery, scheduling, permissions, updates, and monitoring. |
| A local agent on your laptop | Your agent process runs on your own device. | Files stay on the device. Sleep, shutdown, or a process failure can interrupt a run. | Hardware and electricity, plus model and tool charges. | Unattended work depends on the device staying available. |
| Cloud agents in another product (for example, Cursor) | The vendor operates the agent, with its own setup and integrations. | Cursor cloud agents run in isolated cloud VMs. Automations keep notes in MEMORIES.md across runs. | Cursor bills Automations as cloud agent usage. Check plan fees and model usage. | MCP support, PRs with artifacts, and Automations on cron schedules or events from GitHub, Slack, Linear, and webhooks. |