What architecture concept is Add-on an example of?

Salesforce uses a metadata-driven, multi-tenant architecture — and Add-on is a great example of how configuration (metadata) drives functionality.

What does Add-on represent in the Salesforce Platform?

Add-on is a platform feature that provides building blocks for extending and customizing Salesforce to meet specific business needs.

How does Salesforce's multi-tenant model affect Add-on?

In Salesforce's multi-tenant environment, features like Add-on share infrastructure across orgs — which is why best practices and limits are important.

Add-on

Platform🟡 Intermediate

Definition

An Add-on in Salesforce is an additional product, feature, or capacity that can be purchased on top of a base Salesforce subscription. Add-ons extend the functionality of your org beyond what is included in your standard license, such as additional storage, API calls, or premium features like Salesforce Shield.

Real-World Example

Streamline Logistics has a Sales Cloud Enterprise license but needs advanced encryption and event monitoring. They purchase the Salesforce Shield add-on, which layers Platform Encryption, Event Monitoring, and Field Audit Trail onto their existing org. This gives them enterprise-grade security without switching to a different edition.

Why Add-on Matters

Add-on is part of the Salesforce platform layer, which provides the foundation upon which both standard and custom applications are built. The platform handles everything from data storage and user authentication to API access and deployment management, making it the backbone of every Salesforce implementation.

Understanding Add-on is essential for anyone who builds on Salesforce, whether they are an admin, developer, or architect. The platform's metadata-driven architecture means that configuration changes—rather than code changes—drive most of the customization, and this feature is a key part of that model.

How Organizations Use Add-on

•Wonka Ltd — Built a custom application on the Salesforce platform using Add-on to manage their entire vendor qualification process. What used to live in spreadsheets is now a structured, auditable system with automated notifications, approval routing, and real-time dashboards.
•Dunder Mifflin Inc — Used Add-on to extend their Salesforce org beyond traditional CRM. They built project management capabilities directly on the platform, eliminating the need for a separate tool and giving their team a single interface for customer data and project delivery.
•Hooli Technologies — Applied Add-on to create a partner portal where external distributors can log in, view their accounts, submit orders, and track shipments—all powered by Salesforce without any custom infrastructure.