Aquiva Engineering · Internal open source
AqLib is the Salesforce component library our engineers build between projects and reach for on the next one.
LWC components, Apex modules, and the architectural patterns behind them: hardened for security review, built to be customized, and maintained by the engineers who use them.
What's inside
Six categories, one library. Every entry is documented, tested, and ready to drop into a project.
Lightning Web Components for dynamic, responsive interfaces: inputs, datatables, virtual scrollers, and setup assistants.
Browse →Backend building blocks: query selectors, secure DML, triggers, logging, mocks, and HTTP services.
Browse →Larger solutions that cover extensive requirements out of the box: enterprise framework, mapping tool, and retention jobs.
Browse →Architectural blueprints that carry whole features: state management, wire-service sync, and the design decisions behind them, written down as working examples.
Browse →Ready-to-run scripts for everyday org chores: deleting debug logs, resetting a user after a sandbox refresh, and formatting currency.
Browse →A curated list of third-party tools we rate, in the spirit of awesome lists: fflib, jsforce, Avonni components, and the browser extensions we open every day.
Browse →Why it exists
We ship products through AppExchange security review and custom builds into live orgs. What recurs gets extracted, hardened, and reused.
Passing security review is one of the hardest parts of ISV development. The library encodes what past reviews taught us: secure defaults everywhere, and every database write checked against object and field permissions before it runs. The safe path is also the short one.
Recurring patterns across projects become small, reusable components with configurable parameters instead of baked-in assumptions. What stays in project code is the business logic that makes each product different, and reuse never boxes in a design.
AqLib is part of Aquiva Engineering, kept current by certified engineers who run it on live projects and fold what they learn back in.
Clients own their product. Aquiva owns the components, tools, and know-how used to build it. Reuse flows one way: client materials never enter the library, and what makes each product unique stays with its owner.
Who it's for
Three levels of access: the docs are open to everyone, the source code is shared with customer engineering teams, and contributions come from Aquiva engineers.
Browse anytime, no account needed: usage, parameters, and design notes for every component, plus a small collection of ready-to-run snippets. If you are evaluating how we build, start here.
Browse the docs →Aquiva and customer teamsThe GitHub repository is open to our engineers and to customer engineering teams: when we work together, we are ready to share the years of our knowledge that helps to ship your project.
GitHub ↗Aquiva engineersOur internal call to action. AqLib is part of onboarding and everyday work: start from the template, ship from the library, and if you have built the same thing twice, it belongs here.
How to contribute →