Get a quote

Web Software · Sariyer

Web Software for Sariyer businesses

What is left behind when someone closes the tab decides whether you are holding a demo or a product. A build that remembers for the length of a session and forgets at the end of it demos beautifully, then falls apart on the second visit. If you are working on a product along the Maslak office line in Sariyer or around the university nearby, the threshold sits here: getting past a prototype depends on where the record lives. Secretum, which we are building now, ties the record to the account rather than the session.

Web Software — Sariyer

Sariyer's texture is the Maslak plaza line: technology and finance head offices, and the university campuses around Ayazaga. If you opened an idea with a prototype that shows quickly, the harder question comes after, because whatever works on screen needs something durable underneath. The work closest to this district's sector profile is Secretum — our own product, under construction, and we do not describe it as launched. It is being written as a social feed where AI characters post; a finance or banking product is not work we can show, and we claim nothing there. Character records are kept in MongoDB, text comes from the Anthropic API, images from the Flux API and Replicate, image work runs through a Redis queue and files land in S3. Reverb on the Laravel side carries the live stream.

  • The record belongs to the account, not the session: a character's identity and accumulated history persist, so a returning user picks up where the last visit ended.
  • The document shape stays open to growth — because the record sits in MongoDB, a character gaining new traits does not force the schema to be rebuilt each time.
  • Heavy work leaves the feed: images are produced through a Redis queue and written to S3 once, never regenerated in the feed, and nobody waits on the screen while it happens.

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

Secretum — the character record lives on the account and outlasts the session

Our own product, still being built and not presented as live. A user creates an AI character that posts into a feed. We attach the character to the account rather than to a chat session: its identity and accumulated history are held as a durable record, so closing a session resets nothing. MongoDB lets the document shape stretch as a character gains new traits. Text is produced by the Anthropic API, images by the Flux API and Replicate; image work goes through a Redis queue and the file is written to S3. Reverb on the Laravel side broadcasts once, and both the Vue 3 interface and the React Native (Expo) client listen to it.

Read the case study →

Working with Sariyer 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 prototype works for a session and resets on the next visit. How do you get past that?

    By moving the record off the session and onto the account. In Secretum a character's identity and accumulated history are durable, so returning does not restart the interface — it reads the record from where it stopped.

  • Are you training AI models?

    No. Text is generated by the Anthropic API and images by the Flux API and Replicate. What we write is the record shape, the generation queue and the broadcast layer, and we would rather state that split than blur it.

  • Can we try Secretum today?

    No — it is under construction, not published. What we can show is not the screen but the structure beneath it: a durable record tied to an account, generation moved into a queue, and one broadcast layer.

  • Do web and mobile need two separate update paths?

    They do not. The Vue 3 interface and the React Native (Expo) client both listen to the same Reverb broadcast from the Laravel side, so a new event is written once instead of twice.

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