A new architecture in every era, the same team.

Globya's history at a glance

In the software world, 25 years means several generations of technology coming and going. What mattered to us was never jumping on every new trend, but adopting what genuinely helps our clients' businesses at the right time. The table below sums up the main milestones of that journey.

2000 — The early years of the dynamic web

When Globya was founded, online commerce was still a subject of debate in Türkiye. Most companies' websites were nothing more than a few static pages of introduction. In our first projects, we used ASP and classic PHP to build dynamic corporate websites whose content could be updated from an admin panel.

Back then, things that seem ordinary today were major innovations: a product catalog pulled from a database, news and announcements that could be added without technical knowledge, contact forms that went straight to email. This era was also the beginning of our approach: "you run the site, we stand behind it."

2005 — The era of object-oriented software and XML

As projects grew, writing code that was organized, reusable and easy to maintain became essential. With PHP 5, we moved to object-oriented programming (OOP). Thanks to XML and SOAP services, different systems began exchanging data with each other in a structured way for the first time; this laid the groundwork for our integration work today.

In the same period, we used AJAX and jQuery to build interfaces that worked without reloading the page. User experience was no longer measured by looks alone, but by speed and smoothness as well.

2008 — IMFLEXI is born

In 2008, we developed our own e-commerce platform, IMFLEXI. The goal was to give companies that had hit the limits of off-the-shelf platforms a flexible backbone. From the very first version, it included a rule-based engine that showed content based on user behavior; it was an early form of what we now call AI-powered personalization.

IMFLEXI has kept evolving ever since: multiple stores, multiple languages and currencies, B2B and B2C running on the same platform, the KitBuilder product configurator, a visual page editor, and marketplace, payment, shipping and ERP integrations have all been added.

2014 — API-first design and microservices

As smartphones spread, every system had to serve data to the web, to mobile apps and to other software. Instead of large, single-piece (monolithic) software, we began building structures made up of parts that talk through REST APIs and can be updated independently.

In this period, mobile-first design stopped being a choice and became a necessity. With tools like Docker, we made development and production environments consistent with each other, largely leaving the "it worked on my machine" problem behind.

2018 — Cloud and headless architecture

Server management moved to cloud infrastructure; adding resources when demand grew became a matter of minutes. The "headless" approach spread in e-commerce: the commerce engine in the back was separated from the storefront customers see. As a result, the same product data could feed the website, the mobile app and marketplaces all at once.

E-commerce was no longer a single platform but an ecosystem of connected systems. The weight of our integration work grew noticeably in these years.

2022 — Large language models

As large language models (LLMs) reached a wide audience, the nature of software changed once again. We added an AI layer to our products with semantic search, meaning search based on meaning rather than keyword matching, along with embeddings and vector databases. Being able to ask questions of ERP data in plain Turkish in READERP was also made possible by what we learned in this period.

2026 — AI agents and GEO

Today, websites are read not only by people but also by AI assistants. A user who asks ChatGPT, Gemini or Perplexity a question often gets their answer without ever visiting a website. That is why making sure AI understands a site correctly, known as GEO (Generative Engine Optimization), has become as important as classic SEO. We describe our approach on the SEO and GEO page.

In the same period, AI agents that carry out specific tasks on their own began to enter business processes. We use these tools in a measured, supervised way, both in our own production work and in our clients' systems.

What hasn't changed

Over 25 years, languages, tools and architectures have changed many times. The one thing that hasn't changed is how we work: understand the need first, then choose the right technology, and stay by your side after delivery. You can find the tools we use today on the technologies page.