For Family Offices

Multi-entity 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.

Request an introductionSpeak with the founder

The family-office reality

Four operational questions generic wealth platforms do not answer.

0

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.

Generational

access requirements that one-role-per-user tools cannot model

Your spouse sees the trust-income dashboard. Your son's access grows as his role on the succession plan matures. Your external accountant reads every transaction without the ability to modify any. Your attorney sees the documentation layer. Traditional platforms give one access tier per user, all-or-nothing. BasePro ships per-user permission overrides that model progressive access the way families actually practice it.

Cross-border

reality for most modern family offices

Your family holds assets in Mexico, the US, and Europe. Your next external review (maybe an independent trustee, maybe the next generation of principals) asks where the data lives and who holds the keys. Data residency selection at org creation, KMS envelope encryption with org-specific keys, and multi-jurisdictional banking identifiers in one schema turn that conversation into a documented policy answer.

25+

years of operating evidence most family offices need to preserve

Your audit trail must survive the transition from one generation to the next, from one external accountant to another, from one legal counsel to the next. An Excel archive on a shared drive does not survive fifteen years of staff rotation. BasePro's SHA-256 hash-chain audit log with ten-year retention, aligned with NOM-151 expectations, is the continuity substrate. The chain you leave your successor is cryptographic, not narrative.

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 builderPrincipal controls · one truth
As of 22 Apr 2026

Source ledgerPrincipal view
PositionValueYTD
Commercial · CDMX SouthMXN 420M+8.4%
Visible to
FIBRA · Class BMXN 180M+11.2%
Visible to
Co-investment · SPV-AUSD 28M+6.9%
Visible to
Direct RE · Tulum coastMXN 95M+14.1%
Visible to
RE Fund · LATAM ResidentialMXN 220M+9.7%
Visible to
Recipient statements
SNext-gen successor
  • Commercial · CDMX SouthMXN 420M
  • FIBRA · Class BMXN 180M
  • Co-investment · SPV-AUSD 28M
  • Direct RE · Tulum coastMXN 95M

4 of 5 positions

AExternal accountant
  • Commercial · CDMX SouthMXN 420M
  • FIBRA · Class BMXN 180M
  • Co-investment · SPV-AUSD 28M
  • Direct RE · Tulum coastMXN 95M
  • RE Fund · LATAM ResidentialMXN 220M

5 of 5 positions

CTrust counsel
  • Commercial · CDMX SouthMXN 420M
  • Co-investment · SPV-AUSD 28M
  • RE Fund · LATAM ResidentialMXN 220M

3 of 5 positions

Click a chip to toggle visibility · each recipient renders from the same ledger

Privacy-first architecture, verifiable

Dual-dimension row-level security enforces organization_id and property_id at the PostgreSQL layer. Cross-org queries return 404 rather than 403, so portfolio enumeration is impossible, not merely forbidden. Your DBA, your external security consultant, and your privacy counsel can verify the posture directly at the database layer. No middleware to trust, no code-review promise to accept on faith.

Data residency and KMS envelope encryption

The org creation dialog lets you pick the Supabase region that holds your data (EU, US, APAC). Sensitive PII sits behind KMS envelope encryption with org-specific 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.

SHA-256 hash-chain audit log, built for generational continuity

Every write to the portfolio anchors to a cryptographic chain. Monthly partitions, nightly verification cron, 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.

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

Clerk Professional+ surfaces production-verified SAML, OIDC, and SCIM inbound provisioning. Your office manager, external accountants, and attorneys authenticate through your existing IdP. SCIM events emit to the security audit log. When an advisor rotates out, deprovisioning is an automated event, not a ticket queued behind other administrative work.

Enterprise 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.

See pricing

How BasePro reads against your current options.

vs Enterprise ERP (category)vs Oracle NetSuitevs Spreadsheets (the honest comparison)

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 at the PostgreSQL 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 hash-chain audit log, the ten-year retention, the data-residency selection, the KMS envelope encryption with per-org 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.

Request an introductionEmail the founder

Not ready? Explore by role:

FIBRAsInvestment FundsDevelopers & RE Firms