Your stack
Sluice reads your systems and writes back to them
We are not asking a firm to move its book. Sluice ingests from the systems of record, does the work, and pushes the result back where it came from.
Connected
WealthboxCRM
EnvestnetData
NFSCustodian
Not a system of record
Your data stays yours, in your systems
Becoming a firm's books-and-records is a different business with a different regulatory posture, and we deliberately are not in it. Sluice is a processor: it holds what it needs for as long as the work takes, writes the outcome back to the CRM and the custodian, and purges on a schedule the firm sets.
- Connections are configured per firm, per environment, with credentials held by reference
- Write-back ownership is explicit per field — the CRM can stay authoritative where it should
- Retention is a policy, enforced by scheduled purges rather than by good intentions
Connected
WealthboxCRM
Dynamics 365CRM
EnvestnetData
NFSCustodian
Where it runs
Our tenancy or yours
Most firms start on our multi-tenant deployment. Firms with their own cloud and their own security review can take the same container into their environment, with their own keys and their own network boundary. The application is the same either way.
Reads from and writes back to
- NFS · Fidelity
- Altruist
- Envestnet
- Wealthbox
- Dynamics 365
- DocuSign
- Salesforce
- Redtail
See it against your own book
Bring a household that has given you trouble. Thirty minutes, no deck.
Request a demo