Processes, Sharia control, integrations and AI — as a layer on top of your core banking system. Accounting stays in the core; everything else the bank builds and changes itself: visually, without code and without waiting for the vendor.
Islamic banking is not new accounts in the core — it is different processes: a deal instead of a loan, a Sharia check at every step, strict separation of funds. A classic core banking system has none of this, and modifying the core means getting stuck with the vendor.
Business logic, Sharia rules and CRM fields get built into Core Banking. The core gets overloaded, update versioning breaks, and every process change becomes a vendor ticket and months of waiting.
Sharia control lives in policies and Excel, not in the system. A violation is discovered after the fact, during an audit — instead of being stopped the moment it happens.
One platform, delivered as a single project. The outside world only ever talks to the orchestrator — never directly to the core. The core stays thin, closed and stable.
Visual processes on a low-code engine: an analyst builds and changes the process on a diagram, not in the vendor's code. First flow in production — 4 weeks.
Subflows, retry with backoff, catch nodes, SLA timers. The deal pipeline is a diagram, not a "black box".
Catch nodes stop an operation on violation and escalate to the supervisory board. Control is built into the process, not into a policy document.
Flow versioning, rollout without a maintenance window, rollback to any version. Changing a process doesn't stop the bank.
Each process runs in its own environment: a failure in one never affects the others.
PostgreSQL / Mongo / Redis: client attributes, scoring, audit trail, flow states.
Flows and connectors are versioned in the bank's private repository. The bank owns its processes instead of renting them.
Every product ships as a visual deal pipeline with the Sharia flow built in: documents, checks, escalations and core postings are steps on a diagram the bank's analysts control.
The bank buys the asset and sells it to the client at a disclosed markup. Pipeline: application → asset purchase → transfer of ownership → installment schedule.
The bank buys the asset and leases it out. Rental schedule, maintenance events and ownership transfer (Ijara Muntahia Bittamleek) are steps of the flow.
Joint financing: profit is split by an agreed ratio, losses by capital share. Includes diminishing Musharaka for property finance.
The bank provides capital, the client manages the venture. Profit distribution and loss absorption are computed and documented by the engine.
An interest-free loan with principal-only repayment. The flow enforces zero-markup terms and tracks the repayment schedule.
The bank acts as an agent for a fixed fee — agency deposits and investment mandates with a full audit trail of the agent's actions.
An enterprise low-code platform, on-premise. A single point of entry for the outside world and a single integration layer for internal systems — with no cloud dependency.
A single point of entry: REST, SOAP, gRPC, GraphQL. Auth, rate limiting, an integration registry.
A new connector is a subflow copy plus configuration — not a development project. Including the adapter to your core.
Oracle, JDBC/ODBC, Kafka, webhooks, SFTP, email, XLSX, CSV/XML/JSON — out of the box.
On top of core data and orchestrator events runs an intelligence layer: agents take over routine work, analytics turns data into sales. The core stays untouched.
Deal pipelines, scoring, support: routine work runs without manual labor — the manager receives a ready result.
Response prediction, next-product recommendations, RFM and behavioral segments for targeting.
A dashboard with finances, turnover and trends. The bank sees the whole client and offers the right thing at the right time.
Tax ID, industry, turnover — a lead pipeline for Islamic financing of small business.
Tasks, KPIs and AI recommendations for every client — the manager works with suggestions, not raw data.
Conversion, risk and line-of-business KPIs in real time — for the management board and the supervisory board.
Not a "boxed product" but a project delivery: every stage leaves a working result behind.
Architecture and core audit, the list of integrations, APIs and SLAs. Scope and plan are fixed.
The platform on-premise inside the bank's perimeter, the core adapter, Git and environments. First flow — in production.
Deal pipelines go live: Murabaha and Ijara with the Sharia flow, then the rest of the product lineup.
AI agents, "Bank 6.0", external services and channels — as demand grows, by the bank's own team.
A perpetual on-premise license, ready integrations in the delivery, local connectors — defined by Discovery. Support and evolution — 15% per year.
| Package | What's inside | Who it's for |
|---|---|---|
| ENGINE | BPMN + Orchestrator + AI — the platform on-premise, the core adapter, Islamic process templates, the Sharia flow, the bank's Git | A bank or MFO launching an Islamic line of business on its own core |
| ENGINE+ | ENGINE + "Bank 6.0" — plus the marketing ecosystem: campaigns, a partner portal, client and manager cockpits, CRM | Banks building an ecosystem around Islamic products — the recommended path |
| CUSTOM | Selected modules — individual pipelines, integrations or AI modules for a specific task | Banks with a process platform in place that need specific blocks |
Exact pricing follows Discovery (2–4 weeks): we fix the list of systems, APIs, SLAs and the implementation plan.
Five steps from first contact to a pilot — each with a concrete result. The PLATMA team is ready to present the solution to the Supervisory Board: architecture, timeline, SLAs, a demo of working environments.
We will run a demo and answer your questions on architecture and implementation.
Request a demoAn enterprise low-code platform for orchestration and AI. On-premise, the bank's Git, isolated execution environments.
IT Park Uzbekistan resident