Accounting and management systems
ERP, warehouses, documents, point of sale, analytics. Multi-user systems with roles and permissions, reporting, and integrations with external services: accounting packages, banks, marketplaces.
Information systems for business
Systems where AI agents do real work
I design and deliver accounting and management systems end to end: database and API, client applications, and AI agents built into the product. Rust and TypeScript in production, infrastructure on your own servers.
Services
Four parts that assemble into one working system.
AI agents inside the product
Agents that work with your data: import documents from PDFs, run chat threads on any entity in the system, build websites and reports. Sandboxed execution with permissions and tokens issued per step.
Integrations and the MCP protocol
Your internal tools become available to AI assistants through the Model Context Protocol. Access is scoped to each employee's permissions, and sensitive operations are off by default.
Infrastructure and support
Deployment on your own or rented servers: Docker, backups with point-in-time recovery, monitoring, mail, VPN, remote access. No lock-in to cloud platforms.
Systems in production
Real projects in daily use. Each one lists the task and what came out of it.
Molit ERP
Multi-tenant ERP for trade
- Task
- A trading company needs one place for documents, warehouses, pricing, point of sale and analytics, with per-employee permissions and synchronization with their existing inventory service.
- Solution
- Rust (Axum) server over PostgreSQL, MongoDB and ClickHouse; cross-platform clients in Dioxus and Flutter; Windows point of sale in Tauri. Separate update channels for the POS and the app.
- Result
- About 240k lines of code in production, OpenTelemetry observability, backups with point-in-time recovery. AI features run inside the system itself.
- Stack
Agent runtime
Sandboxed agent execution for a SaaS product
- Task
- Give agents access to ERP customer data so that a mistake or an attack on the agent cannot reach another tenant or the database.
- Solution
- Claude Code sessions in a rootless container with three isolation layers: the OS boundary, a separate Linux user per tenant, and ephemeral default-deny API tokens minted for every agent turn.
- Result
- Automatic PDF-to-document import, persistent AI chat threads on any entity, and a chat-driven website builder.
- Stack
Embedded MCP server
ERP tools for external AI assistants
- Task
- Employees want to work with the ERP through their own AI assistants, but access has to match their permissions in the system.
- Solution
- A Streamable HTTP MCP server built into the ERP API: any client (Claude Code, Claude Desktop) connects by URL under the user's own session. Tools are filtered by the employee's permission tree and token scopes.
- Result
- One connection address instead of separate integrations; direct database access is disabled by default.
- Stack
Relay
AI agent orchestration platform
- Task
- Run dozens of coding agents (Claude Code, Codex, Kimi) from one place without losing them on server restarts.
- Solution
- Rust + SvelteKit: one streaming runtime for all agents, a session daemon that keeps them alive across restarts, and MCP tools through which agents move kanban cards and spawn each other.
- Result
- Agents manage tasks, open terminals and message each other without an operator in the loop.
- Stack
The alpiyev.com platform
Self-hosted service infrastructure
- Task
- Remove the dependency on third-party SaaS for mail, passwords, code, remote access and VPN, keeping a single entry point and monitoring.
- Solution
- One server, rootless Docker, an edge nginx behind Cloudflare. Stalwart mail with a web client, Vaultwarden, GitLab with a container registry, RustDesk, sing-box VPN, Grafana + Prometheus + Tempo, and an MCP hub for mail, calendar, contacts and files.
- Result
- More than ten services on one host with a single access scheme and alerting.
- Stack
StroyRinok
Product storefront on top of the ERP
- Task
- Show the catalog and stock levels from the ERP to buyers on a website and in a mobile app without manual exports.
- Solution
- An Astro storefront and a Tauri mobile app that read data through the ERP API with a token of limited scope.
- Result
- The catalog updates together with the books, with no separate admin panel.
- Stack
Process
The order is fixed: each step builds on the result of the previous one.
Audit
We go through current processes, data and systems. The output is a list of what gets automated and what stays as it is.
Design
Data schema, roles and permissions, integration boundaries, where agents operate and what they are not allowed to do. Agreed before any code.
Development
Short iterations on real data. A test environment is available from the first weeks.
Rollout
Data migration, staff training, launch on your servers or ours. The old system is switched off only after a parallel run.
Support
Monitoring, backups, updates and changes on request. A contract with a fixed response time.
Technology
- Server
- Rust (Axum, Tokio, sqlx) · TypeScript · Python · gRPC · REST
- Data
- PostgreSQL · ClickHouse · MongoDB · SQLite · SurrealDB
- Clients
- SvelteKit · Astro · Dioxus · Flutter · Tauri
- AI
- Claude Code · MCP · Agent sandboxing · Playwright
- Operations
- Docker · nginx · Cloudflare · OpenTelemetry · Grafana
Contact
Describe the task in two paragraphs: the business, what hurts right now, which systems already exist. I reply within a day.
Based in Kazakhstan, working remotely with clients worldwide.