Operating foundation
Tenant core, identity and access, and CRM party records.
- Platform core
- Identity and access
- CRM parties
Bring members, deals, funds, governance, and documents into a customer-specific system that can be delivered, isolated, and upgraded with control.
Composable capabilities
Tenant core, identity and access, and CRM party records.
Membership, deal workflow, and governance decisions.
Fund records, investment closings, and portfolio views.
Documents, signatures, payments, and insights.
Verifiable delivery
Resolve modules and versions from a customer profile.
Test the locked source, migrations, and image.
Create an isolated Compose stack and durable data boundary.
Back up first, canary, then complete only after verification.
01 · MANAGED HOSTING
Customer cases are assembled from version-pinned shared modules, not divergent forks.
02 · CUSTOMER HOSTED
Each customer uses its own Compose stack, database, files, secrets and backups.
03 · DEEP PARTNER
Fork the complete private reference system, develop in a partner-owned layer, and continue receiving reviewed upstream module fixes and features through controlled upgrade PRs.
Read the partner manualThis POC demonstrates real module operations, isolation, and delivery controls. It does not imply asset custody, fund accounting, legally effective signing, or a completed production-data migration.
CaaS
No. The same Compose delivery can run on customer Linux, a VPS, or a GCP host managed by us.
Each customer receives a separate Compose project, network, database, credentials, volumes, and backups.
During the POC, a customer image is rebuilt and the application container is replaced. The database and host are not rebuilt.
No. Demo installations use fictional demonstration data only; production onboarding requires a separately reviewed migration.