Who owns WealthOS?
WealthOS is owned by JPMorgan Chase (the United States, NYSE: JPM).[1][2][3][4]
Evidence: JPMorgan Chase & Co. Annual Report on Form 10-K filed 2026-02-13, SEC EDGAR, 13 February 2026. Verified from filings; last checked .
Key facts
- Current owner
- JPMorgan Chase & Co. verified
- Owner HQ
- 🇺🇸 United States, New York
- Origin
- 🇬🇧 United Kingdom, London
- Category
- Technology › Software › Enterprise software
- Parent ticker
- NYSE: JPM
- Last verified
- · 4 sources
About WealthOS
WealthOS is a London-based, cloud-native software platform that runs the middle and back office of digital wealth management services. It now calls itself a J.P. Morgan company: JPMorganChase bought it to rebuild the personal pension of its UK investing business, J.P. Morgan Personal Investing.
Ownership timeline of WealthOS
- Current owner JPMorgan Chase [1][2][3][4] verified
Where WealthOS sits in JPMorgan Chase
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
- 55ip
- Chase
- Chase Europe
- Chase Media Solutions
- Chase Private Client
- Chase Sapphire
- Chase Travel
- Chase UK
- InstaMed
- J.P. Morgan
- J.P. Morgan Asset Management
- J.P. Morgan Natural Capital
- J.P. Morgan Payments
- J.P. Morgan Personal Investing
- J.P. Morgan Private Bank
- J.P. Morgan Private Client
- J.P. Morgan Wealth Management
- Kinexys
- The Infatuation
- WealthOS
Open the full JPMorgan Chase ownership tree →
See the full JPMorgan Chase brand portfolio (20) →
Other brands owned by JPMorgan Chase
JPMorgan Chase controls 20 brands on Brandtree, 2 of them in technology.
Also in technology
- Chase Media Solutions (2024)
Other brands in enterprise software, and who owns them
The 38 brands in enterprise software on Brandtree belong to 23 owners. The largest is Globant, with 6; JPMorgan Chase has 2.
About the owner: JPMorgan Chase
JPMorgan Chase is a publicly listed company headquartered in New York, United States. Brandtree records 20 brands under its control, and it is listed as NYSE: JPM.
JPMorgan Chase & Co. is a financial holding company that serves consumers, small businesses, corporate, institutional and government clients under the J.P. Morgan and Chase brands. Its principal bank subsidiary is JPMorgan Chase Bank, National Association, with U.S. branches in 48 states and Washington, D.C., per its 2025 Form 10-K.
JPMorgan Chase: full profile, brands and acquisition history →
🇬🇧 WealthOS and other British brands
Brandtree records a controlling owner for 615 brands that began in the United Kingdom. 342 of them (56%) are now controlled by a company headquartered in another country, WealthOS among them.
- Featurespace — Visa 🇺🇸
- Kantox — BNP Paribas 🇫🇷
- A.1. — Kraft Heinz 🇺🇸
- ASOS Design — ASOS 🇬🇧
- AVA — Pets at Home 🇬🇧
- AXA Health — AXA 🇫🇷
Frequently asked questions
Who is the parent company of WealthOS?
The parent company of WealthOS is JPMorgan Chase, a publicly listed company headquartered in the United States.
Is WealthOS British or American?
WealthOS originated in the United Kingdom, but it is owned today by JPMorgan Chase, which is headquartered in the United States. So WealthOS is a British-origin brand under American ownership.
Is WealthOS still owned by JPMorgan Chase?
Yes. As of 18 November 2026, WealthOS is still owned by JPMorgan Chase. The ownership record was last checked against primary sources on that date.
Sources (4) & corrections
Last verified . Every ownership fact above is backed by one of these primary documents. Numbers in brackets in the text refer to this list.
- [1] JPMorgan Chase & Co. Annual Report on Form 10-K filed 2026-02-13 — SEC EDGAR, SEC Form 10-K, published 13 February 2026; retrieved 9 October 2026.
- [2] WealthOS: The Cloud-Native Wealth Management SaaS — WealthOS, Official document; retrieved 18 November 2026.
- [3] WealthOS Privacy Policy — WealthOS, Official document; retrieved 18 November 2026.
- [4] Consumer & Community Banking: Marianne Lake, Letter to Shareholders, Annual Report 2025 — JPMorgan Chase & Co., Annual report, published 6 April 2026; retrieved 18 November 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.