How Banking teams in Singapore automate repetitive work with AI while respecting the PDPA and sector rules — implemented by dgm on osFoundry.
dgm is an independent osFoundry integration partner — not affiliated with osFoundry’s maker (OS LLC), and dgm has no completed client integrations yet.
Automation is where AI pays for itself in banking — but the goal is a measurable reduction in manual work on a specific workflow, not ‘AI everywhere’. Here is a sensible way to approach it in Singapore.
What to automate first in banking
Good first candidates are high-volume, repeatable and text- or data-heavy: real-time fraud and transaction-monitoring, AML and suspicious-activity detection and customer-service copilots over policy and product knowledge are typical. Avoid starting with one-off or highly bespoke work — the return is harder to prove.
A practical automation sequence
- Pick one repetitive banking workflow — for example real-time fraud and transaction-monitoring — and write down the current steps and time spent.
- Set a baseline so you can measure improvement, and confirm where the data lives and whether it must stay in Singapore.
- Build a small automation with a human in the loop, check its output against the regulator expectations that apply, then expand.
| Stage | Focus |
|---|---|
| Scope | One workflow, current steps, time spent |
| Baseline | Measurable starting point + data-residency check |
| Pilot | Human-in-the-loop build, checked against compliance |
| Expand | Roll out once value is proven |
Compliance while you automate
Banks are licensed and supervised by the Monetary Authority of Singapore (MAS), the integrated central bank and financial regulator. MAS promotes responsible AI through its FEAT principles (Fairness, Ethics, Accountability, Transparency, published November 2018) and the Veritas fairness-assessment toolkit, and has issued AI risk-management guidance for the sector. Banking is the canonical high-stakes automated-decision sector in Singapore — credit decisioning, fairness assessment under FEAT and auditability matter most here, and AI deployment is a board-level governance matter, not just an efficiency play. Because there is no standalone binding AI Act in force in 2026, the constraints to design around are the PDPA (consent, notification, protection and the PDPC’s AI advisory guidelines), the Cybersecurity Act where critical infrastructure is involved, and the sector rules above.
Keeping automation in Singapore
MAS does not mandate general data localisation, but auditability and the Association of Banks in Singapore’s data-sovereignty guidance push many banks toward in-region or self-hosted deployment. osFoundry’s managed cloud pins data to the US, EU or Japan — it does not currently offer a Singapore managed region (its nearest managed region is Japan). For data that must stay in Singapore, the honest path is self-hosting osFoundry (BYO Cloud) inside a Singapore cloud region such as AWS Asia Pacific (Singapore) ap-southeast-1, Microsoft Azure Southeast Asia (Singapore) or Google Cloud asia-southeast1 (Singapore), or running models locally on-device. osFoundry can run your chosen model under one layer and be self-hosted in a Singapore region or run locally for sensitive workflows.
Where dgm fits
dgm is an independent integration partner that helps Singapore businesses adopt osFoundry — scoping a first use case, handling the build, and connecting AI to the systems you already run. dgm can build the first banking automation with you and keep a human in the loop. dgm is independent of osFoundry’s maker (OS LLC) and has no completed client integrations yet, so everything described here is a service offered, not a past result. If you want to scope a practical first project, dgm can help you map it out.