Get a quote

Software Consulting · Umraniye

Software Consulting for Umraniye businesses

If adding a field means stopping the system, the field never gets added. Umraniye's fabric leans on the mechanical contracting and air conditioning service around Dudullu. If records are written until the end of the day, no quiet hour appears in which a table can be locked, and the new measurement taken on site ends up in a notes box where nothing can search it. So the first question we ask is not which product to buy but why the record cannot stretch. Secretum is what we are building against that limit.

Software Consulting — Umraniye

Mechanical contracting, air conditioning service and small manufacturing sit inside one another in Umraniye. If the record coming back from site wants one more field each season, the question looks like whether to install something new, while the pinch is in how the running system shapes its records. Closest to that pace is our own product, Secretum, still in development with no finished installation to show. Where it does not overlap is plain: Secretum is being built as a feed where AI characters people create post to each other, not a work order, maintenance plan or production tracker. What travels is the give in the record. The character is kept in MongoDB as a document, Laravel takes the records, and a Redis queue absorbs heavy work.

  • When every new field in an inherited system turns into a migration job, teams start typing the information into a notes box; shaping the record so it can stretch empties that box.
  • Heavy work goes to a queue: image generation moves through Redis, the file is written to S3, and the feed never renders it a second time.
  • The cost is written down too: the document enforces no field on its own, so we decide in the application layer which fields have to be there.

Why Algoriel

  • We read the code first

    We did not build the KGM SsangYong corporate site; we read the inherited codebase and left the parts that worked untouched.

  • Fix where the load sits

    The same catalogue query hit MySQL on every page open; that read moved to a Redis cache and nothing else was disturbed.

  • We stay inside your framework

    On the KGM SsangYong site the inherited Laravel, Tailwind and jQuery set was kept; the cache layer was the one addition to the stack.

  • We reconnect broken chains

    At Resterm the calculation sat in a sheet, the catalogue in a file, the quote somewhere third; selection now runs to cart, project, and customer.

  • Reading the code first

    We read the inherited codebase through, then name what moves and what stays untouched, one item at a time. The scope of the change comes out of that reading rather than a template.

  • Staying on the existing framework

    A library the maintaining team has never worked with would be a cost we left behind on our way out. KGM SsangYong's corporate site arrived with its framework and front-end libraries already chosen, and not one dependency was added to that set.

  • The limit of the change

    Only the slow places get opened; heavy spots are handled one at a time and the rest stays where it is. Where that limit falls is written down for you once the reading is done.

  • Tidying the file layout

    Scattered files move into a single naming and folder scheme. Which model uses which file becomes visible without reading code.

  • Taking weight off the reads

    The same query repeated for every visitor can be run once and shared from there. On KGM SsangYong's catalogue pages that query no longer runs until the data changes.

  • The decision taken before code

    Some decisions are made before the first line and are expensive to correct later. Resterm's software was built on the manufacturer's own product structure, because it was clear from the start that a general-purpose quoting tool would not carry it.

Work like this

Software Consulting · Case study

Secretum — being built now: the record stretches, stored ones stay where they are

Our own product, under construction now; no installation runs in the field yet. Someone builds their own AI character, which posts into a feed. Its identity and accumulated history hang on the account, not the session, so it carries on where it left off. Because the record is kept in MongoDB as a document, a character gaining a trait simply gains a field; no step is written to move stored ones into another shape. Anthropic API produces the text, Flux API and Replicate the image; the image job enters a Redis queue and the file lands on S3. The cost is plain: the document enforces nothing, so that check lives in the application layer.

Read the case study →

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

  • Can we add a field without taking the running system down?

    It depends on the shape of the record. Under a rigid schema every addition becomes a migration job, and that job does not fit inside a working day. Holding the record as a document removes the step: in Secretum a character gaining a trait simply gains a field, and stored ones stay where they are.

  • Information coming back from site ends up in a notes box. Why does that matter?

    A value sitting in a notes box cannot be searched, reported on or tied to a rule. The problem is not the person typing it but the field that could not be opened. Once the record can stretch, the measurement is written into a field of its own.

  • Can we buy Secretum and install it?

    No. The product is in development and we say so as it is. What consulting puts in front of you is not an installable package but how we shape the record and which job that decision removes.

  • Do you keep a place in the industrial area, or does a team come to us?

    Neither. We keep no office and the work runs remotely from start to finish. A visit would not change the answer either, because what needs looking at is the record rather than the floor. We begin by working out together which field belongs to which record, and every value now parked in a notes box gets a name in that pass.

Would you like us to read the system you already have?