Platform
Three principles compile to one architecture.
Sovereign
Where DwellFi runs is a contract term, not a vendor preference. The customer's security review and regulatory regime set the deployment surface before signing, and the OS runs inside the perimeter the customer's auditors already accept.
The institutional pattern is the same one DwellFi ships: software runs inside the perimeter the customer's auditors already accept. AI workloads run inside that same perimeter.
Deployment surfaces
Agent · Capital call
Run 4127 · In-tenant
Execution trace
Deterministic
Audit
Agentic
No two funds share the same combination of side letters, asset mix, jurisdictional exposure, regulatory regime, waterfall mechanics, and valuation policy. This is why vertical SaaS falls short in fund operations, and why the work still runs on Excel and headcount.
DwellFi writes real-time custom software, per fund, against your stack. The agents compose the workflow. Capital calls reconcile against the LPA. NAV strikes against custodian feeds. Each workflow ties back to its source documents the same way, every period.
Generic AI guesses. DwellFi agents generate, verify, and ship.
DwellFi benchmarks frontier and open-source models on a continuous schedule, then routes each workload to whichever performs best on it. The fund isn’t locked into one lab’s roadmap.
For workflows that have to be exact, deterministic agents cross-check across multiple frontier models and route exceptions to a human for review.
Routed by continuous benchmark. No single-lab lock-in.
The agents above are the work. The OS below is what makes them deterministic.
OS
Agents are only as good as the layer they run on. The DwellFi OS is that layer: composable primitives that turn fund documents into deterministic answers, every one tied back to a source.
Primitives
5 objects · Infinite compositions
Architecture stack
Top-down · Customer in
Probabilistic vs deterministic
Generic AI is a model that produces text. Fund operations are reconciliation problems, not text problems. Four real workloads, four different ways probabilistic systems fall over.
Input
Side letter set · 47 LPs · ~120 pages
Generic AI
Probabilistic
Throughput
Output
Unable to process file. Try splitting into smaller documents.
Deterministic
Throughput
Output
47 LP side letter records. Every term cited to its page.
Input
36 monthly statements · 4 accounts · multi-currency
Generic AI
Probabilistic
Throughput
Output
Partial reconciliation. Confidence: low. 24 months not processed.
Deterministic
Throughput
Output
36-month reconciliation complete. 412 breaks, each with a reason.
Input
Sub docs, IDs, accreditation · ~50,000 pages
Generic AI
Probabilistic
Throughput
Output
File set exceeds API limits. No output.
Deterministic
Throughput
Output
250 LP profiles complete. AML and KYC files attached.
Input
Quarter close pack · cross-sheet formulas · 300MB
Generic AI
Probabilistic
Throughput
Output
Partial extraction. 25 tabs and all cross-sheet formulas dropped.
Deterministic
Throughput
Output
All 30 tabs in one normalized dataset. Every formula traced to its source cell.
Same input. Different system.
Workflows
The work that scales with AUA or AUM, not headcount. The work that has to reconcile, not approximate.
Notices drafted from LPA commitments, sent to LPs of record, reconciled against custodian receipts.
Positions, accruals, fees, and waterfall calculations rolled into a deterministic NAV pack.
Bank, custodian, broker, and ledger reconciliations against source feeds.
Calculated, drafted, approved, executed against the waterfall.
Quarterly LP letters, capital account statements, side-letter compliance.
Tax allocations, capital accounts, K-1 packages per LP.
Subscription document review, KYC, AML, accreditation, side-letter review.
Regulatory filings, drafted from current fund state.
Management fees, performance fees, carry, hurdle, catch-up, waterfall.
Trial balances, supporting schedules, audit confirmation packages.
Inbound migration of an existing fund admin's data into the OS.
Per-fund agents written against your stack.
SOC 2 Type II, with audit trails stamped on every action. Deployment runs inside the customer's environment. The full security overview covers the controls and the deployment architecture.
Sovereign by design, deterministic by construction, auditable on every action, deployed inside the customer's environment. Pick the conversation that fits where you are.
