Get a quote

Web Software · Fatih

Web Software for Fatih businesses

Around Tahtakale, where wholesale food and hardware trade sits street by street, a business card is still an object. It leaves your hand in batches and never comes back. Then a line gets a new number, a second depot opens, a title passes to someone else, and every card in circulation keeps stating the older version. Around Tahtakale and Eminonu print is still central to the trade, and that gap is where the problem begins. QRVizit, the product we are building right now, holds the address a code points to still and lets the page behind it move.

Web Software — Fatih

Fatih's texture is historic peninsula retail: wholesale food, hardware and guesthouses, all of them working alongside print such as menus, price boards, signage and cards. When what changes lives on paper rather than in a record, updating it means printing again. The work closest to this district's sector profile is QRVizit, our own product, and we are still building it rather than shipping it. It was written for business cards. A guesthouse booking ledger or a wholesaler's order flow is not something we have work to show for, so we do not promise it. The panel and the visitor page sit in one Laravel application: records in MySQL, page content cached in Redis, an interface delivered through Inertia and React.

  • The print run happens once. We fix the address the code points to, then edit the page behind it from the panel, so a changed number or title updates a record rather than a box of cards.
  • Reading the code installs nothing: the phone camera opens the page itself, and we build that page with Tailwind so it reads on a small screen without pinching.
  • Page content is cached in Redis, so a card scanned again and again does not send every read down to MySQL while the records stay in one place.

Why Algoriel

  • Brochure and requests together

    The pages that present your business and the screens that handle incoming requests sit in one application, as they do at Diotek.

  • Listings built on the server

    Product and stock listings are assembled on the server rather than in the browser, as they are on Plastik ve Makina.

  • A second way in

    A calculator, a filter or a listing page has an address of its own, so people arrive there straight from search.

  • Every page has an address

    On Günlük Hava Durumu every date and location keeps a permanent address of its own.

What we build

Web Software
  • A web application of your own

    The parts working behind the site are built around your own way of operating: incoming requests, approvals, lists, the admin panel. At Diotek a pre-sale site survey and a post-installation service call were built as two separate flows.

  • Pages rendered on the server

    Lists and pages are assembled on the server and arrive ready to display, so nobody watches an empty screen fill itself in. Plastik ve Makina refreshes its results in place when a filter changes, rather than reloading the page.

  • Performance and findability

    Every page carries a permanent address, and headings and content come out in a form a search engine can read. Günlük Hava Durumu publishes each date and location breakdown at its own address.

  • Validation on the server

    Form validation is never left to the browser; it happens again on the server. A request that arrives outside working hours still lands in writing instead of in a phone note.

  • Catalogue and filters

    A product, listing or content catalogue follows the distinctions your own trade makes, and the filters answer questions buyers actually ask. On Plastik ve Makina new and second-hand machines share one list, with condition as a filter.

  • Life after launch

    The team that writes the application also keeps maintaining it. Adding a section, or absorbing a busier season, does not mean standing up a second system.

Work like this

Web Software · Case study

QRVizit — the printed code stays fixed while the page behind it is edited

Our own product, under construction rather than finished, and we describe it that way. The address behind the QR code printed on a card is set once; the page it opens is edited from the panel as often as needed, while the card already in someone's wallet stays as it is. Whoever scans it downloads nothing — the camera opens the page directly. Panel and visitor page are gathered into a single Laravel application, with Inertia feeding a React interface, so no separate API layer exists to keep in step. Page content is cached in Redis and records live in MySQL. Ordering, payment and stock fall outside this scope.

Read the case study →

Working with Fatih 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 cards are already printed. Does this mean printing them again?

    Yes, once — the first run has to carry the code. What changes is everything after it: because the address is fixed, a new phone number, a new title or a second depot updates the record in the panel rather than the cards in circulation.

  • We trade wholesale and our product list moves constantly. Can this page replace a price list?

    No. What we describe is an introduction page; ordering, payment and stock are outside it. Publishing a live price list is separate work and not what QRVizit sets out to do, so we do not offer it here.

  • Could we start using QRVizit today?

    No. We are building it now and will not describe it as launched. What we can show today is not the product but the record shape behind it: one fixed address, a page that keeps changing.

  • Someone leaves the company. What happens to the page on their card?

    The page is managed from the panel and the record stays with the business. That person's page can be closed or rewritten with whoever takes the role; the cards already handed out carry the same code, so they open the current page.

Let's work out what your site needs behind it.