Get a quote

Web Software · Istanbul

Web Software for Istanbul businesses

If you already run a site in the Istanbul market, the job is rarely to rewrite it. We look for what carries the page weight and keep the work there. On the KGM SsangYong corporate site that meant putting catalog reads behind a cache and leaving the sections that already worked untouched.

Web Software — Istanbul

Istanbul carries the country's heaviest commercial and technology traffic, so a page that opens slowly costs a visit straight away. On corporate sites the weight tends to collect somewhere specific: a catalog query that runs again for every visitor, or an image folder where nobody can say which file belongs to which product. Both were true on the KGM SsangYong corporate site, and both were reworked. Something we run inside Istanbul's own boundaries sits at a far smaller scale — the QR menu for Çatalca Merkez Kasap, a butcher in the Çatalca district, where the menu is split into sections, each section carries its own address, and a price change is a page edit instead of a reprint.

  • Find what carries the weight: a repeating catalog query moves behind a cache layer, and MySQL runs only when the data changes.
  • Give files an order, so images move into one naming and folder convention and which product uses which file is readable without opening the code.
  • Stay inside the framework a system already runs on when we take it over, so your own team can keep maintaining it.

Why Algoriel

  • Brochure and requests together

    The pages that present your business and the screens that handle incoming requests sit in one application, as they do at Diotek.

  • Listings built on the server

    Product and stock listings are assembled on the server rather than in the browser, as they are on Plastik ve Makina.

  • A second way in

    A calculator, a filter or a listing page has an address of its own, so people arrive there straight from search.

  • Every page has an address

    On Günlük Hava Durumu every date and location keeps a permanent address of its own.

What we build

Web Software
  • A web application of your own

    The parts working behind the site are built around your own way of operating: incoming requests, approvals, lists, the admin panel. At Diotek a pre-sale site survey and a post-installation service call were built as two separate flows.

  • Pages rendered on the server

    Lists and pages are assembled on the server and arrive ready to display, so nobody watches an empty screen fill itself in. Plastik ve Makina refreshes its results in place when a filter changes, rather than reloading the page.

  • Performance and findability

    Every page carries a permanent address, and headings and content come out in a form a search engine can read. Günlük Hava Durumu publishes each date and location breakdown at its own address.

  • Validation on the server

    Form validation is never left to the browser; it happens again on the server. A request that arrives outside working hours still lands in writing instead of in a phone note.

  • Catalogue and filters

    A product, listing or content catalogue follows the distinctions your own trade makes, and the filters answer questions buyers actually ask. On Plastik ve Makina new and second-hand machines share one list, with condition as a filter.

  • Life after launch

    The team that writes the application also keeps maintaining it. Adding a section, or absorbing a busier season, does not mean standing up a second system.

Work like this

Web Software · Case study

KGM SsangYong corporate site — storage cleanup and a cache layer on an inherited build

The site was already live; the job was not to rebuild it but to take weight off it. We moved catalog reads behind a Redis cache — the same query no longer hits MySQL on every page open — and put vehicle images into one naming and folder scheme. We stayed inside the existing Laravel stack and left the working sections alone, so the brand's own team can keep maintaining it.

Read the case study →

Working with Istanbul teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • You work remotely — how does that go on code you did not write?

    We work fully remotely, and the order never changes on a takeover: read the codebase first, then write down what we will touch and what stays as it is. That was the order the KGM SsangYong work followed.

  • Our pages open slowly. Where do you start?

    By finding where the weight sits. On the KGM SsangYong corporate site it was a catalog query repeating on every page open; the reads moved to a Redis cache layer, and MySQL now runs only when the data changes. We publish no speed figure, because we have none to publish — what we can describe is the change itself.

  • How soon can we start?

    Scope first, date second. On an inherited system a date only means something once the codebase has been read, so we do not open with an estimate.

  • Do you support the site after launch?

    Yes. Nothing new enters the stack of a system we take over, so maintenance stays within tools your team already runs. We maintain our own products too, which means we live with that cost rather than describe it.

Let's work out what your site needs behind it.