Use Agentful Cloud

Agentful Cloud is the managed path for teams that want the shop app without owning the server, Postgres lifecycle, media storage, release rollouts, and backup schedule.

Pricing Shape

Plan	Monthly	Annual	Best fit
Free	$0	$0	Evaluation and tiny shops on an Agentful subdomain
Launch	$12	$90	First real store with a custom domain
Grow	$39	$290	Active small business with webhooks and more staff
Pro	$99	$790	Serious operators that need staging and higher limits
Dedicated	From $249	Custom	Shops that need dedicated database/runtime isolation

Paid plans do not add an Agentful platform transaction fee. Standard payment processor fees still apply.

What Stays The Same

The hosted product uses the same product model, MCP tools, settings model, plugin manifest contract, and update discipline as the self-hosted app.

Isolated shop data

Each shop is provisioned as its own database boundary. Shops should not share a schema unless Agentful later adds an explicit tenant boundary.

Scoped MCP tokens

Admin agents still receive narrow bearer tokens. Tool visibility is the intersection of token scope and the owner’s live RBAC grants.

No core-file editing

Cloud agents can change settings, data, and approved plugins. They do not get shell or source access to the running app.

When To Use Cloud

Use the managed path when:

• You want Premier Studio to operate updates, uptime checks, backups, and restores.
• You prefer an MCP-first admin surface but do not want to manage Docker or database credentials.
• You want a production shop quickly and can keep custom behavior inside settings or plugins.

Use self-hosting when:

• You need full infrastructure ownership.
• You want to run private plugin build infrastructure.
• You need to inspect or modify deployment topology directly.

Onboarding Shape

The cloud onboarding flow should collect:

1. Store name, owner email, storefront origin, and support email.
2. Payment provider mode and Stripe credentials when production payments are enabled.
3. Media storage policy and CDN/public image base URL.
4. Initial admin user and MCP token scopes.
5. Desired theme and starter content.

After provisioning, connect your AI client to the hosted MCP endpoint using the token returned once during setup.

claude mcp add --transport http agentful-admin https://<shop>.agentful.app/api/mcp \
  --header "Authorization: Bearer shop_mcp_..."

Provisioning Model

Agentful Cloud runs regional cells. A cell is Cloudzy compute plus Postgres capacity, fronted by Cloudflare DNS/CDN and backed by S3-compatible media storage. Customer signup does not create a VPS. Signup creates one isolated Postgres database and role for the shop, runs tracked migrations, and creates a proxied Cloudflare record for <shop>.agentful.app.

Cell metadata is configured with CLOUD_CELLS_JSON. The committed deploy/cloud-cells.example.json file shows the shape. Database credentials and provider tokens stay in the host secret manager or 1Password and are injected as environment variables.

export CLOUDFLARE_API_TOKEN="$(op read op://<vault>/<item>/cloudflare-api-token)"
export CLOUD_CELL_US_NYC_1_POSTGRES_ADMIN_URL="$(op read op://<vault>/<item>/postgres-admin-url)"
export CLOUD_CELLS_JSON="$(cat deploy/cloud-cells.example.json)"

Operational Boundary

Cloud-hosted normal admin tokens do not expose deploy, restart, restore, shell, or filesystem tools. If Premier Studio ships an operations plugin later, keep it separate from the default admin token and require explicit operator consent for deploy/restore actions.