REDA AI over MCP is live: your configured agents, inside Claude. Explore the connection →
Costs & value

Org-wide AI licensing: what it includes and what it does not

Organisation-wide pricing makes one buying decision simpler: adding another colleague does not add another REDA AI seat charge. The next step is understanding the work covered by the plan and how its shared usage is managed.

At a glance

  • One REDA AI subscription covers one Salesforce org.
  • Choose AI included or Bring your own AI; plan allowances and access controls still apply.
  • Existing Salesforce and third-party entitlements remain separate.

Access and consumption answer different questions

One REDA AI subscription covers one Salesforce org without a REDA AI seat charge for each colleague. Choose AI included, funded through REDA credits, or Bring your own AI, where you pay your provider directly. Org-wide access does not remove plan allowances or Salesforce permissions.

With Bring your own AI, each agent can use a supported provider and model through a configured connection. REDA AI remains the orchestration layer for business context, permitted tools, workflows and usage records in Salesforce. Credentials stay in your own Salesforce credential store; REDA takes no cut of your provider bill.

How the commercial model fits together
  1. One Salesforce org
  2. Configured agents
  3. Your AI funding choice
  4. Visible consumption

Read a plan as a complete offer

Compare Free, Starter, Growth, Business and Enterprise on the Pricing page. It shows the current subscription amounts, allowances, billing terms and eligible nonprofit prices for both AI funding models.

With AI included, the displayed plan total includes its platform subscription and REDA credit allowance. With Bring your own AI, budget for the REDA subscription and your provider’s separate usage charges. Use your order and subscription agreement to confirm the scope you are buying.

What else belongs in the budget?

ItemHow to think about it
Salesforce licencesREDA AI does not replace the Salesforce entitlements needed for the chosen users and channels.
Other servicesAn assistant host or external system can have its own commercial terms.
ImplementationProduction configuration, integrations and rollout are scoped separately.
PeopleAllow for administration, review, support and changes to the workflow.

For a company with multiple Salesforce orgs, do not assume a single subscription covers all of them. Discuss that topology explicitly. An org-wide model is different from a corporate group-wide entitlement.

Plan for usage in the funding model you choose

For AI included, a one-time credit top-up can support a temporary increase in work. See the Pricing page for current packs and rates.

Redeemed top-ups remain available through the end of the redemption month in the following year, unless used sooner. An ordinary subscription renewal preserves unused, unexpired top-ups and their original expiry date; spending them requires an active paid subscription. Included monthly credits have a separate rollover rule, capped at twice the monthly allowance. Do not combine the two into a single promise that all credits last a year. Check the subscription agreement for the governing terms.

Bring your own AI does not consume REDA credits or require REDA top-ups. Your provider bills the usage under your direct agreement. REDA AI still records usage and applies the configured controls, so review provider spending alongside the work completed.

Choose the plan around the workflow

Start with the workflows you need, their expected volume and the tools, prompts and channels they use. Compare the plan allowances, measure representative usage and include retries and human review in your budget.

Free and Starter suit evaluation or a focused workflow. Growth is the recommended starting point for broader team adoption; move to Business when its additional capacity fits your needs. The Pricing page keeps that comparison in one place.

Your process. Your priorities.

Put the idea in your business context.

Bring your workflow and the people who know it. We can explore what a useful first evaluation would look like.

Discuss your workflow