01
SOURCES
Comes in from your tools
Outlook, Lark and Google Drive sync into your knowledge base, with document-level permissions.
OUTLOOK · LARK · GOOGLE DRIVE
iMangroveThe AI workspace financial teams can sign off on
Built for
Family OfficesEAM / OCIOAsset ManagementVC / PEFinancial Platforms
Files are redacted locally and only reach models through the AWS zero-data-retention (ZDR) channel. Your team and AI work side by side on pages, sheets, slides and meetings — every figure traceable, every external action approved.
Example run
Connecting market data · Polygon · Tiingo
How data moves
Inside your walls — from source to sign-off.
Data comes in from the tools you already use, is redacted before any model sees it, gets worked on by your team and AI in one Space, and leaves only with an approval.
02
REDACT · ZDR
Redacted before AI sees it
Sensitive fields are redacted locally inside your tenant; model calls go only through the AWS zero-data-retention channel.
LOCAL REDACTION · AWS ZDR
03
SPACE
Worked on together
Pages, sheets, slides and meetings live in one Space — your team and AI edit the same file.
PAGE · SHEET · SLIDES · MEETING
04
SIGN-OFF
Leaves only with approval
Every figure links back to its source; anything sent outside waits for a human approval and is logged.
CITATIONS · APPROVAL · AUDIT
Extend itPluginsConnectorsSkills
Every new connection goes through the same permissions and approvals.
Core use case
From data room to IC memo — with sources and sign-off.
PER DEAL · IC
IC Memo / DD Checklist
Investment committee memo with redlines from prior memos, DD checklist auto-populated from data room.
DOCX · A4 PDF
QUARTERLY · CLIENT
Client Quarterly Report
Per-client performance, attribution, narrative summary. PII redaction on all client identifiers.
Branded PDF
WEEKLY · EQUITY
Equity Research Pack
Single-name deep dive: financials, valuation, catalysts, ESG flags, model debates. Slides + one-pager.
PPT · PDF · DOCX
DAILY · MACRO
Daily Macro Brief
Markets open, macro events, sector rotation, internal flags. PDF + Lark posting + email blast.
A4 · PDF · Lark
Templates ship with your branding. Mock data shown — real client data never leaves the tenant.
Governance is the product
Every line below is a default — not a sales promise.
- Every external action requires approval.
- Every sensitive read is permissioned.
- Every financial number is sourced.
- Every generated report leaves an audit trail.
ACLPII RedactionTenant IsolationApproval GateAudit Log
Where data and models live
Plain answers for your compliance team.
- Redaction
- Locally, inside your tenant, before any model call.
- Models
- Only through the AWS zero-data-retention (ZDR) channel — prompts and outputs are not retained or used for training.
- Storage
- Tenant-isolated, AES-256 field-level encryption; keys generated and rotated by AWS KMS (or your own KMS).
- Deployment
- Your own VPS / VPC, or AWS Singapore.
- Access
- Document-level permissions; every read is written to an append-only audit log.
Why iMangrove
A team forged inside finance — not retrofitted for it.
The team has architected, secured, and reconciled middle-and-back-office systems running multi-billion-dollar AUM in production. The same hands now design how AI plugs safely into your finance stack.
DOMAIN EXPERIENCE
$10B+ AUM SYSTEMS
- The team has built middle- and back-office systems serving $10B+ AUM · 10+ years in finance back-office.
- Cross-asset coverage: cash, bonds, FX, derivatives, alts, structured products.
SECURITY MODEL
AUDIT-READY
- AES-256 field-level encryption · AWS KMS key generation & rotation.
- Multi-tenant physical isolation · Local PII redaction · Models via AWS ZDR.
EXECUTION DISCIPLINE
PRODUCTION
- Daily reconciliation across providers · Approval gates before external action.
- Append-only audit log · Replayable runs · Done Gate before completion.
INTEGRATION CAPABILITY
BRIDGE
- Private bank feeds · Email extraction · Event-driven cash-flow engines.
- VPS / VPC / Singapore AWS hosting · Read-only by default, encrypted IDs.
What it looks like in practice
AES-256AWS KMSMulti-tenantPhysical isolationField-level encryptionPII redactionAppend-only auditDaily reconciliationCross-asset coverageSingapore AWS
The real moat in financial AI is trusted data, controlled execution, audit trail, and shipped deliverables. We've operated under that bar for years. iMangrove brings that DNA to your team's AI knowledge base and research workflows.
What changes during the pilot
From kickoff to first signed-off workflow.
Fixed scope. Fixed deliverables. No revenue promises — just range, acceptance criteria, and a signed artifact at the end.
| Stage | What you see | What we do |
|---|---|---|
| 01 · Discovery | One pilot workflow selected | Data source + permission assessment |
| 02 · Build | First Daily Macro Brief or research pack draft | Connector wiring + template fitting |
| 03 · Go-live | First signed-off delivery published | Approval flow + audit trail wired in |
| 04 · Scale | Expand to 3–5 workflows across the team | Operating metrics + governance policy |
Honest answers to the awkward questions
What compliance and CIOs ask in the first call.
Where does our sensitive data go?
Tenant-isolated runtime. Self-hosted on your VPS or VPC. Field-level encryption with AES-256, keys generated and rotated by AWS KMS (or your own KMS). PII redacted locally before any model call; models are reached only through the AWS zero-data-retention (ZDR) channel. Audit log on every read.
Will our data be used to train models?
No. Sensitive fields are redacted locally inside your tenant first, and model calls go only through the AWS zero-data-retention (ZDR) channel — prompts and outputs are not retained and not used for training.
How do you prevent hallucinated numbers?
Every figure is bound to a DataSlot — source, timestamp, confidence. Done Gate halts a workflow before completion. Multi-model cross-check surfaces conflicts. Provider chain with stale-flag fallback. Figures without a source are flagged for review.
Can we self-host or run on our own VPS?
Yes. Docker Compose deployment on your VPS, no Vercel dependency. Local Postgres, local object storage (or S3 if you prefer). Cron is OS-level crontab. KMS-managed keys optional.
We already have Bloomberg / FactSet / ChatGPT Enterprise — why iMangrove?
iMangrove is the workflow runtime that sits on top of them, not a replacement. We connect market data, internal knowledge, models, approvals, and delivery into one auditable run — none of those tools does that end-to-end.
What does a pilot actually include?
One workflow (for example an IC memo or DD pack from your data room) with fixed scope, signed-off deliverable, full audit trail, and a clear handoff path to your team. No revenue promises — just range and acceptance criteria.