Ferryt Low-Code Platform in Banking: How It Works

What is Ferryt Low-Code Platform?

Ferryt is a low-code platform developed by DomData that enables organizations to design and develop business applications and multi-stage processes without having to build every component of the system from scratch.

Within a single environment, organizations can combine processes, workflows, forms, data, business rules, documents and communication with other systems. Ferryt also supports BPMN 2.0 process modeling and integrations using REST and SOAP.

That sounds technical, but from a business perspective the idea is much simpler. An organization can change and develop processes faster without rebuilding large parts of its existing IT environment every time.

And this is exactly where Ferryt Low-Code Platform begins to fit particularly well into the banking environment.

Ferryt in banking. Why does this combination work?

A bank is essentially a large process factory. Opening a product, submitting a loan application, assessing risk, making a decision, preparing documents, obtaining approvals, completing a sale, providing post-sale service, managing debt collection, handling complaints or running internal processes.

Each of these areas involves:

• data coming from multiple sources,
• users and roles with different permissions,
• business rules and decisions,
• documents and forms,
• communication with other systems,
• security and auditability requirements,
• exceptions that also need to be handled correctly.

On top of that come regulatory requirements and the need to determine precisely why a particular decision was made and what happened at each stage of a process. It is an environment naturally suited to process platforms.

Ferryt can operate as a layer connecting the business process with data, users and the bank’s existing systems. It does not have to replace the core banking system or other key solutions. Instead, it can connect them and guide the user through the entire process.

The scale of some implementations shows that Ferryt is used for more than simple internal applications. DomData describes the use of Ferryt at organizations including BNP Paribas Bank Polska, mBank and Bank Pocztowy.

At mBank, Ferryt 2.0 was used to automate the process of handling enquiries submitted to the bank by external institutions. According to DomData, the system handles tens of thousands of requests per month in this area.

Ferryt is more than BPM and process diagrams

From the outside, it is easy to put Ferryt into the category of “another BPM platform” or “another low-code platform”. But that is a significant simplification.

In a banking environment, drawing the process itself is usually the easiest part of the puzzle. The real challenge begins when that process has to retrieve data from several systems, execute the right rules, verify permissions, pass information further, handle exceptions, generate a document and do all of this securely and in an auditable way.

The process is only one part of the system

The larger the organization and the more critical the process, the less it is about low-code itself and the more it becomes about architecture, integrations, data, testing and responsibility across systems.

And this is where the first paradox appears.

Low-code does not mean low-skill

The term low-code may suggest that if we write less traditional code, we also need fewer technical skills. For simple applications, that may sometimes be true. In a large banking system, it definitely does not have to be.

Ferryt can reduce the amount of traditional development required to build a process, but it does not magically make the complexity disappear. That complexity simply moves elsewhere.

Someone still has to design the integration. Someone still needs to understand the data model. You still need knowledge of SQL, APIs, external systems, error handling, testing, deployment and dependencies between individual components.

That is why a strong Ferryt Developer or Ferryt consultant often combines several different skill sets: part developer, part analyst, part integration specialist and part process expert.

Add knowledge of a specific banking area – such as mortgages, risk or debt collection – and the profile becomes even more specialized.

Ferryt Developers are in demand. And this is where the problem begins

The situation becomes even more interesting when we look at the talent market. The ecosystem of Ferryt specialists is significantly smaller than those built around Java, .NET, JavaScript or popular cloud platforms.

Experience has primarily been gained through specific implementations, working for the platform vendor, system integrators or directly within financial institutions. This is not a technology where completing a course and two portfolio projects is necessarily enough to enter the market as a junior specialist.

Knowing the platform itself is often not enough

Current recruitment activity illustrates what companies actually expect. In September 2026, the market includes roles connected with developing credit, debt collection, customer-facing and internal processes on the Ferryt platform.

