Addepar vs Altruist 2026: Custody, Reporting and Cost

Decide whether you are buying custody or portfolio intelligence

Choose Addepar when your central problem is understanding and reporting on wealth across custodians, legal entities, and public and private investments. Choose Altruist when your central problem is running custody, account opening, trading, billing, and reporting through a connected operating platform.

Portfolio accounting software organizes investment holdings, transactions, valuations, and performance into records that advisors can analyze and report.

TL;DR: Addepar is the stronger starting point for a complex reporting and data-modeling requirement; Altruist is the stronger starting point for a custody-centered operating model. They can address different layers of the same firm's architecture, so an either-or purchase decision needs to begin with the system you actually intend to replace.

There is also an ownership development to understand before signing. Vanguard announced an agreement to acquire Altruist on August 26, 2026, with closing subject to customary conditions and regulatory approvals, according to Vanguard. That announcement describes a planned standalone business retaining its brand, leadership, and advisor focus. It establishes an acquisition agreement, rather than confirming a completed closing.

Addepar remains privately held, with ownership spanning founders, institutional investors, and employees, according to LegalClarity. Exact ownership percentages are not publicly disclosed. Neither product should be treated as discontinued or merely an old name for the other.

Our recommendation is architectural rather than a universal ranking: resolve the custody decision first, then assess whether the reporting available around that custody arrangement meets your client obligations.

Key Takeaways

• Choose Addepar for a portfolio-data problem involving complex ownership, alternative investments, or reporting across custodial relationships.

• Choose Altruist for a custody decision where connected onboarding, trading, billing, and reporting match the firm's operating model.

• Addepar pricing is Quote-based. Altruist publishes portfolio-accounting terms, but those terms do not represent every possible client or firm expense.

• Require demonstrations using representative household structures, transaction histories, fee arrangements, and exceptions rather than polished sample portfolios alone.

• Buying both deserves consideration only when each has a defined responsibility and the required data connection has been confirmed.

• Workflow automation belongs above the selected systems when it coordinates exceptions and review; it should preserve their accounting and custody responsibilities.

Who this is for

This comparison is for an RIA operations lead preparing a shortlist, replacement recommendation, or implementation budget. It is particularly relevant when the firm is deciding whether disconnected reporting tools or its current custodial workflow create the larger operational burden.

Small-firm prevalence: 92.8% employ 100 or fewer people according to Investment Adviser Association (2026 report, covering 2025). That industry context supports a practical evaluation question: who will own the configuration and exception work after the implementation team leaves?

A firm does not need a particular headcount or asset threshold to justify either platform. Complexity matters more: account registrations, held-away assets, ownership relationships, reporting commitments, and investment restrictions can create operational demands that a headline asset figure misses.

Red flags: you need custody but are evaluating reporting software as its replacement; you require external-asset coverage that nobody has demonstrated; you have no named owner for migration reconciliation.

Start with a written replacement boundary. State whether you intend to replace custody, portfolio accounting, billing, reporting, or the handoffs among them. A platform can satisfy several requirements without eliminating every connected application.

If custody is staying where it is and reporting is the actual purchase, the Black Diamond versus Addepar comparison provides a more directly comparable reporting shortlist.

How we evaluated the operating decision

We evaluated public product descriptions, published subscription terms, API documentation, ownership information, and independent industry commentary. This is a buyer's guide based on those materials; it does not report hands-on testing, customer interviews, or measured implementation results.

The following weights are our proposed evaluation method, not vendor statistics or research findings. They emphasize architectural fit before interface preferences. Adjust them before evaluating vendors so a persuasive presentation does not quietly change the decision criteria.

Score demonstrated capabilities against your requirements, rather than awarding points because a product page mentions a feature. Multiply each normalized score by its weight to assemble an internal comparison.

Keep mandatory requirements outside the weighted score. An unsupported account registration, unacceptable contractual term, or missing critical data source should remain a disqualifier even if other categories score well.

We have deliberately not assigned vendor scores. Public documentation establishes product direction, but it cannot establish how either platform handles your firm's data, permissions, exceptions, or negotiated service scope.

Compare the capabilities at the same level

Addepar describes public and private asset modeling, ownership structures, tailored reporting, a client portal, alternatives management, and complex billing, according to Addepar. Those capabilities explain its appeal for consolidated portfolio intelligence, while leaving implementation scope and commercial terms to be established.

Altruist's custody-centered scope includes account opening, trading, portfolio management, billing, and reporting. The practical comparison is therefore how each platform fits the responsibilities you need covered.

“Supports alternatives” is especially easy to misunderstand. Offering access to an investment does not establish that a platform can represent every external holding, ownership chain, or historical cash-flow pattern your reporting requires.

