Avantos

Strip the agents out and a unified client context layer remains, because the knowledge graph linking clients, products and service teams is not itself a model. Prefilling, validating and coordinating work is what the agents add, but the context is the asset.

Humans stay in control by stated design, with agents preparing onboarding, coordinating handoffs and monitoring progress. Agents are also said to execute work across systems, and no approval gate, escalation path or sampling regime separates moving data from committing an action in a custodial system.

Downstream agent actions all inherit the relationships the graph asserts, so a wrongly linked product or a stale service expectation spreads into onboarding and monitoring at once. Real time data validation is claimed, but how the graph is validated, how source conflicts are resolved and how drift is detected are unpublished.

Four named customers, Vanguard and SEI among them, are also strategic investors from the $35 million Series A that Bessemer Venture Partners led in February 2026. Quotes from that group read as investment statements, and no volume, outcome or deployment figure is attached to any named firm.

A continuously updated system of context implies the graph enriches over time, and Avantos publishes no statement on whether that enrichment stays inside one firm's tenant or feeds any model. Named customers and backers compete in wealth and retirement, which gives the cross client question real weight.

Concentration is the privacy issue: one graph would hold portfolio holdings, beneficiary designations and retirement balances for the same client, which no underlying system held together. The homepage and onboarding page describe no retention schedule, deletion commitment or data protection agreement for the service.

SOC 2 certification is claimed, though a SOC 2 examination is an attestation report, and neither report type nor period is stated. A Secureframe trust center is linked, and whether it releases documents without a request is not shown.

Three regimes meet in this scope, adviser supervision, state insurance suitability rules and federal pension fiduciary duty, and Avantos names none of them. It gives no account of how agent servicing actions reach a firm's supervised books and records, though as a technology supplier it needs no license.

Health scoring of clients decides which relationships get proactive attention and which products surface, and a client scored low never learns a score exists. Where suitability duties apply, a machine surfaced opportunity can anchor an adviser toward a product, yet Avantos publishes no testing or analysis of how scores fall across client segments.

Auditability is stressed and sensitive steps stay under workflow control in onboarding, so a firm can trace what an agent did. Avantos publishes no warranty, indemnity or correction path, and clients get no described route to challenge an agent's output.

Model providers, hosting and data sources are all unnamed for a platform built to concentrate client data. An examiner's fourth party question, whether graph context passes to an external model when an agent reasons over it, is left unanswered.

Integration is both the thesis and the gap: Avantos says it connects to a firm's CRMs, custodians and core systems without replacing them, yet it names no connected system and publishes no developer documentation.

Client context copied from systems of record into a persistent graph raises the residency question early in a wealth firm's review. Hosting provider, region and any private deployment option are unstated for this cloud product.

Every path into the product is a contact request, with pricing, packaging and any trial unpublished. Whether charges run per seat, per client relationship or as a platform fee is open for a product sold across several business lines.

Asset managers, insurers and advisory firms are the buyers, across four business lines from wealth to banking. Covering protection and retirement in one platform is ambitious, since inside one firm those sit in different systems and regulatory regimes, and no deployment is shown for any single line.