Financial planning & wealthtech infrastructure
White-label financial planning, without the white-label wait
White-label financial planning software puts planning tools in front of your clients under your own brand. Worthune's version is configuration, not a services project: set your brand name, a theme validated for accessibility at write time, and your firm's disclosure paragraphs; then embed real client households on your domains via short-lived signed tokens, or build the full experience on the React component kit. A live reference build exists to evaluate and fork, so the portal starts from working software.
What to look for — whoever you choose
Theming with a floor
A white-label theme that can ship unreadable contrast becomes your accessibility problem. Look for validation at configuration time, not a style guide PDF.
Disclosures that append
Your compliance language should add to the platform's own disclosures, never replace them — a white-label system that lets branding edit the math's assumptions text makes every review meaningless.
Scoped credentials for client data
If embeds show real client data, ask what a leaked credential exposes. The honest answer should be: one household's widgets, on your domains only, until a short expiry.
How Worthune answers it
Tenant configuration over an API
Brand, theme (WCAG-gated at write), append-only disclosures, and a domain allowlist — validated with per-field errors so stored configs always render.
→ read the white-label docsTenant-bound embeds
Short-lived signed tokens scope each embed to one household and your allowlisted domains, enforced as a frame-ancestors policy. Tokens can never call the API.
→ see the solutionA reference build to fork
The white-label evaluation surface is live: the component kit on a fictional household, with a theme switcher and a consumer-lite/advisor toggle.
→ open the reference buildWhere this fits: everything above is one platform — calculators & models, planning software, and unified household management, on the same verified engines and one API. How the numbers are made is public: the methodology.
Common questions
How fast can a white-label planning experience ship?
Embeds with your branding are configuration — hours, not sprints. A full client portal built from the reference implementation on the component kit is typically weeks: the engines, theming, and disclosure structure already exist.
Can we remove the Worthune attribution?
On the Growth plan, yes — attribution removal is part of white-label configuration. Below Growth, surfaces carry a small attribution.
Who controls the compliance language?
Both parties, by construction: the platform's own disclosures always render, and your firm's paragraphs are appended to them. The append-only design means branding can never strip the disclosures a reviewer signed off on.
What does a leaked embed token expose?
At most one household's widgets, rendered only on domains in your allowlist, until the token's short expiry. Tokens are display credentials — they cannot call the API or read anything beyond their one household's computed views.
Talk to us