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

Enterprise & Commercial Software for Atasehir businesses

A buyer shopping for enterprise software in Atasehir is not always one company. There is a head office, a few consumer brands under it, branch lists behind each. The shape narrows everything to one question: inside such a roof, where does the boundary fall? The closest thing in our portfolio to that shape is Vipkurum, and it settles the first half: an institution that wants its own domain and brand surface gets a boundary of its own, and a branch sits as a layer inside that boundary. The split is drawn in the records rather than by a filter on a screen.

Get a quote Tell us about your project

Enterprise & Commercial Software — Atasehir

Atasehir is defined by an organisational shape rather than an industry vertical: head offices that decide, branches that run the work, several consumer names on one back office. Vipkurum was built for that shape, and there the boundary does two jobs. The first is reading: an institution sees its own record set, and a record belonging to the institution next door stays outside it. The second is distribution, and it is the one noticed late. Messaging, announcements and notifications draw their recipient list from the same boundary, so a notice written under one brand reaches that brand's parents only. Payment, invoicing and reporting live in the same codebase, yet an institution's financial record never crosses its own boundary. Scoping a roof like this answers two questions, not one: who reads which rows, and where a sent message lands.

  • A branch does not count as a separate institution: classes and timetables sit as a layer inside one, and the boundary is drawn where a separate domain and brand surface begin. In the product that boundary is called a tenant.
  • The boundary cuts distribution too. An announcement or notification builds its recipient list from the institution's own records, so it never lands on a neighbouring institution's parent.
  • A roof-wide report is not made by widening one institution's boundary. It is defined as a separate reading at roof level, with its scope agreed in advance.

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 — adding an institution: a domain, a brand, an empty record set

Seven institutions sit under one roof, among them dekaakademi.com, turkcefm.com and statuakademi.com.tr. Taking on another follows a known sequence: a domain is bound, a brand surface is defined, and the record set starts empty. The institution builds its own lessons, tests, questions and exams from its own panel instead of inheriting a neighbour's content. Classes, timetables and branches open as layers inside it. The codebase does not fork, so maintenance stays on one line and one fix reaches every institution at the same moment.

Read the case study →

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

  • Do our branches count as separate institutions?

    Not automatically. A branch is a layer inside an institution, carrying its own classes and timetables while reading from the same record set. A separate boundary is defined when a brand needs its own domain and public surface.

  • Can head office read a summary across every brand?

    It can, but not by stretching one institution's boundary over its neighbours. A reading is defined at roof level with its scope agreed beforehand, which stops a reporting request from becoming cross-institution access.

  • What does adding a new institution to the roof involve?

    A domain is bound, a brand surface is defined, and the record set starts empty. The codebase does not fork, so maintenance stays on one line. We work fully remotely; this step is a configuration decision.

  • Could an announcement land on the wrong institution?

    The recipient list comes from that institution's own records, so student, parent and teacher lists are never opened next door. A message written under one brand stays inside that boundary, and notifications follow the same rule.

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