A closer look at the work
Start with an area that matters to you. Each project opens into its context, implementation and tools.
01OnlihubTechnical ownership of a commerce platformDetails
I took technical ownership of a growing platform connecting suppliers, products, marketplaces and fulfillment.
- Scope of work
- Lead Developer · architecture, implementation and delivery
From developer to technical owner
I joined the startup working alongside an experienced lead. When they left, I took responsibility for the architecture, database and backend, coordinated a small cross-functional team and guided the product through implementation, support and further development. Discussions with the CEO connected business ideas to technical feasibility and delivery decisions.
One model across different channels
The original platform was designed for a broader multichannel scenario: a product from one source could be published into another channel. I worked with Amazon, Walmart, eBay, TikTok Shop, Shopify and warehouse integrations, reconciling products, external identifiers, real and virtual warehouses, stock, orders and tracking. That original scope helped give rise to MySellerHub as the products evolved.
02BOS / Business Operations SystemA business operations platform, starting with mortgagesDetails
I designed and developed a Python platform for document-based business processes, starting with mortgages: configurable documents, multi-step forms, calculations, access rules and compensation records.
- Scope of work
- Business modelling and system architecture
Organizations and access
The mortgage process sits within a model of organizations, departments, memberships and roles. Permissions combine an allowed action with a scope and conditions on the data. This lets document access follow a person’s responsibilities in the organization.
Documents and forms with state
Document types define typed fields, dictionaries and parent–child relationships. Multi-step forms support nested and repeating inputs, save answers and create or link documents on completion. Submissions can include an expected version so a stale edit returns a conflict instead of silently replacing newer answers.
03MCP HubAgent orchestration, project knowledge and reusable experienceDetails
I built a service where agents find tools and project knowledge, work across connected systems and retain useful methods for later tasks.
- Scope of work
- Agent infrastructure and integration architecture
Find an operation, then load its schema
Tool discovery returns compact matches with argument hints, risk information and a schema reference checked at invocation. The agent requests the exact schema for a selected operation, then invokes it by name. This keeps the full integration catalog outside the prompt while preserving a direct path from intent to the current tool contract.
Local embeddings and hybrid retrieval
Project knowledge combines FTS5 with local SentenceTransformer embeddings. A streamed vector scan retains the best fragment IDs before loading their content, and content hashes avoid embedding unchanged text. Reusable methods have a separate retrieval path: semantic and lexical selection followed by an optional local CrossEncoder that assesses relevance to the task.
04Amazon Data / TrendsLarge-scale Amazon scraping and trend analysisDetails
I designed and built an Amazon data service that scanned categories across the marketplace, excluding books, and used Elasticsearch bulk processing to identify trends.
- Scope of work
- Data acquisition and processing architecture
Historical category-wide scope
The project scanned Amazon categories across the catalog, with books deliberately excluded. Its historical workload was on the order of millions of listings. That breadth made acquisition, normalization and storage design one connected problem: category data had to become a consistent dataset that could be analysed in batches.
Acquisition under external constraints
The parsers had to account for blocking, multiple accounts, proxies and failed requests. Parallel processing, throttling and retries made these conditions part of the acquisition design. Normalization gave downstream indexing and analysis a consistent representation despite differences in the collected source data.
05MySellerHubA shared model across independent commerce channelsDetails
I designed a backend model for products, channel listings, orders and warehouses, with inventory updates and fulfillment connected across external platforms.
- Scope of work
- Multichannel architecture and integrations
Sales channel and supplier
Shopify can be a sales channel receiving products and sending customer orders, or a supplier providing a catalog and fulfilling purchase orders. These roles use separate workflows around a shared product and listing model. Supplier orders carry a local reference used to look for an existing external order before creating another.
Stock can change during an update
Each stock target has a desired quantity and version. After sending an update, the worker checks whether that version is still current. If stock changed in the meantime, the item stays pending for another attempt. Buffer and stock-cap rules adjust the target before it is sent to the channel.
06Liqsale / Daily SnipesFrom supplier spreadsheets to a marketplaceDetails
I built a pipeline that turns fragmented liquidation offers into structured, searchable product listings.
- Scope of work
- Product architecture and data processing
07Unity MCP EfficientA smaller tool interface with access to the full operation catalogDetails
I built a compatibility layer that lets agents discover Unity operations without loading every tool schema into context.
- Scope of work
- Facade design and implementation
08Onlihub CatalogDifferent data paths for different workloadsDetails
I designed and implemented a dedicated Onlihub catalog service with a Rust primary path, Python fallback, Redis caching and Elasticsearch.
- Scope of work
- Architecture and implementation of the catalog service
Dedicated service, explicit data paths
The marketplace catalog became a dedicated service with its own serving architecture. Rust handled the primary fast path, with a Python fallback alongside it. I was responsible for both the architecture and its implementation, separating the catalog workload from the broader commerce application.
Cache, search and transactions have different jobs
Redis cached data for repeated reads, while Elasticsearch provided the search/read model and PostgreSQL retained transactional responsibilities. This separated how catalog data was retrieved from how business state was stored. Bulk operations and heavy-query optimization complemented that division of responsibilities.
09Manufacturing EngineeringThe physical process behind the softwareDetails
My engineering foundation comes from designing parts, machining operations and the processes that bring products into production.
- Scope of work
- Manufacturing engineering and CAD/CAM
10ERP / 1CTranslating company operations into an accounting modelDetails
I built and supported 1C solutions for Ukrainian companies, working directly with customers on accounting, production planning, material consumption and logistics.
- Scope of work
- Business analysis and application development
Understand the company before configuring the system
I worked directly with customers to understand their technological and administrative processes, including projects built from the ground up. That meant discussing how materials, documents, stock and money actually moved before configuring accounting and integrations. The customer’s operational model shaped the software model.
Production, materials and spending plans
The work included production planning, material norms and consumption, stock movements, costs, payroll and spending plans. My manufacturing background helped connect the figures in 1C to the operations creating them. Reports and complex queries made that operational information usable for planning and control.
11Financial SystemsPayments, documents and data integrityDetails
In Onlihub and Liqsale, I built subscriptions, one-time payment flows and transaction models connected to statements, recalculations and business documents.
- Scope of work
- Cross-project financial modelling and integrations
Payments within the commerce workflow
My work in Onlihub and Liqsale included subscriptions, one-time payments, carts, checkout and status synchronization. Stripe and Wise integrations sat within the application’s financial workflow, connecting payment events to the customer’s order or subscription and the relevant transaction records.
A transaction model behind the statements
I worked on transaction types and categories, calculations, recalculations and statements, including PDF output. These records describe how financial operations relate to application state and documents. The model supports tracing the figures displayed to users back to the transactions and movements that produced them.
12ZipurchMaking commerce activity visible on a mapDetails
I worked on connecting order activity, product information and geographic context in a commerce map.
- Scope of work
- Order-data integration and geospatial workflows
13Meeting-to-ActionsFrom spoken decisions to structured workDetails
I worked on a workflow that transforms meeting audio into decisions, action items and tasks in Teamwork through MCP.
- Scope of work
- Speech and agent workflow integration
14Local AI / Lightweight MLChoosing a model that fits the actual taskDetails
I explore local models and lightweight inference for speech, documents, retrieval and practical automation.
- Scope of work
- Applied research and workflow prototypes
15TON TanksTelegram game: server-side battles and game systemsDetails
I helped shape, build and launch a Telegram game. Its backend handles turn-based PvP/PvE battles, tank abilities, rentals, crafting and recorded results; game assets are linked to wallets and NFT state.
- Scope of work
- Product lead, backend and game systems
The battle loop
A server-side battle coordinates PvP and PvE turns. Tank state includes health, armor, speed, abilities, effects, cooldowns and action points. The loop chooses the next turn, applies actions and damage, then sends available actions and state changes to clients over WebSocket.
Ownership, rentals and crafting
Tank access distinguishes an owner from a renter and accounts for cooldowns and rental limits. Crafting checks the input tanks and their ownership, then records a crafting document and the resulting game tank. Wallet links and NFT state are part of the asset model.
16Modular Vehicles / UnityPhysics, modular machines and procedural worldsDetails
I am building and experimenting with modular vehicles, damage, tracked physics and procedural environments in Unity.
- Scope of work
- Independent game systems development
17Blender / 3DFrom hard-surface models to game-ready assetsDetails
I use Blender to build and prepare hard-surface models, materials and textures for game environments.
- Scope of work
- Independent modelling and asset preparation
18Engine Sim Unity AudioPhysical simulation as a source of game audioDetails
I worked on automated generation of engine audio banks for Unity from a physical engine simulator.
- Scope of work
- Independent audio tooling
19Crypto Trading TerminalMarket data, strategies and execution in one toolDetails
I built a trading terminal combining market data, charting, custom strategies, backtesting and live exchange execution.
- Scope of work
- Independent application development