Frequently asked questions.

With a short discovery call. We listen to how the problem shows up, who it affects and what has been tried so far. Then we write down the scope — and what will not be done; the latter is usually more decisive.

Fixed-price when the scope can be defined clearly; time-and-materials when the work needs discovery and the scope becomes clear along the way. We tell you which fits after the first call.

The team is based in Ankara. Site surveys, installation and commissioning are done on site; development and support run remotely.

Yes. We run projects across Türkiye and abroad; when on-site visits are needed, we include them in the plan.

Yes. We were founded in 2019 as KB Yazılım and have continued as Bella Binary since 2024.

We are at Teknopark Ankara (İvedik OSB, Yenimahalle / Ankara). Trade name Bella Binary Yazılım; MERSIS 0163111961900001, tax number 1631119619. These details are also in the site footer and on the Company page.

Your choice. On-premise, cloud or hybrid deployment are all possible. In industrial projects hybrid is a common choice: data stays on site and only summaries go to the center.

Directly with systems that have an API; for the rest we use the database, file-based transfer or UI automation. Which one is possible is verified technically during discovery.

Yes. In custom development the source code is handed over to you and it is yours; licenses of the open-source libraries used are listed separately. Our off-the-shelf products are licensed.

Role-based permissions, encrypted communication, audit logs and backups are standard. With on-premise deployment, data never leaves the company network. See the security section on the Technology page for details.

It depends on the scope. Instead of one long delivery we work in short cycles: the first working version ships early and we build on it. That way you can see where the timeline stands from day one.

Yes. We offer a maintenance agreement covering support, maintenance and further development after delivery. Since the system is delivered documented and hand-over-ready, your own team can also run it.

Yes. User and administrator training is part of commissioning; the goal is for your team to run the system on its own.

1 year of warranty and 1 year of maintenance from delivery. During the warranty, defects in the delivered scope are fixed free of charge; maintenance covers updates, security patches and user support. At the end of the period the maintenance contract can be renewed.

By the written scope. A deviation from the behavior defined in the approved scope is a defect and is fixed under warranty. A request outside the scope is a new feature, estimated and approved separately. Because the scope is written up front, the distinction rests on the document, not on debate.

Yes. Response and resolution times, support hours and priority levels are set in the maintenance contract. A separate support level can be defined for systems that directly affect production.

You do. In custom development the source code and data belong to the client; if the project ends at any stage, the code for the work done so far and all data are handed over.

Yes. The data is yours; a database backup and exports in standard formats (CSV, Excel) are provided whenever you ask. For ready-made products, your data is also handed over when the contract ends.

The list of open-source components used and their licenses is delivered with the project. We mainly use commercially permissive licenses such as MIT, Apache 2.0 and BSD; if a license that requires publishing source code is needed, we discuss it beforehand.