Reading time: 9 minutes
Author: ITDS Team
A Dutch bank that brings in nearshore engineers is entering an ICT third-party arrangement, so the vendor has to fit the bank's risk framework as well as its backlog. This guide compares six nearshore software development partners that Dutch banks can consider, with delivery in Poland, Portugal and the wider region, and lists what to check before a vendor reaches your supplier list.
Last updated: November 16, 2026.
Publisher's note: this guide is published by ITDS, one of the companies described. Partners appear in alphabetical order, using one template. The order is not a ranking.
What a Dutch bank needs from a nearshore partner
Since January 17, 2025, DORA, the EU regulation on digital operational resilience, has set rules for how financial entities manage ICT third-party risk, including contract terms, a register of arrangements and exit planning. The text is on EUR-Lex.
In practice, a suitable partner can support your due diligence, accept your security requirements and audit rights, and plan for a clean exit. Delivery inside the EU simplifies some data protection questions, but it does not make a vendor compliant on its own. This is general information, not legal advice.
How we compare nearshore software development partners for banks
For each partner we note when it is worth considering, what public evidence supports that, and what to clarify before a contract. We separate banking references from general financial-services experience, and delivery locations inside the EU from those outside it. Figures published by the partners are their own claims.
Nearshore software development partners for Dutch banks: comparison
| Partner | When to consider it | Engagement models | Delivery locations | Netherlands presence |
|---|---|---|---|---|
| ITDS | Senior engineers with financial-services knowledge | Staff and team augmentation, project delivery, maintenance | Poland, Portugal | ITDS Netherlands consultancy, Amsterdam |
| Neontri | Mobile banking, payments and data platforms | Custom software, team augmentation, IT outsourcing | Poland | Not found |
| Scalo | Java, .NET, testing and data work on long projects | Staff augmentation, dedicated teams, software delivery | Poland | Not found |
| Sii | Several teams across domains with one vendor | Delivery teams, outsourcing, end-to-end projects | Poland, Sweden, Ukraine, India | Lists the Netherlands among its markets |
| The Software House | Custom digital products and payment platforms | Custom development, dedicated teams | Poland | Not found |
| Velv | Teams from Portugal on Western European hours | Team extension, managed teams | Portugal, Brazil | Office in Amsterdam |
ITDS
When to consider it: when the bank needs senior engineers who already understand banking processes, delivered from inside the EU.
Evidence: ITDS Netherlands is a consultancy that has served Dutch and international banks, insurers and pension funds since 1998. Separately, ITDS Poland and ITDS Portugal supply engineers through ITDS Nearshore. Its published case studies cover leasing systems for CreditPlus, financial integration for Sofinco and lending workflows for Q2. None of these is a Dutch client.
Engagement models: staff and team augmentation, recruitment as a service, project delivery and maintenance, and Build-Operate-Transfer. ITDS handles contracts and payroll for the engineers it places. Data protection terms, access and day-to-day direction are agreed with each client. Delivery from Warsaw, Wrocław, Lisbon and Porto.
What to clarify: which engineers on the shortlist have worked inside a bank, and in which domain.
Neontri
When to consider it: when the scope covers payments, mobile banking or offloading data from core systems.
Evidence: according to its website, Neontri has built software for banking and fintech since 2013. It co-created PKO Bank Polski's IKO mobile banking app, built a data offloading system for the same bank and delivered a PSD2 hub for KIR. It states ISO 27001 and ISO 22301 certification.
Engagement models: custom software development, team and staff augmentation, and IT outsourcing. Headquartered in Warsaw.
What to clarify: references from banks outside Poland, and how its frameworks fit your architecture.
Scalo
When to consider it: when the bank needs Java, .NET, testing, analysis or data skills on a long engagement.
Evidence: Scalo traces its beginnings to 2007 and, according to its website, has more than 650 experts. According to ITwiz, it signed a three-year agreement with PKO Bank Polski covering Java and .NET development, testing, analysis, and data and AI projects.
Engagement models: staff augmentation, dedicated teams and software delivery. Offices in Wrocław, Warsaw, Katowice, Kraków and Gdańsk.
What to clarify: experience with Western European banks, and how engineers are onboarded into a bank's security setup.
Sii
When to consider it: when the bank wants to scale several teams across domains with one large vendor.
Evidence: according to Sii's nearshore page, the company has more than 7,500 experts and assembles delivery teams within one to three months. It lists the Netherlands among its markets and took third place in the main category of the Polish IT@BANK 2019 ranking.
Engagement models: nearshore and offshore delivery teams, consulting, engineering and business services, from Poland, Ukraine, Sweden and India.
What to clarify: whether your contract can limit delivery to EU locations.
The Software House
When to consider it: when the scope is a customer-facing product or a payment platform.
Evidence: The Software House is a Polish custom software company headquartered in Gliwice. Its public profiles describe fintech work on payment platforms and digital products.
Engagement models: custom software development and dedicated teams.
What to clarify: references from regulated banks, not only fintechs, and evidence of its secure development practices.
Velv
When to consider it: when the bank wants a team in Portugal, either embedded in its own processes or managed by the vendor.
Evidence: according to its website, Velv has built nearshore teams since 2017 and shows BNP Paribas, Crédit Agricole and Natixis among the brands it has worked with. It has a dedicated page for Dutch companies.
Engagement models: team extension, managed teams and managed services. Teams in Lisbon and Porto, plus Rio de Janeiro, and an office in Amsterdam.
What to clarify: whether your team will be staffed from Portugal only.
Choosing the engagement model
The model decides who carries delivery risk, which matters to your risk function as much as to your engineering leads.
With staff augmentation, engineers join your teams and your managers direct their work. The bank keeps control of architecture, priorities and production access. A dedicated team works only for the bank and, depending on the contract, may be run by a lead on the vendor's side. Project delivery hands a defined scope to the vendor, which shifts more delivery risk to the partner but needs tighter acceptance criteria and oversight.
How an engagement with a bank usually starts
- Scope and model: augmented engineers, a dedicated team or a delivered project.
- Due diligence: third-party risk assessment, security questionnaire and, where relevant, DORA classification.
- Shortlist and interviews with the engineers who will actually join.
- Contract: services agreement, data protection terms, audit and access rights, exit plan.
- Onboarding: access, security training and integration into your teams.
Due diligence often takes longer than sourcing, so ask each vendor how long its last bank onboarding took from contract to first commit.
Security checks for a bank engagement
A certificate is a starting point, not proof that your team is covered. Ask which locations and services an ISO 27001 certificate actually includes, and whether the engineers assigned to you work inside that scope.
Then look at how work will happen day to day. Many banks give external engineers access only through the bank's own virtual desktop or VPN, with least-privilege rights and logging. Agree how background checks are handled, how access is revoked when someone leaves, and how the vendor's secure development practices fit your code review and release process. These points shape onboarding time as much as hiring does.
Questions for your RFP
- Which banks have your engineers worked inside, and in which domains?
- Where will each engineer work from, and which entity employs them?
- How do you support our DORA third-party risk obligations?
- Which certifications apply to the team serving us, and what is their scope?
- Do you use subcontractors, and will you disclose them?
- Who owns the code and IP from day one?
Nearshore software development partners for Dutch banks: FAQ
What are the best nearshore software development partners for Dutch banks?
The fit depends on scope. A large vendor such as Sii offers scale across many teams and domains. ITDS combines a Dutch consultancy with senior engineers delivered from Poland and Portugal. Neontri has documented bank projects in payments and mobile banking. Compare two or three partners on the same brief.
Does DORA apply to nearshore software development for banks?
DORA covers how financial entities manage ICT third-party risk, so it can apply to contracts with software and staffing vendors. Your legal and compliance teams decide how it applies to a specific arrangement.
Poland or Portugal: which is better for a Dutch bank?
Both are in the EU. Poland shares the Netherlands' time zone and has a large pool of senior engineers. Portugal is one hour behind. The choice usually comes down to the stack, language skills and team size you need.
How long does it take to start a nearshore team at a bank?
Sourcing can take weeks, but due diligence and security onboarding often add more. Ask for the vendor's most recent bank example from contract to first commit.
Does EU-based delivery make a vendor GDPR compliant?
No. It simplifies international data transfers, but you still need data protection terms, security controls and clear access rules.
How to narrow your shortlist
Agree the scope and risk model internally first, then send the same brief and RFP questions to two or three partners. Compare the engineers they propose and how well they handle your due diligence, not only the rate.
Looking for engineers who already know banking? Send us your toughest role.