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

CMS · Beylikduzu

CMS for Beylikduzu businesses

Beylikduzu is thick with showrooms and sales floors, and where several brands trade under one roof each one needs its own door onto the street. On the content side the equivalent looks trivial and is not: if every brand enters from its own address, where is the boundary actually drawn? On Vipkurum we drew it in the schema rather than the interface, at the level of the domain, so what is read never crosses an institution's boundary.

Get a quote Tell us about your project

CMS — Beylikduzu

Beylikduzu has many sales floors, and brands often trade separately under one roof, each with its own team, its own list and its own address. Put them all behind one panel and the first campaign breaks it, because one brand's edit shows up on another brand's page. The portfolio work closest to how this district runs is Vipkurum. Where the overlap ends is worth marking: it was built for education institutions, and a screen on a sales floor or a product catalogue was never part of it — nor is there furniture or textile work we could point to. What travels is where the line is drawn. Laravel runs it, with React panels and a React Native (Expo) client; MySQL and MongoDB keep the records and Redis the cache.

  • Each institution enters from its own address and its records stay inside that institution's boundary, never surfacing on a neighbour's screen; the separation is not a filter setting.
  • The content layer hands the definition of a course, a test, a question and an exam to the institution itself, so a change of assessment type waits on no developer.
  • Adding a brand is a new definition in the system rather than a new installation, and announcements, messages and reports all come off that institution's own data.

Why Algoriel

  • Print becomes editable

    Çatalca Merkez Kasap moved a printed menu to a QR page, so a price change is an edit rather than a reprint.

  • Content gets an address

    Each menu section carries its own address, so a customer can link straight to the section they came for.

  • The institution authors

    Teachers on Vipkurum write their own lessons, tests and exams, so publishing does not wait on a developer.

  • Fixed code, editable page

    QRVizit fixes the printed address once; the page behind it stays editable. We are still building it.

What we build

CMS

  • Content modelling

    Which content types exist, and which fields each one carries, follows your own publishing work. At Vipkurum the assessment type is not hard-coded, so European and Turkish standards sit side by side on the same foundation.

  • The editorial interface

    The person writing and the visitor reading see the same information, with no second copy waiting to be synchronised. Keeping the admin panel and the published side in one application means the content is not held in two places.

  • Addresses and links

    Every page and every section carries a permanent address of its own, so a shared link always opens the same place. At Çatalca Merkez Kasap the menu is split into sections, and codes on different tables land on different points of the same page.

  • Access and permissions

    Who sees what, and who may change it, is defined together with the content type. At Vipkurum a teacher, a student, a parent and an administrator read the same lesson programme at their own level of permission.

  • An update is not a reprint

    When a price, a phone number or an address changes, the printed material stays as it is and the page is updated instead. Çatalca Merkez Kasap keeps its menu as text, so a price change never reaches the printer.

  • Repeat reads

    When the same page is opened again and again, it is served from a ready copy rather than rebuilt each time. QRVizit, still under development, opens a repeatedly scanned card that way.

Work like this

CMS · Case study

Vipkurum — seven institutions on one system, the boundary drawn at the domain

Seven education institutions share one system under their own domain and their own brand. The separation is not a visibility toggle in the interface; it lives in the schema. Each institution signs in at its own address, and student, guardian and payment records stay inside that boundary. The content layer hands over the definition of courses, tests, questions and exams, so different assessment standards sit on one infrastructure without a code change. Adding an institution is a definition in the system, not an installation. Scope is how an institution runs; a sales floor screen and a payment step are outside it.

Read the case study →

Working with Beylikduzu 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 carry several brands. Would they all sit behind one panel?

    The arrangement assumes the opposite. Each brand enters from its own address and sees its own data; what is shared is the system, not the screen. Maintenance stays in one place while the brands never read each other's records.

  • Could you not separate them with a filter in the interface?

    You could, and it would not hold. A filter is a display preference, and the moment it is forgotten or misconfigured a neighbour's record becomes visible. Keep the boundary in the schema and the separation no longer depends on a preference — it comes from where the record sits.

  • Vipkurum was written for education. What does it say to a sales floor in Beylikduzu?

    It was written for how an institution runs, and we do not restate that. A screen on the floor, a product catalogue and a payment step are not in it, and we have nothing to show on those. The one thing that carries is how the boundary is built — who enters from where, and where their record stays.

  • Does opening a new brand mean a fresh installation?

    It does not. A new brand opens as a definition inside the system rather than a second system, and its announcements, messages and reports come off that definition's own data. Nothing extra has to be kept alive alongside it.

CMS in other cities

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

Other services for this location

Let's talk about who will manage your content.

Get a quote or open the service