Vestberry already describes AI extraction with source citations and human review controls, alongside portfolio and fund reporting. A fair comparison starts by acknowledging those capabilities. Source-linked extraction alone is not a defensible exclusive claim for Uranus.

The coexistence case is the work that spans the firm’s other tools. For example, a fictional partner may need to reconcile a validated Vestberry metric with a board document, preserve an IC condition, and track an internal evidence request to a reviewed resolution. Uranus holds that selected evidence and the owned work together. Whether this reduces effort relative to Vestberry’s own configured workflow remains a customer validation question.

Vestberry’s public material discusses APIs, MCP, warehouse feeds, and Excel workflows. That does not provide a universal public endpoint, authorization contract, or tenant export schema for us to implement safely. Obtain vendor-approved documentation and the firm’s entitlement before a live connector. The release therefore offers a guide and generic file mapping, with no native Vestberry sync. Keep ownership economics and administrator-grade reporting in their authoritative system, and preserve definitions and source documents when transferring selected context.

A first import you can review

  • Ask the tenant administrator for an approved structured export or Excel add-in extract.
  • Include metric definitions, currencies, period and investment identities, preserving cited documents separately.
  • For a live connector, request documented API/MCP setup and permitted field scope from Vestberry; do not infer endpoints.

What Uranus adds today

Review the mapping, units, currency, and reporting month before committing. New metrics remain candidates until a workspace owner reviews them. Preserve originals and source identifiers, keep the requested next evidence visible, and attach a reviewed resolution when the work is complete. Export canonical records and version history when you need to move the work again.

This is a proposed workflow based on public documentation, not a paid-account benchmark or a demonstrated performance improvement. Verify the actual entitlement, export schema, and effective permissions with the firm’s administrator. Native formats require customer fixtures before claiming automatic compatibility.