Systems trusted with
money and load.
Payment platforms, distributed systems, DevOps and AI — from architecture design to battle-tested production.
Three directions. One responsibility for the whole system.
Not "just another developer". I own design, code, and support as a single responsibility — no "that's not my problem".
Payment & Fintech Systems
SBP and QR payment acceptance, multi-bank connections, 54-FZ fiscal compliance — no lost or duplicate payments.
Payments that don't lose money under load.
Distributed Systems & DevOps
Microservices, Kubernetes and CI/CD, queues and event-driven design, monitoring and fault tolerance at every layer.
Systems you can observe and control.
AI Engineering
Neural networks into products: chatbots and agents, auto-content moderation, local models for privacy.
AI where it saves hours and money — not just hype.
Systems shipped to production.
Not pet projects — real production systems. Clients are under NDA, so no logos, but the metrics and stack are real. Click a project to expand.
Payment core for transit fare collection: charges, refunds, fiscalization — no losses under peak load.
Utility payment acceptance: personal accounts, meter readings, provider accruals, registers and receipts — via website, terminals, and Telegram bot.
ERP from scratch: warehouse, production, payroll, marketplaces — one system instead of a zoo of Excel sheets and 1C hacks.
Multi-regional learning platform: data isolation by region, mobile app, 152-FZ personal data compliance.
Listings, real-time chat, and search across multiple countries: AI moderation, geo-search, 10k+ concurrent users.
Content generation service: subscriptions and credits, task queues, multiple AI providers.
Orchestrator for autonomous agents: parallel execution, per-user isolation, multi-client support.
Full system stack — from payment core to cluster.
What I own on a team.
Not analysis only, not code only. I own the chain: requirements, architecture, implementation, production.
Payments and billing
Acquiring, SBP and QR, payment splitting, idempotency, reconciliation against bank registries, fiscal compliance. A domain where a mistake costs money.
Infrastructure and production
Docker and Kubernetes, CI/CD, Nginx and Caddy, Prometheus and Grafana with alerts, Proxmox with backups. I don't wait for a dedicated engineer to ship.
Requirements and architecture
Business interviews, specs, domain model, API contracts, non-functional requirements with numbers and a way to verify them. The team gets a document, not a retelling.
Team and process
Decomposition, tasks with acceptance criteria, code review, onboarding, hiring involvement. Teams of up to 5 people, two stacks at once.
Albert Ryabov, system analyst
and solution architect.
I've been writing code since I was 13 — my first project was a game server with a forum and website. Ten years professionally: designing and shipping complex products to production — payment platforms, manufacturing ERP, multi-tenant SaaS, AI services. I build the whole system: from the database and architecture to servers and production support.
Open to full-time roles: remote, full employment.
Open to offers — I'll reply within a day.
Resume, a walkthrough of any case study, and answers to technical questions — on request. Reach me on Telegram or by email.