Back
Template · for discussion

Partnership Memorandum of Understanding

How we work together — your brand and franchise; our platform technology

1. Parties

This MOU is between Ijarah OS (“Platform Partner”) and the undersigned financial institution (“Bank”). It frames a licensed partnership for access to the Ijarah OS — not a one-off software development assignment that transfers ownership of the platform.

2. Purpose

Enable the Bank to originate and manage Islamic home finance (including Ijarah and Forward Ijarah) using Ijarah OS infrastructure under the Bank’s brand, subject to the Bank’s credit and Shariah governance.

3. Ownership

  • Platform technology (Ijarah OS): software, agents, user experience, Policy Studio engine, documentation, trademarks “Ijarah OS”, and improvements.
  • Bank franchise: trademarks, logos, customer data, credit policies as content, Shariah board resolutions as content, and funded-customer relationships.
  • No transfer of platform ownership: Fees under any SOW purchase a license and services, not ownership of platform technology. Source code is not delivered unless a separate escrow/enterprise agreement expressly states otherwise.
  • Other partner banks: Ijarah OS may license the same platform to other institutions. Each bank’s configuration and data remain private and confidential.

4. License

Subject to payment and this MOU and applicable SOWs, Ijarah OS grants the Bank a non-exclusive, non-transferable right to access and use a private bank environment for internal home-finance operations, including a customer journey under the Bank’s brand.

5. Configuration vs custom software

The Bank may configure policy packs (eligibility, DBR, FTV, documents, Shariah rules, exceptions, messaging) via Policy Studio. Configuration does not create Bank ownership of the engine. Custom system connections may be scoped as services; resulting adapters remain platform technology unless expressly agreed.

6. Data and confidentiality

  • Bank personal data remains the Bank’s responsibility as controller where applicable.
  • Ijarah OS processes data to provide the service; PDPL and contractual DPAs apply.
  • Neither party discloses the other’s confidential information except as required by law.

7. Commercial model

Typical structure: (a) setup / onboarding; (b) recurring platform license; (c) usage-based fees (e.g. per funded file). Detailed pricing appears in each SOW. Pilot SOWs do not transfer platform ownership.

8. Term and exit

Term per SOW. On termination, the Bank may export its policy content and case data in industry-standard formats for a defined window. Platform access ceases; Ijarah OS retains platform technology.

9. Non-binding nature of this template

This page is a discussion template for product evaluation. It is not executed until signed by authorised representatives with jurisdiction and governing law completed by counsel.

© 2026 Ijarah OS. Template only — not legal advice.