Deployment
One family per instance, operated where your governance requires.
Capitalvue is the same product in every deployment model. Each family runs in its own dedicated instance; the models differ in where that instance runs and who operates it.
One family per instance
One family. One Capitalvue instance. One data boundary.
Every Capitalvue instance serves exactly one family, with its own application, database, family data directory and secrets. Several instances can run side by side on the same infrastructure without sharing data.
Multi-family offices
A multi-family office runs one instance per family. Its team works inside each family's environment, and no family's data is combined with another's.
Deployment
Three operating models
Capitalvue Managed
- Dedicated family environment
- Operated by Capitalvue
Best for
- Business families
- Smaller single-family offices
- Multi-family offices without dedicated IT
Capitalvue Private
- Runs in the client's own environment: private cloud or on-premise
- Capitalvue can operate the application
Best for
- Privacy-sensitive families
- On-premise environments
- Private cloud
Customer Managed
- Runs in client-managed infrastructure
- Operated by the client's IT
Best for
- Larger single-family offices
- Multi-family offices
- Professional IT teams
Every model runs the same Capitalvue product.
Who is responsible for what
| Responsibility | Capitalvue Managed | Capitalvue Private | Customer Managed |
|---|---|---|---|
| Infrastructure | Capitalvue | Client | Client |
| Operating the application | Capitalvue | Capitalvue or client, as agreed | Client IT |
| Installing releases | Capitalvue | Capitalvue or client, as agreed | Client IT, on its own schedule |
| Backups | Capitalvue | As agreed | Client IT |
| Family data location | Dedicated hosted environment | Client environment | Client environment |
The typical split. Responsibilities, service levels and data location are agreed for each engagement.
Hosting and data location
In Capitalvue Managed, the family's instance runs in a dedicated hosted environment operated by Capitalvue. In Capitalvue Private and Customer Managed, it runs in the client's environment (a private cloud, a data centre or on-premise), and the family data stays there.
Updates
Capitalvue ships versioned, immutable releases. Installing a release updates the application and leaves the family data directory in place. In client-controlled deployments, the client decides when a release is installed.
Your data remains your data.
Capitalvue separates the software from the family data environment. Source evidence, mappings and configuration are part of the family's dedicated deployment; new software releases are installed alongside and leave the family data in place.
The family's analytical state can be rebuilt from its source evidence and configuration alone, with the same published result.
Designed for portability, with a clear separation between software and family data.
How this differs from a shared platform
| Aspect | Typical shared SaaS platform | Capitalvue |
|---|---|---|
| Family data boundary | Usually one platform for many clients | A dedicated instance per family |
| Hosting | Typically the provider's environment | Capitalvue-managed, private cloud, on-premise or client-managed |
| Separation between families | Often logical, within shared systems | Separate deployments: own database, data directory and secrets |
| Financial logic | Varies by platform | Explicit, deterministic calculation layer |
| Source traceability | Varies | Designed into Core |
| Reporting | May be a separate workflow | Generated from the same controlled family data |
Shared platforms differ. The left column describes common patterns, not any particular provider.
For IT and security
A deployment model your IT team can understand.
- Standard container deployment
- Client-controlled infrastructure as an option
- Clear application and data boundary
- Versioned, immutable releases
- Defined backup scope: one database and one data directory per instance