For Salesforce Partners

Deliver the wow. Keep the margin.

Consulting teams, ISVs and OEM partners ship portals, consoles and guided processes on 85+ reviewed components. Same suite on every engagement, nothing rebuilt twice.

85+
components across the suite
30+
five-star reviews
3
packages, one subscription
Listings board
Listings board
What you deliver

Client work that looks like a product.

Real screens from real orgs. Portals, dashboards and guided flows the client's admins can own after handoff.

Partner order desk

A partner portal in weeks. Inline quantities, PO uploads and delivery rings, no Salesforce chrome in sight.

85+
components

You never rebuild them for the next client.

Fall course catalog

The client's brand, not ours. One gallery, six records, the whole catalog.

Revenue cube without a report

Reporting without the report builder. A live pivot on opportunities, totals on both axes.

See them in real orgs
Agent Skills

A delivery team with an AI assistant that knows the library.

Point Claude Code or Cursor at the Avonni skills and MCP server. Your consultants describe the client's screen, review the result and hand it off. Same components, same review, faster.

Shown in Claude Code

One prompt. One deliverable.

The Avonni skills plan the screen, check every component against the real catalog and validate the file before anyone deploys it.

Salesforce logo

Works with Claude, Cursor, Copilot, Gemini and Agentforce

claude — ~/salesforce/avonni-org
✻ Welcome to Claude Code!cwd: ~/salesforce/avonni-org
Build a screen flow to review open Cases and close the selected ones.
I'll check the real Flow Screen Components catalog before building.
avonni - list_components (MCP)(toolset: "flow")
75 components
avonni - get_component_docs (MCP)(name: "datatable")
Properties and outputs loaded
Skill(avonni-flow-components)
Bash(node scripts/create-flow.mjs)
force-app/main/default/flows/Review_Open_Cases.flow-meta.xml
Bash(node scripts/validate-flow.mjs)
Flow valid: 1 screen, Data Table + Button
Done. Reps pick the Cases in the table, then close them in one click. Nothing is deployed until you say so.
Try "deploy it to the sandbox"
? for shortcuts
Consulting, ISV, OEM

Three ways partners build on Avonni

Whether you deliver client projects, ship your own AppExchange app, or embed components in a product, the same reviewed component suite does the heavy lifting.

Portal
shipped
Record pages
configured
Guided flow
in build
Consulting & SI

Deliver faster, keep the margin

Skip the custom UI work on every project. Configure record pages, portals, and consoles from ready components and put your billable hours where the client value is.

Talk to us →
A
Your app on AppExchange
★★★★★
Security review passed
ISV

Ship your app on production-ready UI

Embed Avonni's UI components in your Salesforce app instead of building and maintaining your own. Security reviewed, native, and ready for the AppExchange.

Talk to us →
Your product
OEM

License components for your product

Bundle Avonni components under a dedicated OEM arrangement so your customers get the full UI layer as part of your offering. We work out the terms with you.

Talk to us →
Where to build it

One suite, every surface your clients need

Most partner projects touch a portal, a Lightning page, and a guided process. Avonni covers all three, so you carry one subscription across the whole engagement.

For client work
Portals & sites

Experience Cloud Components

Client portals, partner hubs, and self-service sites that match the client's brand. The most common partner deliverable, shipped in weeks.

Learn more →
Lightning pages

Dynamic Components

Record pages, consoles, and dashboards built visually, so the client's admins can own them after handoff.

Learn more →
Guided processes

Flow Screen Components

Rich screens for intake, onboarding, and approvals inside Salesforce Flows, without custom Lightning work.

Learn more →
Why partners choose Avonni

Built to stand behind your delivery

When you put your name on a project, the components underneath have to hold up. These do.

Security reviewed

Every package passes the AppExchange security review, so client security teams sign off without a fight.

100% native

Components run inside the client's org with no external services, so there is nothing extra to host or explain.

Updated every month

New components and fixes ship on a steady cadence, and they survive Salesforce releases.

A direct line to the product team

Partners talk to the people who build the components, not a ticket queue. Roadmap questions get real answers.

Partner FAQ

Questions partners ask first

How does partner pricing work?

Partner and OEM terms depend on how you use the components and how many client orgs are involved. We set them up with you directly, so reach out and we will walk through the options for your model.

Can we white-label the components?

White-label and embedding scenarios are handled through an OEM arrangement. Tell us what you are building and we will confirm what is possible for your case.

Do the components work across multiple client orgs?

Yes. Each package installs into a client org from the AppExchange, so you deploy the same components across every client project you run.

Can we get a demo org to build in?

Every plan starts with 10 free licenses, which is enough to build and demo real components before a client commits. If you need a dedicated partner setup, talk to us.

From a Salesforce customer
“In our experience, Avonni's product is unparalleled. We considered building our own global components or even delving into our own Lightning Web Components (LWC), but Avonni's value proposition was unbeatable.”
Tyler Teachman
Hitachi High Tech America

Deliver more Salesforce, build less of it

Join the partners shipping client work faster on a reviewed, native component suite. Start the conversation and we will map it to how you deliver.