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

Enterprise & Commercial Software for Fatih businesses

A site in Fatih does not have to be an empty plot. It is the inside of a standing building: a floor of a han in Suleymaniye, hotel rooms in Kumkapi, a shop refit on the Zeyrek slope. The job runs for weeks, so fitting a reader to a doorway means taking it down later, and one crew can move between several addresses in a week. That is why the attendance system puts no device on the door: the record attaches to the location of the scan, not to a fixed point.

Get a quote Tell us about your project

Enterprise & Commercial Software — Fatih

Trade on Fatih's historic peninsula still runs over counters and shop windows, with wholesale food, hardware and small hotels sitting side by side. Refit and renovation work runs inside that same fabric: not one fixed plant but changing addresses. The work closest to that condition is the construction workforce attendance system. The limit deserves stating plainly: it was written for construction sites, and we have nothing to show for a hotel's front desk roster or a wholesaler's counter timesheet. What carries over is the shape of the record — who, at which location, for how long. The field app runs on the worker's phone in React Native (Expo), Laravel takes the records and MySQL holds them.

  • The QR code says who scanned and the location says which site they stood on, so a site is never picked from a list and both facts land in one entry record.
  • Duration comes out of a matched entry and exit pair, and an entry whose exit was never scanned stays open as an incomplete record instead of closing itself.
  • Payment due is not kept in a second calculation table but produced from those pairs, with the same worker's hours at different addresses adding up separately.

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

Construction attendance — nothing to dismantle on site, the hour carries its location

A site is temporary, so a turnstile is hardware you later take down; we put none on the door. Entry and exit come from a QR scan on the worker's own phone, and location verification decides the site, so its name is never chosen by hand. Duration comes from a matched pair, and an entry left open stands as an incomplete record. Payment due is produced from those pairs rather than a second calculation table, and the same worker's hours at different sites add up separately. React Native (Expo) on the phone, Laravel taking the records, MySQL holding them.

Read the case study →

Working with Fatih 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 site is a two-week floor refit. Installing a device there makes no sense.

    We do not install one. The scan happens on the worker's own phone and location verification decides the site. When the job ends there is nothing to dismantle, and the next address needs no new installation.

  • The same crew works several addresses in a week. Do the hours get mixed up?

    They do not, because the record carries the person and the location together. One worker's hours split by address across the same week, and which hour belongs to which site is settled by the record itself rather than by interpretation afterwards.

  • Will we still have to type payment due into a table?

    No, because there is no second table. Payment due is produced from matched entry and exit pairs. Keeping a separate calculation table is exactly what makes the two sides disagree at month end.

  • Enterprise software should also cover accounting and purchasing.

    This work does not cover them. What it describes is narrow: how the time somebody spent at a location becomes a record, and how payment due is produced from it. A hotel's room inventory or a wholesaler's order flow is not something we can show.

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