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 · Istanbul

Enterprise & Commercial Software for Istanbul businesses

A group shopping for an enterprise software company in Istanbul is not always one company. It is two or three consumer brands, a run of branches, and record tables that have never met. The closest match in our portfolio is Vipkurum, where 7 institutions open at their own addresses while every record is kept in one shared system. Bringing another institution under that roof does not mean raising a second installation.

Get a quote Tell us about your project

Enterprise & Commercial Software — Istanbul

Enterprise scale arrives here through brand count rather than headcount: holdings with several consumer names, retail chains, dealer networks, institution groups that share a back office but not a logo. The size of the city adds a second distance: the people doing the work are scattered across it while the panel that records it sits elsewhere. Two portfolio pieces answer that shape. On Vipkurum the brand surface belongs to the institution and the record set is shared: lessons, exams, classes, branches, payments and invoices sit in one shared record set, and an institution reads only its own rows. AlgoKlima's mobile app keeps taking records without looking for a connection, then syncs once one is back.

  • Each institution's boundary is drawn in the record layer — an institution opens at its own address, and the rows it reads stop at its own boundary.
  • The field and the office write into one system: in AlgoKlima a form is saved with no connection and synced when one returns, and in AlgoCar service, maintenance, stock and accounting stay in one flow.
  • The stack does not grow with the institution count — Laravel, MySQL, Redis and Inertia stay as they are, with React Native (Expo) for the phone app.

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

Vipkurum — 7 institutions, separate domains and names, one shared system

There are 7 institutions under the roof: egitakademi.com, ozdilakademi.com, mergenkampus.com and the rest. Each opens at its own address, each shows its own name, and one shared system turns underneath. Shared is the system; separate is the record an institution may read — a student, a payment or an invoice line never surfaces next door. Content belongs to the institution too: a teacher builds a lesson, a test, a question and an exam from the panel. Timetables, classes, branches and reporting travel through the same flow.

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

  • Our group runs several brands. Does each one need a system of its own?

    No. Vipkurum settles it with one shared system and a brand surface per institution. Each opens at its own address, its records are held in that system, and the institution next door cannot reach them. A new brand joins the same system rather than raising a second installation.

  • You work remotely and our branches are in Istanbul. How does that run?

    We have no office and work fully remotely, so the branch count lengthens the scoping work rather than changing how we work. We map where each record starts — at a branch, at head office, or out on a job — then talk about dates.

  • What happens to a record when the crew on site has no signal?

    It still gets written. AlgoKlima's app does not wait for a connection: the technician closes the form, the record sits on the device, and it syncs when a connection returns.

  • Who maintains the system once you are finished?

    AlgoKlima and AlgoCar are our own products and we keep maintaining them, so that bill is one we pay rather than describe. What we build for you takes on nothing from outside the tools we already use, which keeps the codebase readable for whoever inherits it.

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