EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

Enterprise & Commercial Software · Izmir

Enterprise & Commercial Software for Izmir businesses

Inside a plant room, or once a cold store door closes, the signal drops — and the person doing the work still has to finish the record there. On an app that treats a connection as a precondition, the job stays open and the office learns nothing until evening. For a service organisation in Izmir shopping for enterprise software, that threshold is where it has to hold. AlgoKlima was written against it: the record lands in a local queue on the phone first, and the app keeps working without waiting for a network.

Get a quote Tell us about your project

Enterprise & Commercial Software — Izmir

Around the Atatürk Organised Industrial Zone in Cigli, export-facing production is dense. When cooling and climate maintenance is handed to an outside crew, that crew covers several plants in a day and coverage cuts out in a different spot at each of them. The closest work we have to that pattern is AlgoKlima — our own product, whose upkeep we carry. The limit of the evidence is written down too: AlgoKlima was built for equipment servicing, and we have nothing to show on export files, quality certification or the tracking of a production line itself. What travels is the queue. The office panel runs on Laravel with Inertia, the field app on React Native (Expo), and both write to the same MySQL database, with Redis carrying reads.

  • A technician opens and closes a record with no coverage present, because it is written to a local queue on the phone before anything else.
  • When the connection returns the queue drains in the order records were created, and changes arriving from the field and the office merge onto one record through conflict resolution.
  • Warranty, maintenance and fault records hang under the device, so files for units at one address stay apart and history follows a unit that changes hands.

Why Algoriel

  • Many institutions, one system

    Vipkurum runs seven institutions on the same system while each one keeps its records to itself.

  • Adding one adds a boundary

    Each Vipkurum institution signs in at its own domain under its own brand, so adding one does not mean a second installation.

  • Each branch runs its own work

    A branch marks its own exam sheets, so one broken device does not stall every institution at once.

  • Each role, its own view

    Timetable, exams, students, parents, payments and reporting sit on one platform, and who can see what is settled up front.

What we build

Enterprise & Commercial Software

  • Each institution signs in through its own domain

    At Vipkurum, seven education institutions open under their own address and their own brand, and the name of the software never appears on a user's screen.

  • No reinstallation for a new institution

    Adding one more institution means writing a definition. No second copy of the system is stood up, and the maintenance stays in one place.

  • Office and field on the same record

    AlgoKlima's office panel and field app read and write the same record. A technician closes the job where there is no signal, and the entry reaches the office panel once the connection returns.

  • Operational and commercial records close together

    At AlgoCar the service record and the commercial record sit in the same system, so the cost of a job and its revenue are not reconciled across two programs.

  • One institution's data stays closed to the next

    Student, parent and payment records stay inside the boundary of the institution they belong to. That boundary is how the system is set up, not a view switched off on a screen.

  • One technical footing we can maintain for years

    Nothing goes into your system that the team maintaining it does not already know. AlgoKlima and AlgoCar are our own products, built on that same footing, and we work on it every day.

Work like this

Enterprise & Commercial Software · Case study

AlgoKlima — the record enters a local queue and drains once a connection returns

Our own product for air conditioning, boiler and appliance service firms; the upkeep is ours. The field app keeps working with no coverage: the technician opens and closes a record, and it is written to the phone's local queue first. Once a connection returns the queue drains in creation order, and a change made in the field that clashes with one made at the office merges onto one record through conflict resolution. Warranty and maintenance history hangs under the device record, so units at one address keep separate files. Laravel and Inertia carry the office panel, React Native (Expo) the field app, MySQL the core, Redis the cache.

Read the case study →

Working with Izmir 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

  • What does a technician do inside a plant with no signal?

    Carry on writing the record. The app does not treat a connection as a precondition: the form is closed on the phone and the record waits in the local queue. When the signal returns the queue drains in its own order, and nobody has to fill the same form again at the end of the day.

  • If the field and the office both touch one record, which one survives?

    Neither is dropped. The queue is processed in creation order and clashing changes pass through a resolution rule before merging onto a single record. Which field is owned by which side is agreed during scoping; it is a configuration question.

  • Our export volume is growing. Does the system carry that?

    A client's export ambition is their own business and we promise nothing there: customs, trade documentation and export files are outside what we can show. What AlgoKlima carries is the service record, and a larger fleet changes the number of records rather than their shape.

  • Who maintains this once you are done?

    AlgoKlima is a product we run ourselves, so its maintenance load is one we carry rather than describe. Your installation stays on the same toolset: nothing outside Laravel, MySQL and Redis is added, which leaves no separate toolset for an inheriting team to learn.

Enterprise & Commercial Software in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

How many institutions and branches should we plan your system around?

Get a quote or open the service