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

Process Tracking · Sariyer

Process Tracking for Sariyer businesses

When one management team carries several brands at once, the first question in process tracking is whose process you are looking at. If you hold a roof like that around the Ayazaga campus edge in Sariyer, the question returns every term: each brand takes students in through its own door, while the records pile up in one place. Vipkurum answers at the domain level. Seven institutions run the same system under their own name, and one institution's process never lands on a neighbour's screen.

Get a quote Tell us about your project

Process Tracking — Sariyer

Sariyer's texture is the Maslak plaza line and the university campuses around Ayazaga, which gather course floors and academies around them. If one management team carries several brands, process tracking software for Sariyer does not follow a single flow; in Vipkurum seven ways of working run at once. The work closest to this district's institution profile is Vipkurum. The part that does not carry across: Vipkurum is an education platform, and following a technology office's own build process — releases, bug records, a task board — is not something we can show. Laravel sits underneath; MySQL and MongoDB hold the records, Redis carries the cache. The panel was built with React, the phone side with React Native (Expo). There is no building to visit on our side, and the work runs remotely.

  • Each institution opens from its own address and runs its process behind it, so a student, parent or payment row belonging to another one never appears on the same screen.
  • The process definition belongs to the institution: it builds its own lessons, tests and exams and names the assessment type itself, which is how European and Turkish criteria sit on one infrastructure.
  • A manager's report is produced from that institution's own records, and the list an announcement or a notification goes to is drawn inside the same boundary.

Why Algoriel

  • Keeps working offline

    The field app keeps recording with no connection, and the queue reaches the server in order once signal returns. That is how AlgoKlima runs.

  • Entry from QR and location

    Where no fixed terminal can be installed, entry and exit are logged from a QR code and a location reading, and entitlement is worked out from those readings.

  • Records land the same hour

    Jobs close in the field, so the office sees where each one stands without waiting for end of day.

  • Office and field read one source

    The office panel and the field app read the same information, so nobody keeps a spreadsheet alongside it.

What we build

Process Tracking

  • What the record attaches to

    Rather than mapping a process in the abstract, we decide what a record hangs on. On the construction system a row belongs to a person and a site at once, and the two are never separated. In AlgoRandevu we are building a structure where a booking can attach to a person, a room or a piece of equipment.

  • The entry that stays open

    Instead of a live dashboard, one rule: a matched check-in and check-out produce the hours, and a check-in with no scan out stays open. Whatever is stuck shows up as that gap.

  • Who was where, on the record

    Because a single row carries both the person and the site, totals separate by site. When one worker spends the month across two sites, those hours never fall into the same bucket.

  • What is left when the figure is disputed

    Because payroll is derived from matched pairs, the number argued over at month end has a time- and location-stamped record behind it. There is no parallel calculation sheet to reconcile against; the dispute happens over the record itself.

  • Records taken beyond coverage

    In AlgoKlima's service flow the chain does not break where the network does. Once the connection returns the waiting entries are processed in the order they were created, and an edit made in the field and one made in the office merge into a single record through conflict resolution.

  • Process rules kept out of the code

    Rules like the length of a step and the gap between consecutive ones belong in a product setting, not in the code. The aim is that changing one does not mean shipping a release, and that is what we are building into AlgoRandevu right now.

Work like this

Process Tracking · Case study

Vipkurum: the process definition sits with the institution, the boundary with the domain

Seven education institutions run one core under their own domain and brand; the separation is set at domain level, so one institution's records never open on another's screen. What matters here is that the way of working is not identical across them. Through the content management layer an institution builds its own lessons, tests, questions and exams and names the assessment type itself. That is how an institution working to European criteria and one working to Turkish criteria sit on the same infrastructure, with no separate release for either. Taking on one more institution is a definition, not an installation.

Read the case study →

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

  • We run three brands and each wants to be seen under its own name. How does that work on one system?

    The separation is set at the address, not by a filter added to a screen. Each institution opens from its own domain, the system knows which organisation it is in from that address, and it stays inside that institution's records. Seven institutions run this way in Vipkurum.

  • Our institutions do not assess the same way. Does each of them need its own release?

    No. The institution names its own assessment type, and the criterion is a definition in the content management layer rather than something buried in code. In Vipkurum an institution working to European criteria and one working to Turkish criteria sit on the same infrastructure.

  • We are a technology office. Could you track our own development process too?

    That is not something we can show, so we do not promise it. Vipkurum was written for how education institutions operate; release tracking, bug records and task boards fall outside that scope. Naming the limit first beats explaining it later.

  • Would you not come to our office near the campus and watch how the work runs?

    There is no building to come from on our side, and the team works remotely. Rather than watch a process we write it down first: which step is written into which record, and which boundary that record stays inside. That step comes before any screen.

Process Tracking in other cities

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

Other services for this location

What stands behind your month-end figure today?

Get a quote or open the service