Private capital infrastructure, assembled for how you operate.

Bring members, deals, funds, governance, and documents into a customer-specific system that can be delivered, isolated, and upgraded with control.

One disciplined delivery model
Dedicated customer stacksVersion-pinned modulesIsolated data and credentialsControlled upgrades and rollback

A software product, not one cloud project

Software for operations. A delivery system for every customer.

CaaS Factory assembles shared modules into a customer release. Deployment Manager verifies, installs, backs up, upgrades, and rolls it back. Every customer instance keeps its own database, files, and credentials.

  • One source, assembled by customer profile
  • Version- and digest-pinned build artifacts
  • Install on customer Linux or managed hosting

Composable capabilities

From access control to investment records, in one operating context.

01

Operating foundation

Tenant core, identity and access, and CRM party records.

  • Platform core
  • Identity and access
  • CRM parties
02

Investment operations

Membership, deal workflow, and governance decisions.

  • Membership
  • Deal pipeline
  • Governance
03

Fund and investor records

Fund records, investment closings, and portfolio views.

  • Fund records and fundraising
  • Investment closings
  • Portfolio
04

Evidence and control

Documents, signatures, payments, and insights.

  • Documents and signatures
  • Canonical payments
  • Insights

Verifiable delivery

Build → Verify → Install → Upgrade

1

Assemble

Resolve modules and versions from a customer profile.

2

Verify

Test the locked source, migrations, and image.

3

Install

Create an isolated Compose stack and durable data boundary.

4

Upgrade or roll back

Back up first, canary, then complete only after verification.

The same product, delivered to different hosting destinations.

01 · MANAGED HOSTING

Shared module source

Customer cases are assembled from version-pinned shared modules, not divergent forks.

02 · CUSTOMER HOSTED

Dedicated customer installation

Each customer uses its own Compose stack, database, files, secrets and backups.

03 · DEEP PARTNER

Deep-partner source distribution

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 manual

A clear account of what exists today.

This 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

Frequently asked questions

Does CaaS require GCP?

No. The same Compose delivery can run on customer Linux, a VPS, or a GCP host managed by us.

How are customers isolated?

Each customer receives a separate Compose project, network, database, credentials, volumes, and backups.

How is one module upgraded?

During the POC, a customer image is rebuilt and the application container is replaced. The database and host are not rebuilt.

Can a demo contain production data?

No. Demo installations use fictional demonstration data only; production onboarding requires a separately reviewed migration.