The library, the docs, the answers.

For a Boutique tenant with 1–6 funds and standard integrations: 2–3 weeks self-service, plus 4 hours of guided onboarding to validate fee rules and approval chains. For a Growth tenant: 4–8 weeks, with our team paired to your operations and finance leads. For an Enterprise group with dedicated cluster, multiple legal entities, custom adapters and migration from an incumbent platform: 8–12 weeks is the realistic range. We do not staff long, billable implementations — if it would take more than a quarter, we redesign the scope.

No. Investa is designed to live alongside an external fund admin if that's how you run today. The platform pulls daily holdings and NAV files from the admin, validates them row-by-row, and runs your investor-facing operations — subscriptions, redemptions, statements, KYC — in front. Many customers start that way, then bring more of fund accounting in-house over time as they're ready.

Investa supports Shariah-compliant fund structures: profit-and-loss sharing terms, screening rules tied to the fund's mandate, purification accounting, Hijri calendars first-class. We do not certify funds — that's the work of your Shariah board — but we provide the platform on which their decisions are recorded, evidenced and reproducible.

You choose at provisioning. Multi-tenant SaaS runs in EU (Frankfurt) by default, KSA (Riyadh) for tenants requesting it, and UAE (Dubai) on the Enterprise plan. Single-tenant dedicated clusters are available in any of the three. Data does not leave the chosen region — even for backups, even for our staff diagnostics — without an explicit, signed consent path. That path is itself audited.

Yes. Investa ships with a Regulator / Auditor role: read-only, time-bound, scoped to a specific period and set of funds. Your tenant admin issues the access; the auditor receives a credential; the audit trail records every screen they viewed and every export they ran. The role is included on Growth and Enterprise plans at no extra cost.

You can export every entity at any time — JSON, CSV, signed PDF audit packs — through the platform itself. On termination we deliver a final export, hand over signed audit-pack PDFs for the open period, and destroy the tenant within 90 days. We provide a written destruction certificate signed by our security officer.

Almost never — and that's deliberate. The platform's workflow engine is no-code by design; if a workflow you need doesn't fit, that's a signal we should improve the engine, not a signal you should pay for a fork. We build new integrations and new report templates regularly. We very rarely take on custom feature work, and when we do it ships to all customers.

Approval chains are configured per workflow, per fund, per role, with conditional routing on amount, asset class, investor type or any other field on the entity. Four-eyes is a structural property — Investa rejects any workflow definition where a single user can approve a step they themselves initiated. The audit log captures every approver's name, timestamp and the data they approved against.

Yes — we provide a migration toolchain that ingests investor records, holdings history, transactions, KYC files and supporting documents from your incumbent system. The toolchain runs in your sandbox first; you reconcile against your spreadsheet/admin reports; only after sign-off does it run against production. Most migrations cycle the toolchain twice before go-live.

You do, in their entirety. Configurations you create — fee rules, report templates, KYC packs, workflow definitions — are your IP and travel with you on export. The platform itself is ours. We never train models or analytics products on tenant data; we never share data across tenants; we don't have aggregated "customer benchmarks" we sell back.