AI SYSTEMS ENGINEERINGASTANA · KAZAKHSTAN

AI for
your

work.

I build AI agents and document search. I connect them to your systems and run them on your servers.

From first integration to production operation.
Data, access and control stay inside your perimeter.

FROM TASK TO RESULTFICTIONAL EXAMPLE
TASK FROM AN EMPLOYEE

Look into the delayed order.

RequestOrderTerms
The agent cross-checks the dataPrepares a reply and a task in your work systems
TWO DRAFTS · THE DECISION IS YOURS

Reply and task are ready.

The warehouse moved the shipment to 21 September. Customer: the new date. Logistics: check the dispatch.

Reply to the customerTask for logistics
Under employee review · not sent yet

An illustration, not a finished product. Access and approvals are configured to your process.

FOUNDER IN PERSONAleksandr Tikhonov I design, build and support.

EMPLOYMENT EXPERIENCE · LAN E-LIBRARYLanGPT, AI-Snippets AI services for an electronic library.

IN-HOUSE DEVELOPMENTProtocore Agent platform with an open core · beta.

Systems. From practice.

AI services I work on at the Lan e-library, and my own Protocore platform. For each project: the task, my role and the result.

LanGPTLan e-library / RAG

From a question —
to an answer with sources.

The e-library’s materials become context for the model. The reader gets an answer with references.

  1. 01
    Access and queue

    The API checks permissions and limits. The request enters a priority queue.

    JWT · RabbitMQ
  2. 02
    Library search

    The RAG service finds materials and assembles context from source fragments.

    Source 01Source 02…
    Elasticsearch · context for the LLM
  3. 03
    Generation on an available model

    The load balancer routes the request to an LLM backend based on its load.

    LLM routing · fallback
  4. 04
    Answer stream and references

    The answer reaches the interface as it is generated; references lead back to the sources.

    SSE · source markers

Simplified backend diagram. Not a screenshot of the LanGPT interface.

task
An assistant for academic work: summarization, sections with citations, content checks against verified e-library sources without access to the external internet.
my role
Backend and operations: public API with JWT, rate limiting and SSE, a RAG service on Elasticsearch, an LLM backend load balancer with fallback, request moderation, monitoring, Kubernetes deployment.
result and status
Pilot results published by Lan on 17 April 2026: 20 universities, 6,500 users, more than 37,000 queries. Public source.

Founder’s employment experience, 2024 — present. The figures show the product’s scale, not personal contribution; the role can be confirmed by the employer on request.

More about the system
AI-SnippetsLan e-library / search
catalog search: “heat transfer equations in porous media”
snippet answer · sources [1][2]Heat transfer in a porous medium is described by the energy equation with an effective thermal conductivity; calculations use local thermal equilibrium models and two-temperature models [1][2].
Heat and Mass Transfer in Porous Mediatextbook · 2021
Fundamentals of Transfer Theorymonograph · 2019
Numerical Methods in Thermal Physicstextbook · 2020
A demonstration of the principle: texts and sources are placeholders. This is not the e-library interface.
task
A short snippet answer with source markers above the search results. The AI layer must not slow down or break search.
my role
The whole pipeline: cache → query classification and expansion → multi-source search → BM25 + RRF → generation on vLLM → quality gate; circuit breaker and graceful degradation; load testing and vLLM tuning.
result and status
Load test on the target GPU server: 13.2 hours, 55,200 requests, zero infrastructure errors; 87.3% of answers passed the quality gate; median latency 4.6 s against a 5 s target.

Per an internal report on a test of one server configuration. Reliability and quality were measured separately; the median does not mean the latency target was met for every request. The interactive example shows the behaviour when generation is off.

More about the system
Protocorein-house development
frontendsprotocore-chat · protocore-dashboard — chat and admin panel
supportingtool sandbox · embeddings · autonomous worker
enterpriseFastAPI · control plane · LLM routing · RBAC · access plans
core runtimeprotocore — contracts, orchestration loop, hooks, safety, observability · open core, MPL-2.0
deployHelm charts · environment profiles · CI/CD — release boundary
dependencies: frontends and supporting → enterprise → core
task
A self-hosted AI agent platform for organizations that cannot hand data to external SaaS.
my role
Founder / solo developer: core runtime, enterprise backend, sandbox, chat and admin UI, Helm deployment. Developed outside working hours under the anchor-inference organization.
result and status
Open core under MPL-2.0 (code and installation); the platform is in beta; deployment scope and licensing terms are discussed separately.

Core tests and checks are visible in the repository; the platform layer is closed and deployed at the client’s site.

More about the system

More: Search 2.0, Books Keywords Generator, Daedalus, swiftclf-tuna — all systems and experience.

When to bring in an AI engineer

I help build AI into an existing product or take a prototype to production. Here are problems we can start with.

