About Us

Experience and continuity #

Our founder Sinan Alyürük first met Linux in a university lab in 1992, started work in 1995, and has been working with MySQL and PostgreSQL databases since 2000. He earned that experience in systems administration and database administration on Linux and Unix, in very high volume telecommunications, e-commerce and media systems.

Tuğrul Aksoy joined the team as a consultant in 2024. He combines his experience in PostgreSQL and Patroni with MySQL and MariaDB expertise.

Since the firm was founded, we are still working with the organisations that engaged us under contract.

We fill the experienced DBA gap #

Finding an experienced database administrator (DBA) for open source databases is one of the hardest problems organisations in Turkey face. A DBA takes years to develop. Database administration demands a wide competency matrix that reaches well beyond SQL into software development, Linux systems, network administration and cyber security. Expertise in this field is shaped by field experience: operations carried out on live production systems and highly critical problems brought to a resolution.

In organisations that try to close this gap with their own staff, database administration usually becomes a side duty for the system administrator or the software team. While the system runs normally, that arrangement causes no trouble. When a problem hits the database, production is affected directly, and the organisation needs a support approach run by a specialist — one that will not lead to long outages or data loss.

We meet that need without replacing the organisation’s own team. Your team knows the system and the application better than we do; we bring the depth on the database side. We share the reason behind every change we make, and we document every structure we build. Our aim is not to make the organisation dependent on us, but to leave the team able to run the system with confidence.

Our philosophy is to protect our customers’ data systems from the problems that may arise, to keep high availability sustainable, and to carry out optimisation proactively, before those problems surface.

We reduce cloud cost by measuring it #

A large share of organisations running databases in the cloud find the monthly bill growing faster than they forecast. Because adding resources in a cloud environment takes a single setting change, moving to a larger instance becomes a common habit in place of solving the performance problem for good.

We approach cloud cost from four directions:

• Query tuning. Once the slow queries are fixed, a smaller instance is usually enough. Capacity gained without growing the hardware shows up on the bill directly and permanently.
• Sizing and the storage layer. We scale oversized servers down to the real workload, and we choose the IOPS and storage class from measured usage.
• Archiving and the data lifecycle. We limit the storage and backup cost of ever-growing tables with a retention policy, and we run the archiving itself verifiably with our own product, GoArchive .
• From managed services to an independent infrastructure model. Managed database services (DBaaS) reduce the operational load, but they carry high service costs. Once we take that operational responsibility on under our support agreement, open source installations on the organisation’s own infrastructure (IaaS / bare metal) bring the total cost of ownership (TCO) down markedly. We work the figures out together and decide by looking at the data.

Because measurement is what tells us the right path, every cloud cost engagement starts by establishing current usage. On most systems we run performance tuning and the cloud cost work together, as two outcomes of the same measurement.

We are part of the free software ecosystem #

Every service we provide runs on software that grants everyone the freedom to run, study, modify and distribute it. MySQL, PostgreSQL and MariaDB — as well as Percona XtraBackup, pgBackRest, Patroni and ProxySQL — reached their present maturity through the work of developers contributing from all over the world.

The purpose of free software is not to pay something back, but to create an ecosystem that grows through everyone’s contribution. As a firm that benefits from that ecosystem, we prefer to be on the developing side rather than only the consuming side.

The tools we build in our daily work are published under the same freedoms, under the MIT licence, with the source open to everyone on GitHub:

• GoFast parses MySQL slow query logs and works out which query pattern is consuming the total time.
• GoArchive archives related MySQL data in dependency order, verifies that it reached the destination complete, and deletes from the source only once verification has succeeded.
• dbsgomysql provides MySQL schema facts and validation checks to Go applications as a library.

We work to contribute to free software based data systems and to the good of the community.

How we work #

• We measure first. On every system we take on, we establish the current state before anything else, and we build our recommendations on that measurement.
• We recommend free and open source solutions to our customers. The right to install and integrate every component we propose comes from its open source licence. We work independently of vendors, and we do not propose a product that requires the organisation to buy a licence. We support the free software community.
• We agree the limits of our responsibility with the customer. We apply the technical measures auditors ask for at the database layer. Because the legal assessment of compliance remains with the organisation and its legal counsel, we set the boundaries out together at the start of the project rather than offering a guarantee.
• We plan rollback scenarios carefully in our projects. Every change destined for production is verified in a test environment first, and the rollback step is prepared alongside the change itself.

Detailed questions and answers about how we work are on the Frequently Asked Questions page.