screenshot · 16:9
Agentics ID
One account, every product. OIDC, roles, tenants.
The foundation every client gets
One account.
Products that run.
AI for your business.
Agentics is a family of business systems that open with one ID. Each product runs on its own subdomain, the account is the same. When a ready-made product is not enough, we build an agent around your process.
id.agentics.uz Live wms.agentics.uz Live hrm.agentics.uz Beta wash.agentics.uz In development - ____.agentics.uz being added
- products already running
- 3
- years of building software
- 7
- the core stack
- Angular · .NET · PostgreSQL
- data on a server in Uzbekistan
- UZ
Products that open with one ID
Each is sold on its own and they work together. The list updates itself as products are added.
screenshot · 16:9
Agentics WMS
Warehouse, batches and cold chain control.
Manufacturing and distribution
screenshot · 16:9
screenshot · 16:9
Agentics Wash
Car wash till, staff share, customer base, Telegram.
Car wash chains
One account, every product
People sign in once and permissions are managed centrally. A new product means a new permission, not a new password.
- 01 Single sign-on (OIDC). A standard protocol, so it connects to outside systems too.
- 02 Roles and permissions. Who sees what is decided in one place.
- 03 Separated by company. Every client has its own tenant; data never mixes.
An agent for your process
When no ready-made product fits, we build around your process. Your data, your server.
A commissioned AI agent
- problem
- The process exists, but a person runs it by hand
- we build
- An agent that works on your data
- result
- The repetitive part runs itself; a person only approves
AI inside the system you already have
- problem
- The data sits in 1C or Excel, and nobody analyses it
- we build
- An agent over your API, on your own database
- result
- Ask a question, get an answer; the report writes itself
Telegram bot and OTP
- problem
- Talking to customers and staff is scattered across apps
- we build
- A bot for notifications, orders and confirmation codes
- result
- One channel, and every message is where you look for it
Computer vision
- problem
- Plates, goods and events are checked by eye
- we build
- A camera and a YOLO model, running on site
- result
- Recognition is automatic and the log writes itself
Uzbek speech (STT/TTS)
- problem
- Voice enquiries are typed up by hand
- we build
- Uzbek speech to text and back
- result
- A call or a voice note arrives as text
Analytics and a reporting agent
- problem
- The report comes once a week and is assembled by hand
- we build
- An agent on your database, asked in plain language
- result
- A finished report every day, and answers in seconds
Describe your process — you get an architecture and an estimate within two days.
Describe the processHow we work
- 01 1 week
Analysis
We watch the process where it happens, find the data sources and draw the boundary.
- 02 2–3 weeks
Prototype
A small working version on real data. The direction is confirmed here.
- 03 in phases
Development
Every phase ends with something that works; the next one starts after that.
- 04 ongoing
Deployment and support
On your server or ours. Monitoring, updates, training.
Case studies
Public sectorClient confidential
An agent that sorts incoming enquiries
Hundreds of enquiries a day were routed to departments by hand.
Angular.NETPostgreSQLDockerTelegram APIYOLOClaude / OpenAI API
Data stays on a server in Uzbekistan. It meets local law and never leaves the country.
On-premise option. The whole system can run inside your own infrastructure.
Source code is handed over. On commissioned projects the code can belong to the client.
Discuss a project
Describe your process in two or three sentences. You get an answer within one working day.