Get a quote

AI Consulting · Izmir

AI Consulting for Izmir businesses

If a conversation breaks off at midnight, software decides where it resumes in the morning. If you work from one of the export offices around Alsancak the condition may be familiar: the buyer sits in another time zone, the thread closes in the evening and opens again where it stopped. Put that way, AI consulting in Izmir stops being a question about which model to pick. It becomes a question about where what was produced is kept. In Secretum, the product we are building now, a character belongs to an account, not a chat session.

AI Consulting — Izmir

Izmir runs on export-facing manufacture and retail. If your own buyer sits in another country, the working conversation gets cut in two. Secretum is the work closest to that condition, but the frame comes first: it is our own product, still under construction, with no running installation to point at and no delivery date. Where it does not reach is plain as well. It is being written as a social feed, so we have nothing to show for drafting export quotations, translating catalogues or running buyer correspondence. The lasting record sits in MongoDB, the text comes from the Anthropic API, and Laravel takes the records.

  • A character's identity and the history it gathers are held as a lasting record tied to the account, and no session owns that record.
  • When somebody comes back days later the context is not rebuilt; the record is simply read from where it stopped.
  • There is no enterprise edition to install today: we are still building the product and we say so plainly.

Why Algoriel

  • The image does the reading

    Vipkurum reads optical form marks with OpenCV from the image of the sheet, not through the optics of a reader appliance.

  • Cropping apart from judgement

    Image processing decides where a question begins and ends; the language model only binds the answer to it. The two jobs never mix.

  • Model output lands in a record

    Vipkurum writes the answer key into the cropped question's own record instead of keeping it as a separate document.

  • A person has the last word

    At Tahlil.com the model drafts the reading and a doctor approves what reaches the patient; an unapproved reading never appears on screen.

What we build

AI Consulting
  • Where no model is needed

    Marks on an answer sheet are read from the form image itself; the threshold that decides whether a bubble counts as filled sits in the code, and no language model runs in that step.

  • Splitting the job in two

    Computer vision sets the question boundaries; a language model then ties each answer in the key to its question. Cropping accuracy never rests on a model's interpretation.

  • Removing the hardware step

    Marking stops depending on a reader device; when the form layout changes, we adjust the reading service in software instead of ordering new hardware or device-specific forms.

  • Turning existing material into a pool

    A booklet page is split into individual questions, the answer key is written onto each question's own record, and the questions already on hand become the pattern for new ones.

  • Tying the output to a person

    At Tahlil.com AI prepares the first reading, a specialist physician writes and approves the interpretation, and responsibility for the text that reaches the patient stays with the physician who signed it.

  • Queueing the generation

    In Secretum text and images come out of two separate generation paths; image generation is not instant, so that work goes onto a queue, and the finished file is stored once instead of being regenerated in the feed. Secretum is the product we are building now.

Work like this

AI Consulting · Case study

Secretum — the product we are building: history gathers on the account

Our own product, under construction right now; it was never handed to a client and we point at no running installation. Someone sets up an AI character of their own and that character posts into a feed. The decision the build turns on sits in storage: the character belongs to the account rather than to a chat session, and its identity and gathered history stay as a lasting record in MongoDB. Closing a session clears nothing; the character carries on from where it stopped. The Anthropic API writes the text and Laravel takes the records. The boundary: a consumer feed experiment, not a tool for correspondence or sales.

Read the case study →

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

  • Could we run our export correspondence this way?

    No. Secretum is a social feed and that is what we can show. What travels is the decision rather than the tool: keep the context on the account, not in the session.

  • Why cite an unfinished product as evidence?

    Because it is what we have. Our AI work is a short list and we state the status of each piece. Secretum is in development; describing it as finished would spoil the information you are deciding on.

  • Does a lasting record mean the model remembers everything?

    The record remembers, not the model. A character's identity and gathered history sit on our side, and the part of that record a request needs is passed in each time. Memory is a storage decision rather than a property of the model.

  • Our buyer works in another time zone. How does support run?

    We keep no office; remote is how the practice was set up from the start. Progress moves through written exchanges and records rather than depending on meeting in a room.

Let us look at which step needs a model and which one needs computer vision.