Tier Comparison & Pricing

Individual Accounts

Go Tier (Free)

The free tier is perfect for learning, experimentation, and small projects. Get full access to Claude AI assistance with local desktop application.

• Cost: Free forever
• Execution: Planning and analysis only — no file edits, commands, or deployments
• Paw Compute: 132 PC / 5 hours, 528 PC / 7 days
• Use Cases: Learning, trying PawOS, read-only project analysis
• Payment: None required

Pro Tier ($20 USD/month or ₹1,913 INR/month)

Unlock full execution capabilities with the Pro tier — everything you need for everyday professional development.

• Cost: $20/month (USD) or ₹1,913/month (INR)
• Annual Option: $200/year (USD) or ₹19,053/year (INR) — saves 17%
• Execution: Full file edits, commands, installs, deployments
• Paw Compute: 400 PC / 5 hours, 1,600 PC / 7 days
• Autonomous Work: Available at volume-tiered pricing
• Use Cases: Individual developers, freelancers, solo work
• Billing: Individual account, auto-renewal (cancel anytime)

Pro Max Tier ($100 USD/month or ₹9,565 INR/month)

For power users who need significantly higher usage allowances and advanced features.

• Cost: $100/month (USD) or ₹9,565/month (INR)
• Variants: Available in 5x (₹9,565) and 20x (₹23,913) usage multiples
• Execution: Full capabilities (same as Pro)
• Paw Compute: 2,000 PC / 5 hours, 8,000 PC / 7 days (5x variant)
• Advanced Features: Extended context windows, custom configurations
• Autonomous Work: Same volume-tiered pricing, higher quotas
• Billing: Monthly only, individual account
• Use Cases: Data scientists, full-stack developers, complex systems

Organization Accounts

Team Tier (₹1,913 per seat/month)

Perfect for small to medium teams needing collaboration, shared workspaces, and organized billing. Maximum 150 seats per organization.

• Cost: ₹1,913/seat/month (multiply by total seats)
• Maximum Seats: 150 seats hard limit
• Seat Types: Standard (₹1,913) and Premium (₹9,565) available
• Execution: Full Pro capabilities per team member
• Paw Compute: 800 PC/seat / 5h (Standard), 2,000 PC/seat / 5h (Premium)
• Team Features: Shared organization workspace, invite members by email, audit logs
• Organization Settings: Team name, member roles (Owner, Admin, Member)
• Billing: Invoice-based for amounts >₹50,000, credit card for ≤₹50,000
• Address Capture: Automatic for invoices, billing address required
• Use Cases: Startup teams, consulting agencies, in-house development teams

Enterprise Tier (Custom Pricing)

For large organizations with custom needs, SSO, compliance requirements, and unlimited seats.

• Cost: Custom per-seat rates based on volume (contact sales)
• Maximum Seats: Unlimited
• Negotiation: Annual or multi-year contracts available
• Execution: All Team capabilities with no restrictions
• Paw Compute: 4,000+ PC/seat baseline, pooled and configurable
• Advanced Features: SSO/SAML, custom deployments, on-premise options
• Compliance: Custom SLA agreements, dedicated support channel
• Audit & Security: Full audit logs, advanced permission controls
• Support: Dedicated account manager, regular business reviews
• Use Cases: Fortune 500 companies, large consulting firms, strict compliance needs

Payment Methods

Product disclosure

This disclosure is part of the PawOS documentation for Tier Comparison & Pricing. It is written to make the product behavior understandable before a user relies on it, pays for it, connects an account, approves a plan, or authorizes a machine-affecting action.

What users see

• Users see subscription plan, tier entitlement, Paw Compute usage, rolling limits, Autonomous Work Credit balance, checkout/payment status, and blocked-state messages when a request exceeds entitlement or balance.
• Billing docs should distinguish subscription usage from ticket-completion credits and should identify which runtime or action class consumes which meter.
• Upgrade, payment, and limit pages should describe what changes immediately in the app and what remains subject to confirmation or connector setup.

What PawOS does

• Paw Compute meters ordinary runtime usage according to the configured plan and rolling-window limits.
• Autonomous Work Credits are a separate dollar-denominated wallet used for eligible autonomous ticket completions.
• Entitlement checks run before execution-class work and before connector activation/restore where a connector is tier-gated.

Permissions and boundaries

• Buying credits does not upgrade subscription entitlements, and upgrading a subscription does not add Autonomous Work Credits unless a separate credit purchase or included allowance says so.
• Billing permission does not equal action permission. A paid tier can still be blocked by confirmation, connector scope, local system permission, or organization policy.
• Failed, blocked, or unverified autonomous work should not be charged as completed work.

Evidence and records

• Usage and charge records should identify source, amount, period/window, balance where applicable, and whether the event came from subscription usage or autonomous ticket completion.
• A billing block should explain whether the block is entitlement-restricted, usage-restricted, balance-restricted, or connector-restricted.

Limitations and user responsibility

• Exact plan limits and payment availability depend on current pricing configuration and payment-provider setup.
• Refunds, invoices, taxes, failed payments, and subscription cancellation are governed by the live billing provider flow and any applicable legal policy pages.