Similarly, a reporting capability does not establish trading authority, and a data connection does not establish complete historical coverage. Ask for the field definitions, supported account types, refresh expectations, and exception process behind each affirmative answer.

For a broader reporting and operations shortlist, the Orion versus Addepar comparison helps frame another architecture worth evaluating.

Addepar: select it when the wealth picture is the difficult part

Addepar's strongest fit in this comparison is a firm whose reporting problem extends beyond the accounts held at its primary custodian. The deciding requirement might be an ownership hierarchy, an externally held investment, or a client reporting obligation that demands more flexible analysis.

Its limitation is the responsibility that comes with modeling. A configurable representation of wealth still needs agreed definitions, accurate source data, and people who can explain adjustments. Buying analytical depth does not resolve inconsistent household records or missing investment history.

Implementation should begin with a representative ownership map and a source inventory. Identify authoritative records for account identity, transactions, valuations, classifications, and billing instructions. Establish how corrections propagate and who approves changes that affect previously delivered reports.

Request a demonstration that follows an exception through correction and report regeneration. A report that looks right once is less useful than a process that produces an explainable result after a late valuation or ownership adjustment.

A proposed workflow from US Tech Automations could begin when an approved portfolio export arrives: validate its schema and reporting date, compare expected accounts with received records, and create review tasks for missing or changed data. The output would be an exception register linked to source records. Prerequisites include authorized API access or an approved export, stable account mappings, and a task-system connection; an operations reviewer would approve ownership changes and report release.

This orchestration would sit above the portfolio platform. It would neither calculate replacement performance figures nor silently repair investment records. Its value would depend on whether the firm has a recurring coordination problem that native workflows leave unresolved.

If you are comparing reporting architectures for complex households, the Addepar, Orion, and Black Diamond guide offers another way to structure that shortlist.

Altruist: select it when custody drives the operating model

Altruist's strongest fit is a firm willing to evaluate custody and supporting operations together. The attraction is organizational: account opening, investment operations, billing, and reporting can share a platform context rather than requiring the firm to coordinate every handoff externally.

The limitation is that adopting a custody-centered platform creates a custody-centered implementation. Evaluate investment availability, account eligibility, service responsibilities, client authorizations, and transfer exceptions before treating software consolidation as the deciding benefit.

Connected third-party account pricing also should not be confused with proof of feature parity across custodians. Receiving external account data does not by itself establish identical trading, billing, reporting, or service capabilities for every account.

Implementation should start with an account and asset eligibility review. Separate accounts that can move as expected from those needing additional documents, asset-specific handling, or a different operating arrangement. Determine who tracks unresolved transfers and how the advisory team sees their status.

Then test the daily work: an opening request with missing information, a restriction that prevents the intended portfolio action, a billing exclusion, and a client report requiring explanation. These examples reveal responsibilities that a normal-path presentation can miss.

The ownership announcement adds due diligence questions rather than an automatic reason to reject the platform. Ask which commitments appear in current agreements, which are roadmap statements, and how material changes would be communicated. Do not budget assumed future benefits from the proposed acquisition.

Pricing and TCO: distinguish software charges from operating cost

Pricing checked October 14, 2026.

Addepar is Quote-based. Its public pricing route led to a sales inquiry page rather than a published rate card. Request a written scope covering the platform, required modules, implementation, data services, support, and any integration access needed for your design.

For Altruist, External-account rate: $1 per account monthly after 100 free according to Altruist. The same published terms exclude Altruist brokerage accounts from the portfolio-accounting software fee and note that other brokerage or service charges can apply. The page carries a 2023 version identifier, so confirm its applicability in the current agreement rather than assuming it is a newly issued schedule.

The subscription is only part of the comparison. Include data cleanup, historical reconciliation, parallel operation, client communications, employee training, and the cost of retaining systems that the purchase does not replace.

Avoid a misleading comparison between a complete enterprise proposal and an isolated portfolio-accounting charge. Ask both vendors to price the intended operating scope, and separate firm expenses from expenses borne by client accounts.

Custody revenue sources discussed: 3 according to InvestmentNews (2026). Its analysis identifies ticket charges, fund-related revenue sharing, and net interest income as historical custody economics. This is industry context, not a claim that every mechanism applies to Altruist; use it to ask how the applicable custody arrangement earns revenue.

The following scenarios are calculated illustrations of the published external-account formula above. They assume unchanged eligible account counts throughout each billing period and exclude other charges; they are neither customer examples nor vendor quotes.

For a concrete illustrative workflow, suppose the firm connects 250 eligible external accounts: subtracting the published 100-account allowance leaves 150 chargeable accounts, and multiplying by $1 produces a $150 monthly accounting charge before other expenses, according to Altruist. If that same firm separately uses Addepar, a reconciliation process could compare the connected-account inventory with authorized portfolio-query results using portfolio_id; its documentation recommends asynchronous Jobs processing for queries covering 100+ entities, according to Addepar. That comparison would require confirmed data access and account mappings, and an operations reviewer would investigate differences before accepting the billing inventory; it does not assume an existing connection between the vendors.

