From first connection to safe deployment.

1. 1. Create your account

   Sign up with your name, email, and a password of at least eight characters. Complete email verification if your hosted authentication configuration requires it.

2. 2. Complete or skip onboarding

   Choose your role, app count, first priority, and platforms. Select Connect data to continue to Connections, or Skip for now to enter the workspace.

3. 3. Connect a platform

   Open Connections, select Apple, Google Play, Stripe, or Paddle, add the requested credentials, then test and save the connection.

4. 4. Import your catalog

   Open Apps and Subscriptions and refresh provider data. Choose which recurring subscriptions RevenueStack should manage.

5. 5. Build the matrix

   Choose a subscription, set its base target, and apply automatic pricing or one of your pricing groups.

6. 6. Review and deploy

   Run Review & Dry-Run, inspect every target and provider-valid result, then approve the deployment only when the rows are correct.

RevenueStack creates a workspace and OWNER membership on the first authenticated request. The workspace contains credentials, apps, subscriptions, pricing data, team access, audit records, billing, and agent access.

Open Settings → Team & Seats, enter an email, and choose ADMIN or MEMBER. Seat limits are enforced when an invitation is created. Removing a member revokes access without erasing historical actor text.

A user can have more than one membership record, but the application currently selects the first available workspace and does not provide a switcher.

Saved provider credentials are encrypted server-side with authenticated AES-256-GCM encryption. Connection responses return masked identifiers and never return decrypted secrets.

Credential-by-credential setup guides

1. Refresh apps

   Open Apps and refresh the connection. Apps are discovered from the provider and cannot be manually created.

2. Refresh subscriptions

   Open Subscriptions and refresh all apps or one app. Apple and Google import auto-renewing subscriptions; Stripe and Paddle import active recurring prices.

3. Mark subscriptions as Managed

   The Managed toggle controls whether a subscription participates in automated pricing and previews.

4. Check imported fields

   Verify the provider identifier, name, billing period, base amount, currency, and optional group or base-plan identifier.

Subscription metadata editing, cross-platform merged products, trials, introductory offers, and subscription archive/delete controls are not currently modeled.

1. 1. Choose a managed subscription

   Select the app and active subscription in the Pricing Matrix.

2. 2. Set the base target

   Enter a positive base price and select Automatic pricing or a pricing group.

3. 3. Calculate territory targets

   RevenueStack multiplies the base by the territory group multiplier and applies configured minimums, maximums, and rounding.

4. 4. Resolve provider-valid prices

   The adapter finds the nearest valid price or price point and returns the final currency, value, and required provider identifier.

5. 5. Inspect differences

   Compare target, current, and final prices. Review warnings before saving or opening a dry run.

Illustrative calculation

Base price:       USD 10.00
Group multiplier: 0.70
Raw target:       USD  7.00
Provider options: USD  6.99 / USD 7.99
Resolved price:   USD  6.99 (-0.14%)

• Create a group with a 1–120 character name and a positive multiplier up to 10.
• Assign or remove territory codes and optionally recalculate affected targets.
• Edit an individual matrix target when one market needs a manual exception.
• Use Safety & Deployment settings for protected subscriptions and excluded territories.
• When deleting an assigned group, choose a valid fallback group.

Explorer supports up to three pricing groups. Indie, Scale, Founder Lifetime, and Studio Lifetime support unlimited groups.

A warning appears when an exact target is unavailable or the closest valid result differs by more than 5%. A difference over 20% is an alert. Safety rules may block large changes.

Available controls

• Reset Store Prices
• Import CSV and Export CSV
• Manage Pricing Groups
• Review & Dry-Run
• Application and subscription selectors
• Quick-Apply Pricing Group and Target price
• Territory search and group filters

1. Run the analysis

   Open Preview & Dry-Run, select the application and subscription, then choose Re-run Analysis.

2. Review every row

   Check current, target, final, difference, provider identifiers, warnings, excluded markets, and unchanged rows.

3. Resolve blockers

   Refresh stale data, correct invalid rows, remove unintended protections, or reduce territories when a plan limit applies.

4. Acknowledge the confirmation

   An OWNER or ADMIN confirms the exact signed rows in the deployment modal.

5. Follow progress

   The deployment view reports totals, the current step, and per-row success or failure.

Web deployments can be approved by an OWNER or ADMIN. MCP WRITE tools only stage a confirmation; an OWNER or ADMIN must approve it in RevenueStack. There is no multi-approver or maker/checker rule.

Adapters may perform bounded request retries, but there is no persistent job queue, user-configurable retry schedule, cancellation during execution, or automatic rollback.

Explorer allows two live deployments per month with up to five territories. Other plans allow all supported territories; an individual request is capped at 250 rows.

History records include

• Actor and UTC timestamp
• App, subscription, platform, territory, and currency
• Previous and new values
• Provider price-point identifier when available
• Status, sanitized provider response, and safe error message

History records are database records, not cryptographically immutable events. Deleting an app cascades related logs, and no automatic reversal action exists.

Indie, Scale, Founder Lifetime, and Studio Lifetime can import UTF-8 CSV up to 512,000 characters and 1,000 parsed rows. Canonical headers are CountryCode, YearlyTarget, MonthlyTarget, and WeeklyTarget. Prices must be positive and no greater than 1,000,000,000.

Connect an agent

1. 1. Create a key

   Open Settings → AI Agents & MCP → Create API Key. Choose the smallest permission that supports the intended work.

2. 2. Copy it once

   The full rs_mcp_live_… secret is shown only at creation. RevenueStack stores its SHA-256 hash and a visible prefix.

3. 3. Configure the client

   Use the Streamable HTTP endpoint and send the key as a Bearer token. A local stdio bridge is also available.

4. 4. Review activity

   Inspect last use, activity, pending confirmations, and update or revoke access in Settings.

Connection details

Endpoint: https://app.revenuestack.app/api/mcp
Transport: Streamable HTTP / JSON-RPC
Header: Authorization: Bearer rs_mcp_live_••••••••

Permissions

Available tools

Visible checkout uses Paddle Billing. Workspace access updates when signed provider webhooks report the plan, billing cycle, customer, subscription, and status.

In-app downgrade, cancellation, cycle switching, invoices, refunds, and a billing portal are not currently available.

Paid and lifetime plans can enable deployment completion/failure, discrepancy, connection-problem, and large-change emails and set the destination email.

• Stripe deployment is unavailable; Stripe connections are read-only.
• There is no automatic rollback, deployment cancellation, or user-configurable retry schedule.
• Workspace switching, ownership transfer, workspace deletion, and account deletion are unavailable.
• There is no public REST API, billing portal, invoice UI, or MFA flow.
• Cross-platform comparisons are heuristic because products lack canonical cross-platform links.
• RevenueStack has no live FX feed, historical FX table, or tax-calculation engine.
• Audit records are not cryptographically immutable and retention cleanup could not be confirmed.
• MCP rate limiting is process-local unless a distributed control is configured in production.