Early Access. Invitation Only.
One system for everything your family office runs.
Real estate, operating businesses, investments, and family finances in a single structured database. The four domains live in the same schema and link to each other. Built by someone who runs a family office.
Request Access
We are onboarding a small number of family offices.
The Platform
Four domains in one database.
You run real estate, businesses, investments, and personal finances on separate tools that no one designed to work together. MAROM holds all four in one structured record, with the links between them built in.
Real Estate
Holdings, ownership entities, leases, property managers, maintenance, and income, structured and linked. You stop pulling reports out of property management software to reconcile them by hand.
- —Holdings & ownership structures
- —Lease tracking and expirations
- —Property manager access control
- —Maintenance and capital work orders
- —Income and expense by property
Operating Businesses
If the family runs one operating company or several, MAROM holds the entity structure, financials, and key metrics alongside the rest. The business sits in the same record as the properties and the portfolio.
- —Entity and ownership hierarchy
- —Operating financials
- —Key performance metrics
- —Staff and vendor relationships
- —Board and governance records
Investments
Portfolio positions, custodian accounts, and advisor relationships in one place, structured and connected to the rest of the family's wealth.
- —Portfolio positions and allocations
- —Custodian and account structures
- —Advisor read-only access
- —Performance and reporting
- —Alternative and private investments
Family Finances
The personal layer: household accounts, trusts, insurance, estate documents, and the financial picture of each family member. Collaborators cannot reach any of it.
- —Trust structures and beneficiaries
- —Estate and succession documents
- —Household accounts and budgets
- —Insurance policies
- —Per-member financial summaries
Security Architecture
The database enforces every permission.
Row-level policies sit on every table in MAROM. The database checks who is asking on every query, so a missed check in one screen or one API route cannot expose data it should not. That holds regardless of how a request reaches the system.
01 / 04
Database-Layer Enforcement
Row-level security policies live on every table. The database decides what each session can read on every query.
Every table in MAROM carries row-level security policies. The database decides what a given session can read on every query, regardless of how the request reaches it. You cannot change that from the interface. It is part of the schema.
Who It Is For
Built for family offices and the outside people they work with.
MAROM is built for the operational complexity of a family office, where the household also includes trusts, entities, employees, and outside people who need limited access to parts of it.
Primary user
Family Office Principal
The family members who own and oversee the structure. You see real estate, businesses, investments, and family finances in one place, without waiting for a staff member to reconcile exports from five separate tools.
01 of 05
Provenance
Built by someone who runs a family office.
MAROM came out of a weekly problem: reconciling real estate, a business, investments, and family finances across tools that do not connect. The data model follows how family wealth is structured, including trusts, entities, ownership hierarchies, and the complexity of running an operating business alongside real estate and personal wealth.
It runs on production infrastructure today. All four domains and the schema are built. This is a working system in early access.
FAQ