For Family Offices
Cross-LLC real estate operations, privately held.
Your structure is layered: a fideicomiso holds title, a SAPI runs operations, a trust holds equity. Each generation of your family needs a different level of access. BasePro models all of that natively, with a privacy architecture your next external auditor can verify.
The family-office reality
Four operational questions generic wealth platforms do not answer.
Operational frictions
Entity registry
6 entities · 4 layersZero off-the-shelf ERPs model your entity structure out of the box. A fideicomiso holds title. A SAPI handles operations. A trust holds equity. An external holding company in another jurisdiction consolidates the economic interest. Most real-estate platforms model one entity at a time and expect you to reconcile the layers in a private spreadsheet. BasePro's portfolio layer speaks in the language your lawyers already use: one-country-per-org for regulatory clarity, per-entity config, per-property overrides where operations differ.
Source: Wealth-tech platform feature audit, 2025–2026
One canonical cockpit, every specialist on the same canvas.
Eight trusts × twenty-four LLCs × nine direct properties roll up into a single director's cockpit. Occupancy, NOI delta, AUM by entity and generational voting class, estate-plan currency, trust-accounting status, CTA / FinCEN posture — all on one canvas. The same canvas your investment-committee chair opens at quarterly review, your estate lawyer reads before the annual family assembly, and your tax counsel reconciles at year-end close. No version-of-truth ambiguity, no consolidation tooling. The cockpit IS the canonical view; specialists project per-domain depth where their expertise lives.
Family Office · 8 trusts · 24 LLCs
Next IC · 18dDirect properties
9
Total AUM
$248M
+3.8% QoQ
Voting classes
G1·G2·G3
IC due
18d
Estate plan: current · review Q4 · Trust accountings: 12 of 12 filed · CTA / FinCEN: on time
Entity structures modeled the way your counsel speaks
A fideicomiso, a SAPI, a trust, and a cross-border holding company each occupy their place in the portfolio layer. One-country-per-org for regulatory clarity, per-entity configuration for operational differences, per-property overrides where one asset needs a different approach. Your chart of accounts does not flatten your legal structure into a single generic ledger. It preserves the structure you built with intention.
Progressive access, per person, per action
Role-level permissions set the baseline. Per-user overrides layer on top, atomic per CRUD action. A family principal has full access to the operational ledger. A next-generation successor gains approval authority on specific entities as their mandate matures. An external accountant reads every transaction with no ability to modify any. An attorney sees the documentation folder without seeing the bank detail. Each permission boundary is explicit, audited, and reversible.
Statement builder
5 positions · 3 recipientsSuccessor: 4/5 · External accountant: 5/5 · Trust counsel: 3/5
Privacy-first architecture, verifiable
Tenant isolation is enforced below the application layer — at every table that holds your data, in two dimensions: organization-scope and property-scope. Cross-tenant boundaries cannot be probed. Your auditor, your external security consultant, and your privacy counsel can verify the posture against documentation we provide. The isolation is structural, not configurable — part of the data architecture, not a setting your team toggles.
Data residency and envelope encryption
Choose the region that holds your data at signup — EU, US, or APAC. Sensitive personal data sits behind envelope encryption with per-organisation keys. When your independent trustee or external privacy advisor asks about your encryption approach, the answer is documented architecture, not a best-effort claim. Cross-border families can align residency to the jurisdiction your successor-trustee expects.
Multi-region foundations
per-org residencyTamper-evident audit log, built for generational continuity
Every write to the portfolio anchors to a tamper-evident chain. Ten-year retention available; sensitive fields redact cleanly for external review without breaking the chain. The point is not that an auditor can verify the past year's activity. The point is that your successor can verify the past fifteen years of activity, after three external accountants and two legal counsels have rotated through.
Audit chain — multi-generational
SHA-256 sealedG1 principal opens the portfolio. First entity registered, ownership recorded, audit chain initialized.
External accountant transitions out. Successor onboards with read-only ledger access; chain continuity preserved across hand-off.
G2 principal gains approval authority on operations. Permissions evolve atomically; every prior decision remains verifiable.
G3 added to portfolio audit. Cryptographic chain connects fifteen years of decisions to the next generation.
Internal Data-Protection Officer runs scheduled chain verification. Every prior write reproduces; archive integrity confirmed.
Cross-border banking in one schema
CLABE for Mexican operations, ABA for US rails, SWIFT and IBAN for international movement, all in one normalized table tagged to currency and country. Bank-feed reconciliation runs on the same substrate. Your Mexican rental income, your US-denominated distributions, and your European holding-company cash positions reconcile against the same ledger. Multi-currency P&L roll-ups land in the principals' report without an FX spreadsheet in the loop.
Enterprise IdP surfaces for staff and advisors
Production-verified SAML, OIDC, and SCIM inbound provisioning. Your office manager, external accountants, and attorneys authenticate through your existing IdP — Okta, Azure AD, Google Workspace. Provisioning events land in the security audit log. When an advisor rotates out, deprovisioning is an automated event, not a ticket queued behind other administrative work.
SCIM lifecycle — manager / accountant / counsel
IdP-drivenEnterprise tier, priced for family-office operations.
Custom pricing anchored to entity count, advisor seats, and compliance surface. No per-seat gotchas that fight the IdP rollout. No minimum seat-count lockout that penalises a lean family office.
How BasePro reads against your current options.
Architecture, not promises
Privacy and continuity are structural, not aspirational.
Family offices choose software cautiously, and rightly so. The platform that holds your operational evidence today will still hold it when a successor reviews the quarter your grandchildren inherit. BasePro was designed for that horizon from the first line of code.
The BasePro team does not access customer data. Support workflows run through explicit, audited access-elevation events that the organization approves in-product, and access closes the moment the ticket does. The posture is verifiable below the application layer, not in a policy PDF.
Most platforms in the family-office market treat a fideicomiso, a SAPI, and a cross-border trust as three unrelated customers. BasePro's portfolio layer models that structure the way your counsel already speaks about it. One portfolio. Many entities. Clean separation. Per-user progressive access that grows with the next generation.
Role-level permissions set the baseline. Per-user overrides layer on top, atomic per CRUD action. Every permission boundary is explicit, audited, and reversible — and every grant is visible to anyone with the right to audit it. Transparent roles are the product, not a configuration afterthought.
The tamper-evident audit log, the ten-year retention, the data-residency selection, the envelope encryption with per-organisation keys — those are not enterprise checkboxes. They are the continuity substrate a successor inherits when the current generation steps back.
Introduction through a mutual contact preferred.
We open the conversation through someone you already know, or directly with the founder. No cold outreach form on this page, by design.
Not ready? Explore by role: