Build Scalable Customer-Facing Apps on Salesforce Beyond Experience Cloud Limits

Page view caps, concurrent user limits, and API quotas tied to license type are what a customer portal hits first — when registrations climb toward the hundreds of thousands, or when traffic spikes on launch day. The constraint is not the design. It is what a single Experience Cloud org will carry.

The problem is straightforward. You need full control over branding and user experience, yet you also need to keep Salesforce as the system of record for data, workflows, sharing rules, and now agentic features. Rebuilding everything from scratch on an external platform duplicates effort and creates compliance gaps. Staying inside Experience Cloud eventually forces trade-offs on scale or customization.

Current state of customer-facing apps on Salesforce

Most teams start with Experience Cloud because it provides built-in authentication, Lightning components, and direct access to Customer 360 records. As volume increases, the same org that once felt flexible begins to constrain options. Page views often sit between 500,000 and 1 million per month per org depending on edition, while API allocations remain linked to license type. Concurrent user handling becomes unpredictable at the upper end of community licenses.

Heavy custom builds outside Salesforce attempt to solve this by moving the frontend entirely to React or another framework and calling APIs. These projects quickly grow complex because teams must recreate authentication flows, permission checks, and audit trails that Salesforce already manages. The result is longer delivery cycles and ongoing maintenance of duplicated logic.

The better way: Headless architectures with Multi-Framework and Headless 360

A lighter path decouples the presentation layer from the Salesforce backend while preserving the platform’s security model. Headless 360 exposes data, workflows, and business logic through APIs, MCP tools, and CLI commands so that agents or custom code can interact directly without a browser. Multi-Framework adds a runtime that lets you build and run React applications natively on the Agentforce 360 platform with built-in authentication, GraphQL access, and Apex invocation.

This approach keeps the heavy lifting on Salesforce while giving you complete frontend freedom. You avoid rebuilding sharing rules or Field-Level Security because the apps inherit those controls. Development cycles shorten because you use familiar open-source toolchains such as Vite and Tailwind alongside Salesforce SDKs that respect governor limits. The same governance tools that apply to Lightning components extend to these React micro-frontends.

Headless Architecture works here because it separates concerns without sacrificing the single source of truth. Teams that adopt this pattern report faster iteration on branded interfaces while still using Agentforce for conversational or agent-delivered components across web, mobile, and Slack surfaces.

How it works in practice

Start by confirming your org runs on Hyperforce and carries an Enterprise, Performance, or Unlimited edition. Enable Salesforce Multi-Framework in Setup or through a scratch org definition. Generate a React template with the CLI command sf template generate ui-bundle or let Agentforce Vibes create initial components from natural language descriptions.

For identity, configure Headless Identity so that login and registration remain handled by Salesforce even though users never see an Experience Cloud site. An Experience Cloud site can still serve as the backend account and contact store if needed. Deploy the React application through the CLI; it appears in the App Launcher and supports local preview during development.

Agentic experiences become available through the Experience Layer. Agents can surface interactive cards for approvals or status updates while respecting the same permissions and Field-Level Security (FLS) that apply to internal users. MCP tools provide dynamic discovery of capabilities, and the Trust Layer supplies guardrails such as zero data retention and toxicity detection.

Licensing flows through existing editions rather than a new SKU. External Apps licenses support high-scale API-heavy experiences and can reach roughly two million users when additional API and storage capacity is purchased. Consumption elements appear through Agentforce Flex Credits, typically priced at around $500 per 100,000 credits source. Standard actions consume about 20 credits while voice interactions cost more. Monitor usage in the same dashboards used for other platform limits.

Honest limitations and considerations

Multi-org strategies help with extreme scale but add routing complexity and data synchronization overhead. Governor limits still apply to individual transactions even when the frontend sits outside Experience Cloud. Consumption-based pricing means heavy agent usage can increase costs, so teams need clear visibility into Flex Credit consumption before rolling out broad agentic features.

Early availability of some MCP servers and Multi-Framework features required English as the default language, though this restriction has eased in later releases. Production support for Multi-Framework stabilized with Summer ’26 and later. Data quality and permission model hygiene remain prerequisites; moving to headless does not fix underlying record access issues.

Decision Framework

Choose the lighter headless path when your primary needs are frontend design freedom, moderate to high user volumes under two million, and continued use of existing Salesforce workflows and Data 360 context. It also fits when you want to introduce Agentic Architecture without rebuilding identity or compliance layers.

A heavier or fully custom build outside Salesforce becomes warranted when you require millions of concurrent users that exceed even multi-org sharding, when regulatory requirements prohibit any Salesforce-hosted identity, or when the majority of compute must run on serverless functions outside the platform for cost or latency reasons. In those cases, plan for explicit data synchronization and separate audit mechanisms from the start.

Next step

Want help implementing scalable customer-facing apps on Salesforce beyond Experience Cloud limits? Book a meeting to discuss your needs. Review current licensing options in the Support Portal for External Apps and Agentforce Flex Credits.