
Banking · 2025
A mobile banking app, rebuilt from scratch
A bank with 30 branches
148,000monthly active users 12 months after launch
- Kotlin
- Swift
- Java, Spring Boot
- PostgreSQL
We test systems built by you or by others: before every release, under load and with automated tests.

Our QA team has 14 engineers, most of them in the Ganja office. We use Playwright for the web, Appium for mobile and k6 for load. We plug the tests into your CI pipeline: they run after every change and the results go to the team.
In two weeks we check the system’s key scenarios and hand over the bugs found, by priority.
A regression suite in Playwright and Appium, run in CI on every merge.
Sale-day load with k6 and a report on the bottlenecks.
A checklist and a signed report for every version.
A full-time test engineer in your team, by the month.
2–3 days
The system, the environments, existing tests and risks.
2–3 days
What we test by hand and what automatically, and the priorities.
1–3 weeks
Scenarios, automated tests, a load test; bugs go into your tracker.
1 day
What we found, how serious it is and what to do next.
Prices without VAT (18%), at the rates in force since 1 January 2026.

Banking · 2025
A bank with 30 branches
148,000monthly active users 12 months after launch

Public sector · 2022
The general contractor of a state agency
1.2mapplications in 2025

Retail · 2023
An electronics chain with 9 stores
13%online share of sales, up from 4%
Not everything. Scenarios where a mistake is expensive, such as money, sign-in and contracts, run automatically; the rest by hand. Usually 60 to 70% of the regression suite is automated.
No, a test environment that copies it. On the live system only a short, agreed check at night.
Write one sentence or pick the screens, integrations and deadline: the team, the weeks and a price range appear at once.