taskengineering workfrom practice
Model answers are unreliable and can’t be verifiedA regression set on the client’s data, LLM-as-a-judge with human spot checks, a quality gate on the output; a run on every change to the model, prompt or index.AI-Snippets: 87.3% of answers passed the quality gate under loadinternal report, one server configuration
Knowledge is scattered and search misses what mattersCorpus preparation, hybrid BM25 + kNN search with RRF, reranking; the index stays inside the perimeter; retrieval quality is measured on an agreed set.LanGPT: RAG over verified sources without the external internetfounder’s experience, Lan e-library
There’s a prototype, but it isn’t built into the processesAn agent on a runtime with tool contracts, state between steps, confirmation of risky actions and a log; integration with the client’s systems.Protocore: open-core agent runtime, MPL-2.0in-house development, beta
Data can’t go to external servicesSelf-hosted inference on vLLM in the client’s Kubernetes, index and logs in the client’s infrastructure; external integrations and telemetry only per an agreed list.Protocore: deployment in the client’s infrastructurein-house development · beta
Too expensive or too slow under loadChoosing a model for the task and hardware, batching, quantization, context size; a load test under fixed conditions before rollout.AI-Snippets: 13.2 h, 55,200 requests, median 4.6 s against a 5 s targetreliability and quality were measured separately

What exactly you are buying

You can order an implementation, bring me in to develop an existing system, or discuss Protocore for your team.

01 / implementation

A system built for the task

From task analysis to handover into operation: architecture, implementation, deployment inside your perimeter, acceptance on an agreed set.

  • what I solveknowledge search, agent-driven automation, model hosting
  • what you getan integrated service with quality criteria, monitoring and documentation
  • how we workstages with written deliverables; the founder in person
02 / support

Development and support

For a system that already runs: audit, change plan, regression runs, model and index updates, incident analysis.

  • what I solvequality degradation, growing load, model changes
  • what you getquality reports and an improvement plan
  • how we workbusiness days, SLA in the contract
03 / platform · beta

Protocore for your team

My own engineering foundation: an open-core agent runtime under MPL-2.0 and a closed platform layer deployed at your site under licence.

  • what I solveyour team building agents on its own
  • what you geta platform with runtime, access control, sandbox and observability
  • how we workplatform licence; the core is free
About the Protocore architecture

The system doesn’t end at the model’s answer

Four stages. Each has a written deliverable and an acceptance criterion; the work continues after the model’s first answer.

Task analysisweek 1

We fix what to measure and how

Data, perimeter constraints, access requirements and quality criteria. Without them there is no way to tell whether things improved.

output: task description, architecture, estimate; written acceptance
Prototype with metricsmeasurable

A first version on your data

Retrieval and prompt variants are compared on a regression set, not on gut feeling.

output: prototype and a metrics table on an agreed set
Deployment inside the perimeteron-prem or cloud

vLLM and Kubernetes in your infrastructure

Integrations and telemetry per an agreed list; monitoring and an operations document.

output: the system in your cluster; scenario-based acceptance
Operation and evalsongoing

Production quality under observation

Regression checks on model or index changes, error and latency control, quality reports. The client’s team continues the work independently.

output: reports and an improvement plan; support scope per the contract

Who will work on the system

Design, implementation and handover into operation: the founder in person. No intermediaries between the problem statement and the code.

Aleksandr Tikhonov

AI Systems Engineer · founder

Since 2024 I have been responsible for the backend and infrastructure of the Lan e-library’s AI services — LanGPT, AI-Snippets, Search 2.0, Books Keywords Generator: architecture, development, integration, Kubernetes deployment, monitoring and production support. In parallel I develop Protocore, a self-hosted AI agent platform with an open core.

My focus is engineering production systems around LLMs, not training models: services, RAG and backend architecture, integrations, resilience, observability and operation under latency and cost constraints.

Standalone projectfrom task analysis to handover with documentation and acceptance
System developmentaudit, change plan, implementation, measuring the effect
Supportincidents on business days, updates, reports; SLA per the contract

IN-HOUSE DEVELOPMENT / ANCHOR INFERENCE

For the team.
For yourself.

Two products, different jobs. A platform for how a company works and a personal agent that works as a team.

01 / PLATFORM FOR TEAMS · BETA

protocore+

Agents do the work.
You stay in control.

Interfaces, tools and task execution around an open core. For integrating AI agents into a team’s processes.

Open core MPL-2.0
The platform is a proprietary layer, beta.

Open the platform
02 / PERSONAL AGENT · OPEN SOURCE

daedalus.

Works as a team.
Asks all at once.

A personal AI agent with its own window on macOS, Windows and Linux. It hands work to a team of agents, checks every command against a policy and comes to you only with what a person has to decide.

FILM · CORRIDOR H8▶ The film “The Task Board” 2:57

macOS · Windows · Linux
Open project MIT · your model and your key

Open Daedalus
LAB / PROTOCORE RESEARCH

What the agent remembers.
What it actually did.

Context, task completion and result verification. Papers with methodology, artifacts and the limits of their conclusions.

Explore the research

New orders are paused

All our capacity is on a current project right now, so we are temporarily not taking new orders. When we reopen, it will show here.

temporarily · not taking new orders

Contacts

Directly: hello@anchorinference.com or Telegram @notsoulmate

Contacts and order status

Contractor: Anchor Inference LLP, BIN 261040019769, Astana, Kazakhstan.

Orders are paused

We are temporarily not taking new orders: all our capacity is on a current project. The request form is switched off until we reopen.

Existing arrangements, contracts and company details: hello@anchorinference.com · Telegram @notsoulmate