Updated June 17, 2026 by Sunny Chauhan, Salesforce Platform Developer II, Data Cloud Consultant.

Salesforce GA'd a new ISV SKU in April 2026 called Data 360 Provisioning for ISVs (Salesforce Summer '26 ISV strategy). It collapses the old per-cloud SKU model into a single Flex Credit currency. The big shift: batch data ingestion is now free and unmetered. You only pay when data activates for an agentic outcome. For ISVs whose products ingest a lot of customer data and use only part of it, the unit economics changed materially. For ISVs whose products activate everything they ingest, less so.

Pro Tip

TL;DR Data 360 Provisioning for ISVs is GA as of April 2026. Replaces legacy per-cloud SKUs with a unified Flex Credit currency. Batch ingestion is free and unmetered. ISVs and customers pay only when data activates for an agentic outcome (agent action, automation, real-time enrichment). Best for products that ingest broadly but activate selectively. The pricing change can cut data costs significantly for ISVs whose old model paid for ingest even when the data sat unused.

Before this release, Data Cloud (now Data 360) charged ISVs and customers per-cloud SKUs. You paid for Sales Cloud data volume, Service Cloud data volume, Marketing Cloud data volume, each tracked separately, each with its own quota. The old model rewarded ISVs who could keep data volume low and penalized those whose products legitimately needed to ingest a lot of data even if most of it sat at rest.

The new model:

1/ One currency. Flex Credits replace per-cloud quotas. One pool, one usage meter.

2/ Free batch ingest. Pulling data into Data 360 in batch is free and unmetered. Doesn't matter if it's a million rows or a billion.

3/ Pay on activation. You consume Flex Credits when data is activated for an agentic outcome: an agent action invocation, an automation trigger, a real-time enrichment, a model inference.

The economic logic is: Salesforce doesn't care if data sits at rest. They care if it does work. So ingest is free, work costs.

I've watched the founders we work with at Appnigma run two different reactions to this announcement, depending on what their product does.

→ ISVs that ingest broadly but activate selectively. Conversation intelligence products, revenue intelligence products, intent data products. They pull every meeting, every email, every signal, but only act on a small subset (the "interesting" ones). For them, the new model is a clear win. They were paying for data volume they weren't really using.

→ ISVs that ingest exactly what they activate. CPQ products, billing products, contract products. Every row they pull they do something with. For them, the old model and the new model are roughly equivalent on cost.

→ ISVs that activate more than they ingest (via enrichment, joins, agent actions on combined data). The new model can actually cost more for high-activation products, because activation is now the meter.

The honest read: this is a pricing change Salesforce designed to favor the AI-agent and intelligence categories they want more of on AgentExchange. If your product fits that shape, the math got better. If it doesn't, you should re-run your unit economics before assuming you'll save money.

Salesforce hasn't published a public Flex Credit rate card as of June 2026. Pricing is set per partner contract and negotiated as part of your ISV agreement. What I've seen across the founders I work with:

→ The credits are bought in bundles tied to your customer's anticipated activation volume → Customers can buy their own Flex Credits or roll them into their seat-based ISV subscription → Larger volumes negotiate lower per-credit rates → Salesforce's published partner messaging frames Flex Credits as "elastic" pricing, which in practice means quarterly true-ups

If you're sizing a deal, get the actual rate from your partner manager. Don't size off blog estimates, including this one.

Three operational steps for the ISV.

1/ Update your partner agreement to reference the new SKU. This happens through your partner manager or Partner Operations.

2/ Switch your customer-facing pricing to reflect Flex Credits or convert your old per-cloud usage estimates to the new model. Most ISVs I've talked to are building a pricing calculator their customers use to estimate activation volume.

3/ Instrument activation tracking in your product. You want to know per-customer how many activations you're driving, both for internal margin tracking and for explaining the customer's bill if they ask.

The instrumentation is the part most ISVs skip and regret. The new pricing is "fair" only if you can show the customer what they're paying for.

The pricing change is part of a coherent push. The AgentExchange Builders Initiative backs smaller ISVs with capital and engineering support. The AgentExchange Go-to-Market App handles enterprise sales mechanics. Data 360 Provisioning with Flex Credits removes a cost barrier for AI-driven ISV products.

