Eirlab.

AI at work, from hands-on practice: agents, products, models, hardware and live demos where you can see it for yourself.

Agents in daily work

As-built documentation agent

Holds the as-built documentation engineer’s position at a construction company: reviews site documents, checks completeness and prepares concealed-work certificates. Asks a person for missing information.

How it works

  • Text and tables PDF, DOCX and XLSX: a dedicated handler for each format.
  • Scans and drawings OCR, a vision model, DWG → DXF conversion.
  • Cross-checking Finding gaps and discrepancies across documents.

Sales assistant

Answers customers about products, services and company policies. Prices and stock come from internal sources, so answers never drift from what is in the warehouse. Enquiries turn into analytics: what people ask for and could not find. In messengers it understands voice messages and hands complex requests to an operator.

Products

app.charmonye.com

An AI visualisation and design-development engine for landscaping: a private plot, a residential courtyard, a neighbourhood, the grounds of a commercial property. Interiors run on the same engine with a different input. It grew inside a working landscape studio, which remains its first user and reviewer.

A photo or a plan goes in; a controllable result comes out: a visualisation, its refinement, object placement, a render from a plan and a “from photo A to photo B” document that says what to do, in what order and what to check on site.

How it works

  • Operations A queue, a worker, recovery after failure; every generation keeps its prompt version and snapshot.
  • Models Routing between providers with a fallback; 44 codified styles.
  • Credits Prepaid, idempotent billing, a history and artefacts for every operation.

FastAPI · Vue · PostgreSQL · Redis · Docker

dashboard.charmonye.com

A living map of AI tools for construction, landscaping and interiors: what exists for a task, whether it is alive or an abandoned demo, how people use it and what those who tried it say. Every conclusion links to a source; there are no rankings.

How it works

  • Scout Looks for tools that fit a task and reads their pages.
  • Judge and council The judge drops tools where AI is only a label; a council of models from different families gives the verdict. A person approves every card.
  • Showcase A static page reads one published JSON file: no database, no API, no server.

TypeScript · pi agent engine · Alpine.js · Playwright

Documents and search

Document processing

  • Accounting documents Bank statements → transactions and counterparties → categories → analytics and a dashboard.
  • Books and large archives PDFs, scans, DOCX and XLSX → Markdown with headings and page numbers. After a failure, processing resumes from the same page rather than the start of the archive.
  • Document images Before the model sees them: PDF to PNG, photo straightening, slide clean-up, inpainting.

PDF · DOCX · XLSX · DWG / DXF · OCR

Search you can check

A test question set separates retrieval failures from model errors. The chain: refine context → retrieve → rerank → model; every fragment keeps its page number, so an answer can be checked against the book.

Qdrant · Zvec · GraphRAG · multimodal RAG

When there is no need for an index

With only a few files, the agent reads them directly, without a vector store. That is how the assistant on alesyadesign.ru works.

Models and hardware

Where to run a model

The choice starts with data, workload and budget: what may go to an external service, what must stay inside, and who will operate the system.

  • Overseas cloud A quick start without buying equipment, when data may be transferred abroad.
  • In-house servers Data stays inside the company. Hardware needs purchasing, setup and maintenance.
  • Russian provider The same open models, data kept in the country, no server to buy. Working contacts with such providers are already in place.

Models

Qwen, Gemma, Llama, GLM, Phi and GPT-OSS are tested for speed, memory and quantisation loss. Qwen-VL and DeepSeek-OCR read drawings, scans and document photos.

Voice

Speech to text: Parakeet and GigaAM locally, Groq and Deepgram in the cloud. Tasks reach agents by voice.

GPU servers

Hands-on experience assembling and configuring servers on RTX 3050–5090 GPUs, including modified 48 GB RTX 4090s: hardware, OS, networking, remote access, firewall.

Serving: vLLM · llama.cpp · SGLang · Ollama · LM Studio · Open WebUI

Infrastructure and operations

Close to the data

An agent can live on the company’s own server: the model sits next to the data, and only what is explicitly allowed goes out.

Hosting

Vercel when the platform is enough, a dedicated VPS with nginx when control matters. Certificates, CDN, backups, link previews in messengers.

Monitoring

Metrics and failure alerts; external checks notice when a service stops answering from outside.

Servers and access

Physical machines and VPS: several domains on nginx, self-hosted RustDesk, hosts linked through Tailscale.

Docker · nginx · supervisor · pm2 · fail2ban · Prometheus · VictoriaMetrics · Alertmanager · Grafana · Termius · SOCKS5

Building with agents

Working environment

Task → architecture → BDD scenarios → code → verification. Claude Code and Codex are in daily use, each in its own role; Droid, OpenCode and cliproxy regularly.

  • One MCP server for every environment Task tracker, messengers, schedules. A task from a voice message lands in the morning digest, whichever agent picks it up.
  • Working library In its third year: hand-picked material from industry channels. A librarian agent files it by topic; other agents take rules and context from it before a task.

Claude Code · Codex · Droid · OpenCode · cliproxy · Antigravity · Grok · herdr · Orca

Tools have to earn their place

Giving one task to different models exposes problems in both the result and the instruction. The rtk router brought no savings on real workflows and was dropped. A custom orchestrator compared Codex, GLM, Sonnet, Haiku, MiniMax and Kimi on the same task; the experiment is complete, and daily work uses existing tools.

Open roles and own environments

Librarian, architect and developer roles; a folder template where an agent runs a project from files and rules rather than scattered chats. Hermes and OpenClaw are deployed and adapted to the work.

Images and video

Generation on a local server

When source material cannot leave, generation stays on a local server. The practice covers ComfyUI, FLUX and Qwen-Image.

Video

Clips, promos and social media material: generated with Seedance, Kling and Runway, then edited and scored. For example, vertical clips made from still AI images: the camera flies over a site plan, a person walks up to a finished house.

Carousels and infographics

The material and key points are checked first, then comes the layout. HTML templates and Python turn it into carousels, reports, dashboards and PDFs.

Websites and automation

Websites

  • alesyadesign.ru A studio site with an embedded AI assistant.
  • ostalyk.ru A design bureau: a single-screen home page and work from AI visuals to production layouts.
  • charmonye.com English and Arabic editions, RTL layout.
  • abm-ai.ru A bilingual site on Next.js.
  • React + Vite Festival landing pages, an estimate calculator that reads photos and PDFs; bookings run on QloApps.

Astro · React islands · Tailwind · Framer Motion · Playwright

Bots and automation

A video link → an audio track, with large files split into parts. A channel monitor catches keywords and forwards messages to the right group. Parsers, change notifications, scheduled jobs.

Telethon · yt-dlp · ffmpeg · cron · supervisor

Open projects, knowledge, events

AI Day

The Green Lecture Hall at the Gardens and People festival, Moscow, August 2026: concept, programme, organisation. Each talk was one specific case, taken apart in detail.

Contact