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

CMS for Sisli businesses

A card order is never placed for one person. When a title changes, one line changes and a whole print run waits behind it. A new run also only fixes the cards still in the drawer: the ones already handed out keep carrying the old number, and there is no collecting them back. Sisli runs on brand shopfronts around Nisantasi and Tesvikiye, and a card handed across a table is in circulation the same week. QRVizit is being built against that — update the record rather than reprint the card.

Get a quote Tell us about your project

CMS — Sisli

Sisli puts central trade and cosmetics retail on one stretch, and a first meeting there still starts at a table, with a card handed across it. The work closest to that is our own product, QRVizit, and we will not call it finished: it is still being built, with no live installation to point at. Nor does it reach everywhere. QRVizit replaces the printed card as a record, and a brand's product catalogue, a campaign page or a multi-brand shopfront is not work we can show. What we can show is where a change gets written. Laravel runs it, with Inertia serving the panel, React driving the interface and Tailwind shaping it; MySQL holds the records and Redis the cache. We keep no office; the work runs remotely.

  • A reprint only corrects the cards you still hold, whereas updating the record reaches the card sitting in someone else's drawer as well.
  • The admin panel and the page a visitor sees live in the same Laravel application, with Inertia feeding the React interface, so a content change never leaves a second service to update.
  • However many times the same record is scanned in a row, not every scan reaches the database: page content is cached in Redis while the records stay in MySQL.

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

QRVizit — a card already given away catches up when the record changes

Our own product, still under construction: not a client handover. The arrangement is this. The address a printed code points at is fixed once, and the page that address opens is edited from the panel. When a title or a phone number changes, no print order goes out — the record is updated, and cards handed over months earlier start showing the correct detail. That is the part a reprint cannot do. The panel and the visitor page sit in one Laravel application with Inertia feeding React, Redis absorbs the scan load, and the records stay in MySQL. What travels is where a change gets written.

Read the case study →

Working with Sisli 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 printed our cards last month. Does this arrangement mean printing them again?

    The point is not to produce another run but to take the reprint decision off the table. If there is no scannable code on the card, one print is needed; after that it is a record job. QRVizit is still being built, so we are not handing over a running installation.

  • The cards we handed out are in other people's hands. What changes for them?

    That is where the gain sits. A reprint fixes only the cards you kept, while the ones already given away keep carrying the old detail. Update the record and the card waiting in a drawer opens the same address, showing what is current.

  • Could the same panel run our brand catalogue and campaign pages?

    No, that is outside the scope. QRVizit is built around a person and a card record. A product catalogue, a campaign page or a multi-brand shopfront is separate work, and we have nothing to show there, so we promise nothing there.

  • Do you have an office near the Tesvikiye shopfronts in Sisli, and can we see QRVizit running?

    We keep no office and work fully remotely, and we do not claim a client in this district. The product is still under construction, so there is no live installation to demonstrate. What we describe is the arrangement itself.

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