MeshiaDocs
All docsPricing
Continue
All docs
Getting started
Your first sessionThe workspaceSSH access
Core concepts
Agent rolesSoon
ExperimentsResearch plans
CanvasSoon
WorkflowsSoon
Integrations
External AI agents (MCP)Connect MeshiaGitHub
WebhooksSoon
Notifications
Platform
Billing and plansAgent memoryMulti-chatKeyboard shortcuts
Reference
GPU catalogAgent toolsSecurityLimits and quotas
Reference

Limits and quotas

Plan limits

LimitFreePro
Workspaces3, including those in teams you ownUnlimited
Meshia GPUs attached at once2No plan cap (workspace limits still apply)
GPU classesStarterAll
Included storage100 GB2 TB
Included usage$10 once$500 every month
Your own connected machinesUnlimitedUnlimited

A workspace counts while it is running, or stopped with saved files. Deleting a stopped workspace's files frees its slot. Settings > Billing and the dashboard show your current usage against these limits.

Compute has no fixed lifetime. Workspace spend caps, GPU caps, total budgets, and billing status determine whether compute can continue.

Request limits

Same-origin app requests can be rate-limited by route. If you exceed a limit, you'll get a 429 Too Many Requests response with a Retry-After header telling you how long to wait.

WebSocket connections (used by the workspace UI) are limited to 5 concurrent connections per session. This is more than enough for multi-chat with 4 panes plus the main session connection.

Pod resource limits

Each pod gets the full GPU you selected. No sharing, no oversubscription. System resources per pod:

ResourceAllocation
CPU8 vCPUs
RAM32 GB (A100/H100/H200: 64 GB)
Disk100 GB NVMe SSD
Network1 Gbps

If you need more CPU, RAM, or disk for a specific workload, email luke@meshia.io. We can provision custom pod configurations for Pro users.

Agent limits

  • Max agents per session: 5 (one per role)
  • Max message length: 32,000 characters per message
  • Max file size for agent reads: 10 MB (for larger files, the agent reads in chunks)
  • Max concurrent background tasks: 8 per pod
  • Max artifact upload size: 2 GB per file

Workspace lifetime

Closing or refreshing Meshia does not stop an active workspace. Once a chat turn, scheduled task, managed background job, research run, or compute command is accepted by Meshia, the server owns it. Reopen the workspace later to inspect its persisted progress and results.

Meshia does not use browser presence, an open tab, or button clicks as proof that a workspace is active. A workspace remains active until you explicitly stop it or a server-enforced limit, budget, or runtime failure ends it. Any future inactivity policy must check durable server work before stopping compute; an accepted or running task prevents an inactivity stop even when every browser is offline.

Storage

Workspace files are stored in Meshia's durable object storage. Free accounts include 100 GB shared across their workspaces; Pro includes 2 TB. Your workspace storage limits count toward this allowance, including empty space. A team's workspaces count toward its owner's allowance, so a team owner's personal and team storage share one total and any overage is billed to the owner. Members' personal workspaces stay on their own accounts. Storage above the allowance is billed at $0.08/GB/month while the storage is retained. The dashboard shows your storage against the allowance.

← Security