Permaura: Buy vs Skip (Agency Agent Permission Gateway)
IF your agency runs AI agents (Claude, ChatGPT, Cursor) against client Stripe, GitHub, HubSpot, or Slack accounts and needs per-connection allow/require-approval/deny rules plus device-signed approvals, THEN start on the Free plan at $0 with unlimited local agents, connections and policies in 1 workspace, and upgrade to Pro at $19 monthly ($15.83 annual) once you need 3 workspaces, 1 hosted gateway, unlimited hosted secrets, and a managed permaura.app tunnel. IF you are staffing multiple seats across client accounts, the Team plan at $19 per seat monthly ($15.83 annual) is the tier to price into retainers.
By InnovaAI ResearchPublished
Permaura: Buy vs Skip (Agency Agent Permission Gateway)
“IF your agency runs AI agents (Claude, ChatGPT, Cursor) against client Stripe, GitHub, HubSpot, or Slack accounts and needs per-connection allow/require-approval/deny rules plus device-signed approvals, THEN start on the Free plan at $0 with unlimited local agents, connections and policies in 1 workspace, and upgrade to Pro at $19 monthly ($15.83 annual) once you need 3 workspaces, 1 hosted gateway, unlimited hosted secrets, and a managed permaura.app tunnel. IF you are staffing multiple seats across client accounts, the Team plan at $19 per seat monthly ($15.83 annual) is the tier to price into retainers.”
- Client workflows touch money or messaging (Stripe refunds, Gmail sends) where a device-signed approval on phone, desktop, or Apple Watch is a contractual requirement
- Delivery spans more than one client toolchain, so per-connection allow/require-approval/deny policies beat handing out raw API keys
- The agency needs signed, linked audit trails to satisfy client security reviews or procurement questionnaires
- You are past a single pilot and need 3 workspaces plus remote access to gateways, which the Free plan's 1 workspace cannot cover
- A productized setup engagement (for example a $2,250 SMB agent setup at roughly 20h effort) can absorb the gateway deployment and policy configuration
- The client will not install or manage a gateway locally or via Permaura hosting, since that operational overhead sits on top of direct API access
- Only one workspace is ever needed and no hosted secrets or managed tunnel are required, making the Free plan at $0 the ceiling and a paid tier unnecessary
- Agents act on read-only or low-sensitivity data where approval gates add friction without reducing real risk
- The agency has no MCP-compatible assistant in play (Claude, ChatGPT, Codex, Cursor), so the gateway has nothing to sit between
- Budget cannot carry per-seat pricing at $19 per seat monthly once the team grows beyond a single operator
More on Permaura
- StrategyWhy Permaura Turns Agent Security Into Agency Retainer Revenue
- ConceptPermaura Approval Tier Ladder
- Evaluation RulePermaura Rule: Gate Client Credentials Before You Delegate Agent Work
- Failure PatternThe Permaura Approval Fatigue Trap: Why Agencies Fail With Permaura on Multi-Client Agent Workflows
- Implementation BlueprintPermaura Agent Permission Gateway Rollout (7-10 days)
- Operating ProcedurePermaura Client Gateway Provisioning (Onboarding)