Build customer portals, partner hubs, and community sites on Experience Cloud with components that match your brand and respect your sharing rules.

Every component works for authenticated and guest users out of the box, so you can open a portal to customers without extra plumbing.
Components honor your existing sharing rules and permissions on every record.
Bind to Salesforce records through queries, CMS collections, or manual setup.
Works across Experience Cloud site types, so you are not boxed into one.
These components are part of the Avonni suite the MCP server exposes to your AI tools.
Your AI assistant can look up components and their real settings instead of guessing.
Answers come from documented component data, so the output matches the package.
Want the details? Learn about the Avonni MCP Server →
The same components underneath. What changes is where you build, and who does the building.
One component, dropped straight onto a Lightning page.
Several components assembled into one custom layout.
Portals and community sites, in your brand.
Wizards and intake forms inside Flow Builder.
The same components, as tags in your own code.
Most teams pair Experience Cloud Components with Dynamic Components: the portal your customers see, the pages your team works in.
Experience Sites are quoted separately. Portal and community licensing depends on your setup, so reach out and we will scope it with you.
Yes. They support authenticated and guest users, and respect the sharing rules and permissions you already set.
Colors, fonts, spacing, and layout are configured visually, with advanced CSS classes when you need finer control.
The components work with Aura and LWR sites, so you are not locked into one build.
Experience Cloud components are part of the same Avonni suite, alongside Flow Screen, Dynamic, and LWC components.
Start with 40+ components, keep your data where it is, and ship a branded Experience Cloud site your external users will actually use.
Available on the AppExchange