Private asset operations
Run every private asset from one command centre.
Meridian gives family offices and private asset teams one place to coordinate maintenance, tasks, approvals, crew, documents, vendors and schedules across yachts, aircraft, properties and vehicles.
Full product, no card required. An operator replies within one business day.
Maintenance · Approvals · Crew · Documents · Vendors · Schedules
Private portfolios create operational complexity.
A single asset can involve a captain or manager, a dozen vendors, insurers, class or airworthiness bodies, and a principal who needs to approve spend. Multiply that by a portfolio and the work spreads out.
Where the work ends up
Service history in one spreadsheet. Quotes in an inbox. A crew change agreed in a messaging app. Certificates in a shared folder, some of them expired. Dates in a calendar only one person keeps.
What it costs
Nobody can answer the simple questions quickly: what is overdue, who is waiting on whom, what has already been approved, and what happened last time this asset was serviced. The answers exist, but they have to be reassembled by hand.
Individual asset-management systems make this worse rather than better. A yacht management tool does not know about the aircraft, and neither knows what the principal has already approved.
One connected record
One operating record across every asset.
Every job in Meridian carries its context with it. Open a work order and the asset, the person responsible, the vendor, the documents, the approval and the full history are already attached.
Because the record is connected, the same job appears wherever it is relevant: on the asset's own file, in the vendor's job list, in the owner's approval queue and in the operations board. Updating it once updates it everywhere.
Core workflows
What teams actually do in Meridian.
Maintenance and servicing
Set service schedules by date or by usage (engine hours, kilometres, airframe hours) and Meridian raises the job when either threshold is reached first. Log what was done, what it cost, and which vendor did it, against the asset’s own history.
Tasks and approvals
Raise a task or work order, assign a lead, and track it through open, scheduled, waiting, blocked and done. Work that needs the principal’s sign-off goes to an owner approval and waits there, visibly, instead of stalling in someone’s inbox.
Schedules and obligations
Registrations, surveys, certificates, insurance renewals and recurring bills all carry due dates. See them as a calendar, an agenda or a forward view, so a lapse is something you scheduled around rather than discovered.
Documents and records
Store certificates, policies, quotes, invoices and manuals against the asset or the job they belong to. Documents with an expiry date are tracked, so a certificate that is about to lapse becomes an action rather than a surprise.
Crew, staff and vendors
Keep crew and staff assignments, contracts and certification expiries per asset. Invite vendors to the specific jobs they are doing: they receive the work order, submit quotes, post updates and close out, without access to anything else.
Owner reporting
The operations board is the current position at any moment: what is open, blocked, waiting and scheduled, with spend tracked per asset in the currency each cost was incurred in. Each asset can export a handover pack covering its record. Scheduled written owner briefs are in development.
Asset coverage
Four asset types, one portfolio.
Each asset type carries the operational detail specific to it, while staying part of one portfolio the whole team can see.
Yachts
Crew rotations, passages and movements, class and survey dates, refit and yard periods.
Aircraft
Airworthiness and certification windows, crew currency, positioning flights and scheduled inspections.
Properties
Household staff, contractors, statutory certifications and seasonal readiness.
Vehicles
Collection servicing, registrations, storage, transport and pre-use readiness.
The shared parts stay shared. A vendor, a document or an approval works the same way whichever asset it belongs to, so a team that learns one asset type already knows the others. See what each asset type tracks.
Who it’s for
Built for the people who keep private assets moving.
Meridian is used by the team around the asset, not only by the office. Everyone works from the same record, with access scoped to their role.
Family office staff
Oversight across every asset the principal owns, in one place: what is due, what is blocked, what needs approval and what it is costing.
Personal assistants
The schedule and the obligations in one view, so a renewal or a movement is not something to be chased down across four other people.
Estate and property managers
Contractors, staff, certifications and recurring work per property, with a record of what was done and what it cost.
Yacht captains and chief officers
Run the vessel’s own programme (crew, servicing, surveys, yard periods) and report upward without rebuilding the picture each time.
Aviation and fleet managers
Certification windows, crew currency and scheduled inspections tracked against usage, alongside the rest of the portfolio.
Vendors and service providers
Receive the work orders you are assigned, quote them, post updates and close them out. You see your jobs, and nothing else.
Access is granted by role. Staff work across the portfolio; vendors are invited to specific jobs and see only those, never the wider record. Every change is attributed to the person who made it.
Security and discretion
Private by default, and scoped by role.
Portfolio information is sensitive well beyond its financial value. These are the controls in the product today.
Role-based access
Every person in a portfolio holds a role: owner, staff, vendor or administrator. That role determines what they can open and change.
Vendors see only their own jobs
A vendor invited to a work order gets that work order. They cannot see the rest of the asset’s record, the other vendors, the portfolio, or what anything else costs.
Enforced in the database
Access rules are row-level policies in the database itself, not checks in the interface. A request for data outside your portfolio returns nothing, whatever it was sent from.
Multi-factor authentication
Accounts can require a second factor at sign-in. Until that challenge is passed, the session cannot read portfolio data.
Activity history
Records carry their own history: what changed, who changed it and when. Useful for handovers, and for answering questions months later.
Access-controlled document storage
Uploaded documents are not public files with hard-to-guess addresses. Each one is served through a short-lived link issued only to someone entitled to open it.
Bring your portfolio operations into one view.
Know what changed, what is due, who owns it and what happens next across every asset in the portfolio.
Start the trial and add your first asset in a few minutes, or tell us the assets and the team and a Meridian operator replies within one business day to arrange a walkthrough built around your own portfolio, not a generic demo.
Founding accounts. The first 20 accounts pay half price, for life. Founding pricing is applied automatically at checkout, closes by count rather than by date, and does not expire once yours.