Services
From a focused website to software used in day-to-day operations.
A project may need only design and frontend work, or it may also require an API, database, bot and server delivery. The boundary and deliverable for each part are written down before work starts.
Product strategy & design
Before screens are designed, I define who uses the system, what data enters it and what the outcome needs to be. The result is a page map, core flows, first-release priorities and a reviewable prototype.
This phase does not end with a vague promise of a better experience. It states where users enter, which decisions they make, what data is created and what each screen is responsible for.
- Scope & requirements
- Information architecture
- UI/UX design
- Interactive prototypes
Websites & frontend
I build corporate websites, catalogues, commerce and admin interfaces with React or Next.js. Mobile behaviour, RTL/LTR, accessibility, SEO and performance are part of the initial design; motion and WebGL are used only when they explain something useful.
The deliverable includes reusable components, indexable routes, explicit loading and error states, and a production build ready for a VPS.
- React, Next.js & TypeScript
- RTL/LTR responsive systems
- Motion, SVG & WebGL
- Technical SEO & structured data
- Image and Core Web Vitals optimisation
- Forms and admin integration
Backend, API & data
I implement APIs, authentication, permissions, files, notifications and data models as explicit NestJS or FastAPI modules. PostgreSQL and Prisma work also covers migrations, indexes, backups and upgrade paths.
Before launch, invalid input, external-service failure, retry behaviour and event logging are defined so the system is not limited to ideal scenarios.
- NestJS & FastAPI
- PostgreSQL, Prisma & migrations
- JWT, sessions & permissions
- Redis, queues & jobs
- File uploads & notifications
- Swagger, tests & logs
Automation, bots & integrations
I build Telegram bots, Mini Apps, webhooks and integrations to remove duplicate data entry and repetitive work. Each workflow records its input, decision, action and outcome so failures stay visible and retries remain controlled.
Each automation defines a manual fallback, idempotency and logs so replaying an event does not create duplicate orders or messages.
- Telegram bots & Mini Apps
- Webhooks & API integration
- Payments, orders & alerts
- Queues, schedules & retries
- CRM, forms & internal systems
- Execution-status dashboards
Network, server & infrastructure
For local or overseas VPS delivery, the path from DNS to service is documented: Linux, Docker Compose, Nginx, TLS, firewalling, SSH, VPN and container-network separation. The database stays private, and backup and restore are tested before handoff.
Deployment files, environment templates, health checks and recovery commands are delivered so the server remains understandable beyond its original builder.
- Ubuntu & SSH hardening
- Docker Compose & private networks
- Nginx, DNS & TLS
- Firewall, VPN & port restriction
- PostgreSQL backup & restore
- Monitoring & event logs
Delivery, observability & optimisation
Launch is not the end of the work. I make application and Nginx logs, container health, resource use, frontend errors, endpoint status and response times visible. Releases use reproducible builds, controlled migrations and a rollback path.
After handoff, service ownership, log locations, update steps and incident actions are written down explicitly.
- CI/CD & versioning
- Health checks & uptime
- Central logs & error tracking
- Core Web Vitals & profiling
- Scheduled backups & rollback
- Documentation & maintenance plan
Technology