Customer profile
Pasargad Wealth (illustrative) is a Tehran-based wealth firm serving high-net-worth individuals and institutional accounts on the Iranian Bourse and Farabourse. Their compliance team answers to the Securities and Exchange Organization (SEO) and works closely with the Central Bank of Iran (CBI) on AML matters. The firm cannot use public-cloud SaaS for regulatory and political reasons; everything must run inside their own infrastructure.
The challenge
Pasargad's existing platform was three vendors stitched together with custom Python scripts. The Persian language and Jalali calendar support was retrofitted, and certain edge cases — quarter-end Jalali calendar formatting, mixed-direction text in client correspondence, Iranian rial number formatting at high magnitudes — broke regularly. The firm wanted to consolidate to a single platform that treated Persian and Jalali as first-class concerns, but every viable platform was foreign-built and required public-cloud SaaS.
Modir's sovereign deployment model resolved both. The platform runs entirely inside the customer's K8s cluster; the only outbound dependency is what the customer pre-approves and routes through their own egress controls. Persian and Jalali are not retrofits — they are tested in the same CI matrix as English and Gregorian.
Why Modir
The decision came down to four properties. First, the codebase ships with signed container images and a published SBOM; the customer's security team verifies signatures at install time. Second, the localization architecture passes Persian + Jalali through the same CI gates as English + Gregorian. Third, the audit chain construction does not depend on any external service — Vault transit signing is optional, and the chain can be verified with a zero-dependency Python script. Fourth, OPA policies live in customer infrastructure; CBI-aligned AML rules can be authored and tested locally without round-tripping to a vendor.
Implementation timeline
- Weeks 1–2 — Discovery + signing review. 90-minute architecture workshop. Customer security team reviews release signing, SBOM publication, and supply chain controls.
- Weeks 3–6 — Provision. Customer K8s cluster prepared. Argo CD installed inside customer perimeter; releases pulled from a customer-mirrored OCI registry. Vault and Postgres seeded. CBI-aligned AML Rego pack written and tested.
- Weeks 7–10 — Migrate. Three desks (40 advisors, 600 clients) migrated. Iranian Bourse symbol catalog imported; Farabourse instruments added. Performance backfilled 12 months in Jalali.
- Weeks 11–14 — Soft launch + audit verify. First 25 advisors operational; audit chain genesis; first quarterly evidence pack produced for SEO.
Outcomes
Pasargad's deployment is fully air-gapped from public infrastructure. All data lives inside the customer's K8s cluster, in Tehran. Persian rendering — including mixed-direction client correspondence, Jalali calendar headers in PDFs, Arab-extended numerals in monetary fields, and rial magnitudes correctly formatted with thousand separators — passes the same CI matrix as English. The first SEO evidence pack was produced in five seconds and verified independently by the customer's security team using the published Python verifier.
Quote
We could install it without calling Modir. The image signatures verified. The SBOM matched what we expected. The audit verifier ran offline. Six months in, we still haven't had to open an outbound connection — and our compliance team produced a regulator pack in five seconds the day they tried.
CTO, Pasargad Wealth — Illustrative
Where they are today
Pasargad (illustrative) has expanded to all six desks (175 advisors), added the trading workflow connected to their Bourse counterparty, and runs the AI commentary graph on a private model endpoint hosted inside the cluster. Per-tenant cost caps stay enforced because LiteLLM enforces them locally; the model itself never reaches the public internet.
Outcome metrics
- 0 outbound connections from cluster
- 100% audit chain integrity
- 5 seconds first SEO evidence pack
- 175 advisors on platform (current)
- Persian + Jalali tested in CI
- Signed images verified at install
Stack
- Topology: on-premise · air-gapped
- Locale: fa-IR · Jalali
- Models: private LLM endpoint
- Custody: Iranian Bourse + Farabourse
Illustrative case study based on representative deployment patterns. Customer name, quotes, and specific numbers are illustrative.