Belitsoft and the expensive art of getting software to work

On a Sunday, the bots arrived. They marched through a digital media company’s catalogue pages until its website could barely serve the people it was meant for. The business collected leads through that site. An unavailable page was therefore a rather expensive blank sheet of paper.

Belitsoft’s September 2026 account of the rescue begins with a familiar disappointment: the customer had already bought protection. What it needed next was someone who understood the application behind it. That distinction runs through the company’s work, from learning platforms to software testing. The purchase is an engineering team. The useful result is a team that knows what it has joined.

The Sunday the website stopped

The attacked platform was a .NET application with more than fifteen years of development behind it. In Belitsoft’s telling, bots had bypassed the previous Cloudflare setup and reached the server directly. Moving to Akamai did not, by itself, settle the matter. A rule intended to stop suspicious traffic also stopped real users. A security system can be impressively strict and commercially useless at the same time.

Belitsoft audited the application, tuned rate limits and added rules for requests the software had no legitimate reason to receive. It also increased server capacity and optimized heavily visited pages. The company reports that, in one recent month, 20.7 million of 31.8 million requests were blocked before reaching the server. These are the supplier’s reported results.

The interesting part is the fit between protection and behavior. A customer’s application determines which pages exist, which requests matter and what ordinary use looks like. Understanding those details changes the rules an engineer can write. Buying a tool is one decision; adapting it to the business is another piece of work.

The backlog that hired a testing team

A different customer, a cybersecurity software company, had a less theatrical problem. Its products needed customer-specific features. Each change created more testing work, and the internal team could not keep up. Belitsoft’s testing account describes regression checks becoming the delivery bottleneck. The first thing under strain was the process for checking changes.

The engagement grew into a hundred-person group: seventy QA engineers and thirty developers. Belitsoft reports 40% lower development and testing expenses. Its dedicated-team account also describes onboarding falling from two to four months to two weeks, supported by team documentation and mentors. Trust gained through testing preceded a broader development assignment.

The staffing choices are worth noticing. The separate QA case describes building an experienced core, then adding middle and junior specialists where the work allowed it. Buying seniority for every task would have been a peculiar form of economy. The customer needed the right mix of people and someone to organize their work.

For a buyer, the 40% comparison needs a denominator. It describes this customer’s development and testing expenses against its local alternative. It is not a price list. The broader purchasing lesson is an inference: compare the cost of useful delivery, including the time existing staff spend teaching newcomers and checking their work. A lower rate is only one part of that calculation.

Two developers, then a learning business

Belitsoft’s education work offers a longer view. Its SharePoint LMS case dates the relationship to 2007 and says the project began with two developers. The published account later describes a team of roughly three dozen and a learning system serving more than five million users. That user count belongs to the customer’s product.

The assignment was to put training into the Microsoft environment businesses already used. The platform connects with Microsoft 365 and Teams, handles courses and assessments, tracks progress and supports mobile access. Belitsoft reports annual development savings above $600,000, based on its comparison with Northern European employment costs.

There is a practical appeal here: an employer can deliver and monitor learning without asking staff to leave their familiar workplace software. Yet the machinery behind that convenience is considerable. Content, identity, reporting and support must agree with one another. A training product becomes a continuing engineering responsibility as customers and features accumulate.

The company also offers customizable learning software, including JoomLMS, and bespoke LMS development. Those are different buying decisions. A configurable platform gives a customer an existing base to adapt; a custom build starts with that customer’s requirements. The choice depends on how much of the intended experience existing software can already provide.

Another education project, Ezyeducation, shows the range of the work. Its published description includes approximately 3,000 teaching videos and 13,000 explanation videos, automatically graded tasks and reports for teachers. Here the value lies in connecting teaching material to assessment and feedback. The video library is large; the workflow is what makes it usable.

A bank moves against the cloud current

Modernization does not always mean moving into the cloud. In April 2024, Noventiq described work with Belitsoft for a Cambodian bank moving from Power BI’s cloud service to on-premises Power BI Report Server after a change in local legislation. The bank then faced product limitations and a lack of backward compatibility.

The joint team proposed separate layers for data ingestion and transformation, a warehouse and an analytical layer, with Report Server distributing reports. It tested the approach through a pilot for one business domain and transferred knowledge to the customer. The account describes a proof of concept, rather than a completed bank-wide transformation.

The useful question is where the work belongs - and who will understand it when something changes.

That project helps locate Belitsoft in the market. It sells engineering services around a customer’s systems: development, integration, testing, modernization and support. A buyer may keep daily product decisions inside its own team and hire extra specialists, or commission a larger delivery assignment. Its range spans .NET, Java, Python and web technologies, alongside cloud and AI work.

An internal team, independent contractors and other software services firms are all alternatives. The case for Belitsoft rests on the particular domain experience and delivery arrangement a customer needs. A catalogue of programming languages is useful for screening suppliers; the people assigned to the job matter more once the contract begins.

The part a buyer can copy

There is a pattern across these projects. Find the constraint before adding capacity. Give engineers access to the application’s history. Test a manageable piece of a proposed change. Keep someone on the customer’s side responsible for what the software is supposed to accomplish. These are transferable practices, not proprietary magic.

They also have conditions. Staff augmentation needs a customer able to set priorities and review results. A migration needs a reason stronger than fashion. A rescue needs enough access to understand the failing system. When a standard product already solves the problem, commissioning custom code adds a responsibility the buyer must be prepared to carry.

Belitsoft’s careers page describes flexible work, learning benefits and an average employee tenure of four years. Continuity has an obvious attraction in this business: an engineer who remembers why a feature exists can save the next engineer a long investigation. That is an interpretation of the economics, rather than proof that any individual project will succeed.

The media company’s website needed to work on Monday. The learning platform needed to keep working as its audience grew. Between those two demands sits Belitsoft’s business: understanding someone else’s software well enough to change it without losing the purpose it serves.