Prove the handoffs before expanding the rollout

A useful acceptance exercise follows an account from its source record to its final report and billing treatment. Require the team to explain which system owns each value, which transformations occur, and where exceptions become visible.

Start with representative records rather than the cleanest records. Include shared ownership, an excluded asset, a stale valuation, a registration issue, and a correction to historical data. Success means the team can explain and recover from each condition, not merely produce attractive output.

A second proposed US Tech Automations workflow could start when an authorized Altruist status export becomes available: match accounts to the firm's CRM, identify missing onboarding information or unresolved transfer items, and assemble an internal review queue. Prerequisites would include a supported export or approved integration, documented status meanings, permission to process the data, and reliable CRM identifiers. An operations lead would review exceptions; client messages, trading decisions, and money movements would remain subject to the firm's separate approval processes.

For either architecture, require an explicit failure state. Missing data should produce “unavailable” or “needs review,” rather than a successful-looking empty result. Repeated inputs should not create duplicate tasks, and a failed run should have a named owner.

Before expanding beyond the initial acceptance scope, document reconciliation results, unresolved limitations, access permissions, and recovery steps. Preserve the previous system or export evidence long enough to investigate discrepancies under the firm's retention policies.

Compare native workflows, no-code tools, and an internal build fairly

The alternative to custom orchestration may be native platform configuration. If existing billing controls, reports, task queues, or integrations cover the requirement, using them can reduce the number of moving parts your team must maintain.

Zapier, Make, and n8n can also support run histories, retries, error branches, and audit evidence when configured appropriately. An internal engineering team can build similar controls. Neither approach should be dismissed as inherently unsuitable merely because it is assembled by the buyer.

The ownership question is what matters. Someone must design and maintain observability, idempotency, escalation, access controls, credential handling, and connector changes. A successful initial run does not establish that these responsibilities have been addressed.

A proposed managed design could specify different responsibilities: source-linked exception records, duplicate suppression based on approved identifiers, controlled retries, and escalation rules assigned to named roles. Those are configurable design requirements, not exclusive capabilities or promised results.

Compare the options against the same acceptance exercise. Require each proposed approach to show what happens when data arrives late, credentials stop working, an account identifier changes, or a reviewer rejects an item. Choose the approach whose controls and ongoing ownership your firm can sustain.

Questions to resolve before the purchase

Is Addepar a replacement for Altruist custody?

No, Addepar should not be treated as a replacement for Altruist's custody function. Its portfolio-data and analysis role belongs in a different architectural decision. If you are moving assets, assess the receiving custodian separately from the reporting platform that will describe those assets.

Can Altruist replace a separate reporting platform?

Yes, if its reporting meets the firm's actual requirements. Reproduce representative review packets and investigate external holdings, ownership structures, historical returns, and billing treatment before retiring another system. A familiar report layout alone does not establish equivalent data coverage or calculations.

Can an RIA use both platforms?

Potentially, if the required data access and contractual permissions are confirmed. Define custody, reporting, and billing responsibilities before designing the connection. Do not assume that purchasing both creates a supported integration or that every relevant field transfers automatically.

Which platform is cheaper?

The cheaper option cannot be determined without matching the intended scope and accounting for implementation. The public accounting terms and a negotiated platform proposal describe different purchase boundaries. Compare the cost of the resulting operating model, including systems retained and staff responsibilities.

Should the Vanguard announcement change the shortlist?

It should change the due diligence questions, rather than automatically determine the selection. Distinguish signed commitments from expected future benefits, and request current information about closing status and product continuity. Evaluate present capabilities without treating an acquisition plan as a guaranteed roadmap.

When NOT to use US Tech Automations?

Use a simpler existing tool when native reporting already meets the requirement, a controlled export handles the occasional handoff, or your team can maintain a small no-code workflow. Additional orchestration is difficult to justify without authorized data access, a recurring coordination problem, and a named reviewer for exceptions.

Make the choice around the responsibility you need covered

Select Addepar when consolidated portfolio intelligence is the requirement that existing systems cannot satisfy. Select Altruist when custody and its connected operational tools fit the intended operating model. Consider both only after demonstrating the required connection and defining which system owns each responsibility.

The final purchase record should contain the accepted scope, disqualifiers checked, representative outputs, reconciliation findings, current commercial terms, and the person responsible for unresolved exceptions.

Where a recurring handoff remains, the workflow approach described by US Tech Automations provides a basis for specifying a proposed design around authorized inputs and human review. Keep the platform decision grounded in custody and reporting requirements, then add coordination only where the acceptance exercise shows it is needed.