55+ LWC components on AppExchange

Ship Salesforce UI without rebuilding the basics

Data tables, kanbans, calendars, and maps you import as tags. A built-in query engine handles the data. You keep VS Code, SFDX, and git.

Start freeView documentation
55+
LWC components
12
data-driven with Query Mode
10
free production licenses
accountList.html
<template>
<avonni-dd-datatable
header-title="Key Accounts"
query={query}
columns={columns}
search-fields={searchFields}
filters={filters}
show-pagination>
</avonni-dd-datatable>
</template>

One tag stands in for the LWC, Apex, and CSS you would otherwise write and maintain.

Where the time goes

The build is the quick part. The upkeep is the rest.

Every Salesforce team ships the same surfaces on every project: a data table with inline edit, a kanban tied to a picklist, a calendar across objects. The first version is fast. Keeping it current across releases, accessibility, and new requirements is what adds up.

The headline feature
55+

Components maintained for you

Upgrades, accessibility, and Salesforce release compatibility ship with the package. Your team spends its time on business logic instead.

12

Data-driven components with a built-in query engine.

1 tag

Imported like any standard Lightning base component.

10

Free production licenses, with unlimited sandboxes.

How it works

Install, import, ship.

1

Install

Add the Avonni LWC Components package from AppExchange. One package, 55+ components.

2

Import

Drop any avonni-* component into your LWC. It behaves like a standard Lightning base component.

3

Ship

Your code stays focused on business logic. Avonni maintains and updates the UI components.

Query Mode

Data-connected components, zero Apex to write.

Most libraries hand you UI and leave the data plumbing to you. Avonni's 12 data-driven components carry a built-in query engine: set the object, fields, and filters, and the component handles the SOQL, pagination, caching, and refresh. If you would rather bring your own data, static mode renders any items array you pass it.

accountList.js
query = {
objectApiName: 'Account',
addedFields: ['Name', 'AnnualRevenue'],
filter: "Industry = 'Technology'",
orderBy: 'Name ASC',
limit: 100
};
✓
SOQL handled for you
✓
Pagination built in
✓
Caching and refresh
✓
Search and filtering
✓
Inline editing and export
The difference in one line

One tag, or the code behind it.

1 tag
With Avonni
Import the component and configure it. Maintenance travels with the package.
vs
800–1,200
Lines behind a hand-built data table
LWC markup, JavaScript, Apex, CSS, and tests, plus everything you maintain afterward.

A good split: reach for Avonni on the heavy, well-solved surfaces like tables, boards, and calendars, and keep your own code for what is genuinely custom to your org. Ten generated data components leave an org owning 10,000+ lines of code. The Avonni catalog is discoverable, so your AI assistant writes correct avonni-* markup instead of another black box.

Side by side

The full checklist, line by line.

Build it yourself, with or without AI
Avonni LWC Components
Data table with inline editing
800 to 1,200 lines to own, written or generated
About 30 lines of config
Kanban with drag and drop
The demo is fast, rollback and edge cases are yours
About 30 lines of config
Scheduler with timezones
Timezone and DST edge cases are yours to test
About 30 lines of config
Apex controller and test classes
Required for each component
Not needed in query mode
Pagination, search, filtering
Custom logic every time
Built in
Error, loading, empty states
Built and tested by you
Included
SLDS styling and accessibility
Yours to build and test
Included, with styling hooks
Salesforce release compatibility
Regression tests three times a year
Maintained managed package
Security review
Your code, your review
AppExchange security reviewed
Upgrades
Manual refactors
Package updates
AI assistant compatibility
A black box to the AI
Discoverable component catalog

AI makes the first version fast. The left column is what your team still owns after the demo works.

Who builds with it

Built for teams shipping Salesforce projects.

Consulting firms

Drop in the tables, boards, and calendars a project needs, and spend the recovered weeks on the client's business logic.

Platform modernization

Bring rich grids and interactive surfaces to Lightning with a fraction of the code, and keep them current as Salesforce evolves.

Teams building with AI

Let your AI tools focus on the code that's custom to your org, and lean on Avonni for the commodity UI so the codebase stays small and readable.

ISVs on AppExchange

Ship polished UI in your managed package by taking Avonni as a dependency instead of maintaining your own component library.

Prefer no-code

Not writing LWC? There's a no-code path.

Admins and BAs get the same components, configured with clicks instead of code.

Building a page

Dynamic Components

A visual, no-code builder for Lightning pages. 85+ components, configured with clicks.

Learn more →
Running a guided process

Flow Screen Components

70+ components for Screen Flows, dragged and dropped in the Flow Builder. Free up to 10 users.

Learn more →
Put a number on it
See the five-year cost, side by side

This page shows what one Avonni tag replaces. The calculator shows what that saves you: build plus maintenance across Salesforce releases, with your own numbers.

Open the cost calculator

Start with the components that are already solved.

10 free production licenses. Unlimited sandbox access. Installed inside your Salesforce org in a couple of minutes.

Start freeTalk to us