Together, the message: Salesforce wants more AI-native ISVs on AgentExchange and is removing friction at the cost layer, the engineering layer, and the sales layer.

For a SaaS founder thinking about whether to build on Salesforce in 2026, the bundle of changes makes a noticeably better case than the 2025 economics did.

A conversation intelligence product (analogous to Gong or Avoma) ingests every meeting recording across its customer base, runs AI summarization on each one, and activates only the meetings the customer's sales team actually opens or shares.

Under the old per-cloud SKU model: the ISV paid for full ingest volume, then again for storage, then again for the AI activation. Three meters, all running.

Under the new Flex Credit model: ingest is free. The AI summarization runs and consumes credits per activation. Storage at rest is free.

Concrete math: a customer ingesting 100K meetings per quarter but only activating summaries on 30K of them (the ones a rep opens). Old model: paying for 100K. New model: paying for 30K. Roughly a 70% reduction in the data-cost line item, with the savings split between the ISV and the customer depending on contract.

• [ ] Confirmed which "ingest vs activate" pattern describes your product → Yes / No

• [ ] Got the Flex Credit rate card from your partner manager → Yes / No

• [ ] Re-ran customer-level unit economics under the new model → Yes / No

• [ ] Updated your partner agreement to reference Data 360 Provisioning SKU → Yes / No

• [ ] Built or updated your pricing calculator for customers → Yes / No

• [ ] Instrumented activation tracking per customer → Yes / No

• [ ] Communicated the pricing change to existing customers (with the math) → Yes / No

A new Salesforce SKU GA'd April 2026 that replaces legacy per-cloud Data Cloud SKUs with unified Flex Credits. Batch ingestion is free and unmetered. ISVs and customers pay only when data activates for an agentic outcome (agent action, automation, real-time enrichment). See the Salesforce Summer '26 ISV strategy blog.

Yes. Batch ingestion into Data 360 is free and unmetered as of April 2026. The cost moved to the activation side: agent invocations, automation triggers, real-time enrichments, model inferences.

No. The revenue share applies the same way to ISV sales. Data 360 Provisioning is a separate SKU for the data and activation costs. ISVs still owe the standard 15% (ISVforce) or 25% (OEM) on their product sales.

Customers can buy directly or the ISV can bundle Flex Credit volume into their own subscription pricing. Most ISVs I've talked to are exposing Flex Credit consumption to the customer as a line item or as part of a tiered pricing model.

The Flex Credit model applies to Data 360 usage. Customers running your Managed Package without Data 360 don't incur Flex Credits. If your ISV product requires Data 360, the customer needs both your product license and a Data 360 SKU.

No. The Security Review process is unchanged. $999 per submission for paid apps, 4 to 5 weeks officially. The pricing model affects data costs, not the review.

Salesforce hasn't published public pricing. Get rates through your partner manager or Partner Operations team. Pricing varies by volume tier and partner agreement.

Sunny Chauhan is the founder and CEO of Appnigma AI, a no-code platform that generates Salesforce AppExchange-ready Managed Packages from natural-language prompts. He holds Salesforce certifications in Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate. Since launching Appnigma in 2024, his team has helped B2B SaaS companies including Warmly, Hyperbound, Pylon, Seam AI, and Avoma ship native Managed Packages and model their data and activation economics on Salesforce.

Originally published June 17, 2026. Last reviewed June 17, 2026. Pricing model details verified against the Salesforce Summer '26 ISV strategy blog and Partner Community guidance current as of the published date.

• AgentExchange Go-to-Market App

• AgentExchange Builders Initiative ($50M ISV funding)

• How does the AppExchange revenue share work

• How ISVs Can Embed Agentforce 360 in Their Products

• Building Agentforce Components for AgentExchange

• Salesforce app development cost

1/ Salesforce blog, ISV Strategy for the Summer '26 Release 2/ Aquiva Labs, Summer '26 Salesforce Release Highlights 3/ Salesforce, Summer '26 Release Notes 4/ Salesforce Ben, Summer '26 Release coverage

What activation pattern does your product run, and have you instrumented the per-customer activation count yet?