Our criteria change often. Do we come back to you each time?

No. The assessment type lives in a record the institution writes, not in code. Defining a new criterion is work done from the management screen and waits on no release from us.

Does moving the rule into data make it boundless later?

The boundary is not removed, it moves. The data model decides which fields can be defined; the institution writes its own criterion inside that model. What is opened up is the content, not the structure.

Vipkurum is an education platform and we make moulds.

We say plainly where the evidence stops: the platform was built for education, and we have nothing to show on production scheduling or bench utilisation. What carries across is the decision itself — whether a rule belongs in code or in data.

What happens if we add a second brand under the same roof?

It becomes a tenant definition rather than a new installation. Because the boundary is drawn at domain level, that brand's records do not open to its neighbour. We keep no office in Ikitelli; the team works fully remotely.

System Architecture · Basaksehir

System Architecture for Basaksehir businesses

Mould and machine shops are dense along the Ikitelli line in Basaksehir. If the list of what counts as acceptable hangs on paper beside the bench, changing the bench changes the list, and the foreman is the one who writes the new version. Move that job into software and the real question is not the screen but the pen: who writes the list from now on. On Vipkurum the pen went to the institution, so an assessment type is a record it writes rather than a branch in our code.

Get a quote Tell us about your project

System Architecture — Basaksehir

If your acceptance criteria shift from job to job and bench to bench, what software has to carry is not a ready-made question bank; the question is who holds the right to define. The work closest to this district's sector profile is Vipkurum. Where it does not overlap comes first: the platform was built for education, and we have nothing to show on operator competence, production scheduling or bench utilisation. What travels is the layer the rule sits in. A content management layer puts the criterion on the data side, not in code. Below it sits Laravel, with MySQL and MongoDB holding records, Redis the cache, React the panels and a React Native (Expo) app.

An institution builds its own lessons, tests, questions and exams in the content management layer, so an assessment type exists as a record it wrote rather than a branch in the code.
A changed criterion does not wait on a release from us: European and Turkish standards sit side by side on the same infrastructure without a separate installation.
The tenant boundary is drawn at domain level, so one institution's records never open to its neighbour and taking on another institution is a tenant definition, not a new installation.

Why Algoriel

The parts read one source

At Tahlil.com the site, the admin panel and the mobile app read the same information instead of behaving as three systems.
Where each job is solved comes first

Which layer handles which job is decided before code, because work that has to move later is expensive to move.
The summary recomputes itself

As the Günlük Hava Durumu archive grows, the climate summary recomputes from it; nobody maintains a monthly table by hand.
One rule for file layout

On the KGM SsangYong site, where a file is written and under what name now follows one rule the upload code obeys.

Where the data divides

When several institutions share one system, each enters through its own domain and student, guardian and payment records stay inside that institution's boundary. This arrangement is what the term multi-tenant describes.
What a record attaches to

Whether service history is written against a person, an address or a device is settled before the schema exists. Reversing that later means re-attaching everything already recorded.
Permission held in the data model

A teacher, a guardian and an institution administrator reach the same timetable record at their own level of access. Permission is part of how the record is defined, not a view switched off on a screen.
Splitting the read path

Which screens are served from a held copy and which go to the database is settled before the first record exists. On Vipkurum a frequently opened screen comes from the copy, and only a read with no copy reaches the database.
Interfaces on a single system

Tahlil.com hangs three interfaces off one system: the patient site, the physician panel and the mobile app read the same record, and no second data model is written per interface.
Storage laid out on day one

The naming and folder scheme files will live under is fixed at the start; a layout imposed afterwards turns into a migration.

Work like this

System Architecture · Case study

Vipkurum — the institution defines an assessment type as a record it writes

Seven education institutions run the same software under their own domains and brands. What the architecture settles is where the rule lives: a content management layer lets an institution build its own lessons, tests and exams, and define the assessment type itself. That is why European and Turkish standards sit on the same infrastructure without a separate installation, and why a new criterion waits on nobody. The tenant boundary is drawn at domain level, so student, guardian and payment records stay inside it. React panels and a React Native (Expo) app sit on one Laravel install; MySQL and MongoDB hold records, Redis the cache.

Read the case study →

Working with Basaksehir 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 criteria change often. Do we come back to you each time?

No. The assessment type lives in a record the institution writes, not in code. Defining a new criterion is work done from the management screen and waits on no release from us.
Does moving the rule into data make it boundless later?

The boundary is not removed, it moves. The data model decides which fields can be defined; the institution writes its own criterion inside that model. What is opened up is the content, not the structure.
Vipkurum is an education platform and we make moulds.

We say plainly where the evidence stops: the platform was built for education, and we have nothing to show on production scheduling or bench utilisation. What carries across is the decision itself — whether a rule belongs in code or in data.
What happens if we add a second brand under the same roof?

It becomes a tenant definition rather than a new installation. Because the boundary is drawn at domain level, that brand's records do not open to its neighbour. We keep no office in Ikitelli; the team works fully remotely.

System Architecture in other cities

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

Other services for this location

Let us settle where your data divides before any code is written.

Get a quote or open the service

System Architecture for Basaksehir businesses

System Architecture — Basaksehir

Why Algoriel

The parts read one source

Where each job is solved comes first

The summary recomputes itself

One rule for file layout

What we build

Where the data divides

What a record attaches to

Permission held in the data model

Splitting the read path

Interfaces on a single system

Storage laid out on day one

Work like this

Vipkurum — the institution defines an assessment type as a record it writes

Working with Basaksehir teams, remotely

Frequently asked

Our criteria change often. Do we come back to you each time?

Does moving the rule into data make it boundless later?

Vipkurum is an education platform and we make moulds.

What happens if we add a second brand under the same roof?

System Architecture in other cities

Ankara

Istanbul

Izmir

Let us settle where your data divides before any code is written.

System Architecture for Basaksehir businesses

System Architecture — Basaksehir

Why Algoriel

The parts read one source

Where each job is solved comes first

The summary recomputes itself

One rule for file layout

What we build

Where the data divides

What a record attaches to

Permission held in the data model

Splitting the read path

Interfaces on a single system

Storage laid out on day one

Work like this

Vipkurum — the institution defines an assessment type as a record it writes

Working with Basaksehir teams, remotely

Frequently asked

Our criteria change often. Do we come back to you each time?

Does moving the rule into data make it boundless later?

Vipkurum is an education platform and we make moulds.

What happens if we add a second brand under the same roof?

System Architecture in other cities

Ankara →

Istanbul →

Izmir →

Let us settle where your data divides before any code is written.

Ankara

Istanbul

Izmir