Requirements include experience in process modeling on Ferryt, but a closer look at these roles reveals expectations related to banking processes, SQL, XML, REST, SOAP and integrations with external systems.

For example, Bank BPS was looking for a specialist familiar with Ferryt 2.0, the RDE module, SQL, REST and SOAP, as well as integrations with external systems.

That no longer sounds like simply hiring a “low-code developer”. It sounds more like looking for someone who knows Ferryt, understands banking, can communicate with the business and also understands what is happening underneath the entire process.

And at that point, the candidate pool becomes considerably smaller.

Why are Ferryt skills so difficult to source?

The problem is not simply that relatively few people list Ferryt on their CV. More importantly, knowledge of the platform itself is often not enough.

One bank may need a Ferryt specialist who also understands the mortgage process. Another project may require experience with decision engines and credit risk. Another may be highly integration-focused and require strong knowledge of SQL, APIs and external systems.

In practice, organizations are not looking for a single skill. They are looking for the intersection of several skills within the same person.

And that is precisely why finding the right specialist can be much more difficult than an organization initially expects.

Ferryt and the technology paradox

In IT, we love talking about new technologies. A new AI model? Everyone has an opinion. A new framework? Dozens of comparisons will appear in no time. A new database? Another potential “game changer”.

Meanwhile, businesses often have the greatest need for specialists in technologies that are not new at all.

A solution was implemented deep inside an organization several years ago. The platform grew. More processes and integrations were added. The system began supporting critical parts of the business, and the organization realized that it would continue developing it for many years.

Ferryt is a very good example of this phenomenon.

It may not be the most talked-about technology on the market, nor does it compete for attention with generative AI. But it increasingly appears where something entirely different matters: real business processes used every day by large financial institutions.

Is it worth developing Ferryt skills?

From an organization’s perspective, the answer naturally depends on its technology environment and the scale at which the platform is used.

However, if Ferryt already supports important banking processes, the skills required to develop it stop being a niche addition. They become part of what enables the organization to maintain, change and scale an important part of its IT environment.

From a specialist’s perspective, the situation is equally interesting. Ferryt remains a relatively specialized technology, but it operates in a sector where solutions can stay in use and continue evolving for many years.

Ferryt experience can also be combined with knowledge and skills in areas such as:

• credit processes and other banking processes,
• BPMN and business process modeling,
• SQL and relational databases,
• REST, SOAP and system integrations,
• business and systems analysis,
• testing and error handling,
• banking systems architecture.

And that combination may prove considerably more valuable than simply knowing another low-code tool.

Ferryt in banking – key takeaways

Ferryt Low-Code Platform is an interesting example of a technology that did not need enormous media hype to establish a specific role in the market.

DomData has built a platform that addresses an important challenge faced by large organizations: how to develop complex business processes connected with multiple existing systems. Banking is a natural environment for this type of solution.

1. Ferryt is more than a BPM tool. In large implementations, data, integrations, business rules, testing and architecture all matter.
2. Low-code does not mean low-skill. Reducing the amount of traditional code does not remove system complexity.
3. Banking is a natural environment for process platforms. The large number of processes, rules and systems creates clear business use cases for this type of technology.
4. The hardest part is finding the right combination of skills. Knowledge of Ferryt itself may only be the beginning of the requirements list.
5. A less visible technology is not necessarily a less important technology. Systems supporting critical business processes may need to be maintained and developed for many years.

As use of the platform grows, a second challenge emerges: finding people who know how to develop it. And this is where the traditional “low-code” label can become slightly misleading.

Finding a strong Ferryt specialist can sometimes be more difficult than finding another Java Developer. Not because Ferryt is inherently more complex than Java, but because there are fewer experienced specialists and knowledge of the platform itself is often only the first item on the requirements list.

And that is exactly why we are likely to hear more about Ferryt in the years ahead.

FAQ – Ferryt Low-Code Platform

Frequently asked questions about Ferryt, its use in banking and the skills required to work with the platform.