every model spec’d & versioned · Concordance-tested 2×changelog →

Comparison

Worthune vs BridgeFT

BridgeFT and Worthune are both API-first and both sold to firms and fintechs building their own products, but they are different layers. BridgeFT is a multi-custodial data aggregation platform: positions, tax lots, cost basis, held-away accounts, and household data from custodial feeds. Worthune does not aggregate. It holds the household as a planning record, projects it, proposes strategies, and fires webhooks when the plan drifts. A product can use both: BridgeFT for the data pipe, Worthune for what the household should do next.

Every claim below about BridgeFT carries the page it was read from and the date. Oldest check on this page: .

Worthune

Unified household management, a whole-household planning engine, and verified financial models, delivered as a REST API, an MCP server, SDKs, and embeds that customers ship under their own brand. Every model has a published spec and returns a per-run audit record.

Wealth-management firms and the platforms that serve them, and developers at fintech, wealthtech, banking, and AI companies.

BridgeFT

API-first wealthtech infrastructure: a multi-custodial data aggregation platform with a REST API, analytics, and an advisor application.

RIAs, TAMPs, fintechs, and developers.

Side by side

Sourced facts only. Where a cell says a vendor does not publish something, that means we looked at the page named in the sources below on the date shown and it was not there — not that the answer is no.

WorthuneBridgeFT
Account aggregationNo — Worthune does not aggregate accounts or connect custodial feeds; households are kept current by bulk import of the customer's aggregator or custodian exports, with a dry runYes — a multi-custodial data aggregation platform, including held-away accounts
How households are modeledA versioned household record the customer's product owns through the API: members, accounts, incomes, and obligations, re-projected on change, with signed webhooks when a stored plan's numbers drift and a decision history per householdClient and household information is a data category in the API
How it is deliveredREST API, MCP server, and a one-script-tag embedA REST API (the WealthTech API) and an advisor application, with data aggregation, analytics, and application modules
Programmatic APIYes — REST and MCP, no key required for the three sample modelsYes — public documentation, including authorization guides for custodial feeds
Client-facing portal or appNo app of our own; household embeds and a white-label reference build ship under the customer's brand, with attribution removal on GrowthNo portal of its own; custom client portal experiences built on the API are a stated use case
Free tier or trialThree models, no signup and no key, attribution requiredA development sandbox is listed; no free trial is stated
Entry priceFree for three models; $495/month for the full catalogNot stated publicly

Where BridgeFT is stronger

The custodial data pipe, already built

BridgeFT connects to custodial feeds, delivers positions, tax lots, and cost basis through an API, and covers held-away accounts, with public documentation and a development sandbox. That is hard, unglamorous infrastructure, and a firm that needs clean custodial data in its own product would otherwise spend a long time building it. Worthune does none of it.

When Worthune is the wrong choice

If what you need is custodial data

Worthune expects you to bring data: households are kept current by bulk import of an aggregator's or custodian's exports. If you do not have that data flowing yet, start with an aggregation platform like BridgeFT; Worthune is the layer that plans on top of it.

Our case

Where we think the difference actually matters

This section is our opinion rather than sourced fact, and it is marked that way on purpose — the table above is what a source URL can settle, and this is what it cannot.

What the data means for the household

Multi-year projections, coordinated strategies, and tax-aware decisions on the household record, plus Lodestar proposals an advisor approves.

A record that notices change

Re-projection when anything changes, and signed drift webhooks when a stored plan's numbers move, with a decision history per household.

A published price and a keyed sandbox

Monthly plans priced by active households are on the pricing page, and a free sandbox key arrives by email.

Client surfaces under your brand

Household embeds and a white-label reference build ship on your domains, so the planning view reaches clients as part of your product.

Questions

Common questions

What does BridgeFT cost?
Not stated publicly. Its site routes prospects to schedule a demo, as of the date in the sources below.
Can I use BridgeFT and Worthune together?
In principle, yes: aggregated custodial data can be mapped into Worthune households through bulk import, which validates every row with a dry run before writing. We do not offer a prebuilt integration, so the mapping is your team's to build.
Does Worthune aggregate accounts?
No. Worthune is not an account aggregator, custodian, or portfolio accounting system. It plans on household data you bring.
Do both offer a sandbox?
BridgeFT lists a development sandbox for its API. Worthune issues a free thirty-day sandbox key by email that opens stored households, the planning engine, and the full model catalog.

Sources

Every claim above, and where it came from

Product names and trademarks belong to their owners and are used here only to identify the products compared. Nothing on this page implies endorsement or affiliation. Found something out of date? Tell us at support@worthune.com and we will re-check it.

All comparisons · How our models earn a release