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

Enterprise & Commercial Software for Umraniye businesses

A mechanical contractor or an air conditioning service firm around IMES can run a site in two pieces: marketing pages built by one team, and a separate tool collecting requests. Two panels, two logins, two backups. Changing a paragraph and adding a request field land on different desks. So the enterprise software question in Umraniye is not which theme to install. It is which application a request should first land in. Diotek carries no such split.

Get a quote Tell us about your project

Enterprise & Commercial Software — Umraniye

Around IMES and Cakmak in Umraniye a machine shop, a mechanical contractor and a service firm work on the same street. If the corporate pages come from one team and the request box from another, maintenance goes to two addresses. The work closest to this district's texture is Diotek. Where it does not overlap: it was written for a firm selling air conditioning and ventilation, and we have nothing to show on production planning, stock movement or a manufacturing work order. What carries across is where the application's edge falls — content and request records sit on one MySQL schema, Inertia handles page transitions on the client, and routing and form validation stay in Laravel. One fix reaches both the public page and the request screen from a single maintenance line.

  • Marketing pages and request screens live in one application, so nobody goes to one panel for content and a second tool for the request form.
  • Because the request record and the page content sit on one schema, no reconciliation step between two systems is ever created.
  • Maintenance stays on one line: a single fix reaches the public page and the request screen at the same moment, with no second release calendar to keep.

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

Diotek — marketing pages and the request flow in one Laravel application

A firm selling air conditioning and ventilation has two jobs on its site: describing the product and capturing the request. Diotek does not split them across systems; both sit in one Laravel application. Inertia handles page transitions on the client while routing and form validation stay in Laravel, and the request record sits on the same MySQL schema as the content. Corporate pages and request screens come off one Tailwind scale, and maintenance stays on a single line, so one fix reaches both at the same moment. The scope is stated too: production planning, stock movement and manufacturing work orders sit outside this work.

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

  • Our corporate site is one thing and our request form lives in another tool. What does merging them buy us?

    It brings maintenance onto one line. Two tools mean two panels, two logins and two backups, and adding one field touches both sides. On Diotek the page and the request sit in one application, with the record and the content on the same schema.

  • If request records and site content share one place, can a content edit break the request flow?

    It does not, because what is shared is the application, not the fields. A content row and a request row sit in different tables on the same MySQL schema. The sharing happens in maintenance and routing, not inside the record.

  • Our site is already live. Can we move to this arrangement without a rewrite?

    Scoping comes first: which pages move across, which request fields become records, which old links are kept. On Diotek keeping the marketing side and the request side in one application was a design decision, and the same decision can be taken in stages on a live site.

  • Would you not need to come to IMES and see the process?

    We keep no office and nobody travels to a workshop; the work runs entirely remotely. We draw the line between page and request by listing together which field is written to which table, rather than by observing a floor.

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