Aetrum is now Trevaun.
On November 10, 2026, one year after we started, Aetrum LLC took a new brand name. Here is what changes for you, and what does not.
Aetrum LLC now does business as Trevaun. Same company, new brand. Read the noteAetrum LLC now does business as Trevaun. You followed an Aetrum link. Aetrum LLC now does business as Trevaun: same company, new brand. What changedAetrum LLC now does business as Trevaun.
What we learn in real Salesforce orgs: access, credentials, integration dependencies, migrations, and governing AI agents.
On November 10, 2026, one year after we started, Aetrum LLC took a new brand name. Here is what changes for you, and what does not.
Senior architecture leadership for the hours you need: what a fractional Salesforce architect does, what it costs, and when it fits.
Part 1: An agent is not a new security model. It is a new consumer of the one you already have. Two doors into the org, one access surface, and five questions to answer before go-live.
AI generates Apex, Flows, and LWC faster than most teams can spec them. Build speed stopped being the constraint. What nobody moved to match is the review of integration dependencies, agent access, and credential governance.
Part 6, the final post. A dependency map is correct the day you draw it and wrong a quarter later, because the org keeps moving and nothing native keeps the map current. Keeping it true is an operating model, not a document.
Part 5 of the series. Salesforce records who changed a credential and when it expires. It does not record who is accountable for it. That gap is where renewals fall through.
Part 4 of the series. A Named Credential looks like an endpoint and a login. Underneath, it is often a certificate dependency, and Salesforce does not draw that line for you.
Part 3 of the series. A Connected App is one node in Setup with half a dozen invisible edges. In 2025 those edges became a breach blast radius and a forced migration at the same time.
Part 2 of the series. A single inbound API certificate, an expiry nobody tracked, and why the move to short-lived certificates makes mutual TLS the first place the dependency graph bites.
Part 1 of a series. The invisible edges between certificates, Connected Apps, and Named Credentials, and why the short-lived certificate era makes mapping them matter more than ever.
Part 3 of 3. The forcing functions most teams discover too late: reporting, integration, and scale as design inputs in month one, not discoveries in month eighteen.
A consolidated timeline of the five mandatory step-up authentication gates rolling out June through August, with an architect's view of each control and a prioritized prep checklist.
A 30-minute audit checklist for Connected Apps and OAuth access, anchored to the May 11 ISV partner deadline.
Part 2 of 3: Why master-detail vs. lookup is the most consequential choice nobody escalates.
Part 1 of 3: The data model decision that determines whether year two is a victory lap or a re-platforming project.
A practical guide for developers, architects, and consultants who want better decisions, faster.
We reply within one to two business days.