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

Enterprise & Commercial Software for Tuzla businesses

In the heavy manufacturing yards around Aydinli in Tuzla one shift closes and another crew sits down at the same work, so a job belongs to a queue that changes hands rather than to one person. When the record is tied to the session, the handover takes it away and the second crew asks the same questions again. Secretum, the product we are building right now, ties identity and accumulated history to the account instead, so the record picks up where it stopped.

Get a quote Tell us about your project

Enterprise & Commercial Software — Tuzla

Production in Tuzla is cut by shift rather than by daylight; around Orhanli and Aydinli the start and the finish of one job can fall to different crews. Enterprise software gets a continuity question here before a reporting one. The closest thing we have to that condition is our own product Secretum, which we will not call finished: it is in development, with no running installation to show. Where it does not overlap: Secretum is a social feed product where a user builds an AI character, and we have nothing to show on shipyard operations, shift planning or heavy manufacturing output. What we can show is what a record hangs on — the character sits in MongoDB as a document, and Reverb on the Laravel side carries the live layer.

  • We attach a character to the account rather than to a chat session, so its identity and accumulated history are kept as a lasting record and nothing resets when a session closes.
  • The character record sits in MongoDB as a document, so the structure stretches as new traits are added and we do not rebuild the schema each time.
  • One Reverb broadcast set up on the Laravel side is read by both the Vue 3 web interface and the React Native (Expo) client, so we write no second update path.

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

Secretum — in development: the record hangs on the account, not the session

This is our own product and we are building it now, so there is no running installation to show. A user builds an AI character of their own and that character posts into a feed. The arrangement: the character is attached to the account rather than to a chat session, and its identity and accumulated history are kept as a lasting record, so nothing disappears when a session closes and the character stands where it stopped. The record sits in MongoDB as a document and the structure stretches as traits are added. Anthropic API writes the text; Flux API and Replicate produce the image, queued through Redis and stored on S3.

Read the case study →

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

  • What happens to an open job record when a shift hands over?

    It depends on what the record hangs on. Hung on a session, it leaves with the handover. On Secretum we hang it on the account: identity and accumulated history persist, and the next session resumes from the same point. In heavy manufacturing that means the incoming crew does not start from nothing.

  • Can we see Secretum running?

    No. There is no running installation to show. We are building it now and we will not present it as finished. What we can discuss is the decision itself: what the record is attached to, how the document structure stretches, whether the broadcast travels on a single layer.

  • Do you have shipbuilding or maritime software for our yard work?

    We do not. Nothing in our portfolio was written for ships, yards or the maritime trade, and we will not present work we do not have. What we can talk about is the shape of the record. You bring the trade knowledge; we write down where each record is entered.

  • Would you not need to be on site to watch a shift handover?

    We hold no office, and the job runs remotely from start to finish. Instead of watching a handover, we work out together which fields have to be filled when a job changes hands, and which record those fields are written to.

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