
FloppyVPN
Full software of a simple commercial VPN service company. Frontend, backend, integrated apps.
Backend, desktop, web and the hardware in between.
Nine departments, one developer. Everything below is work I do myself — from the database schema to the cable in the ceiling.
Server-side applications, RESTful APIs and microservices. Database design across MySQL, PostgreSQL and SQLite.
Human-friendly native applications with WinForms and WPF. Clean interfaces for operators and power-users who prefer a proper window over a browser tab.
Full-stack web work in Blazor, ASP.NET Core and Razor Pages. Responsive frontends, real-time dashboards, landing pages and robust APIs.
I maintain and customise existing WordPress sites when required. For a new project, real code is the better answer — and I will say so.
IoT and embedded interfaces, hardware-software integration, custom firmware and protocols. Industrial control panels assembled on request.
Full IP video system design, installation and configuration — cameras, recorders, networking and cable runs.
Schema design, query optimisation, migrations, and the rescue of tables long thought lost. MySQL, PostgreSQL, SQLite.
Deployment, hardening, certificates and backups. From bare metal to containers, with monitoring that actually pages someone.
Real devices that bridge code and the physical world. Sensors, motors, relays, buttons and displays — prototypes and finished products that react to what is around them.
Shipped work, filtered by what it is made of. Some entries stay nameless — private commissions do not get a public link.

Full software of a simple commercial VPN service company. Frontend, backend, integrated apps.





Intermediary service for ordering clothing from China. Account system, admin panel, order creation and editing, invoicing and payment processing, notification integration with messenger, and delivery management.

No account managers, no hand-off between four departments.
You talk to the
person writing the code.
We work out what the thing actually has to do, and what it definitely does not. Honest estimate up front, including the parts that will hurt.
Data model, services, deployment target. Decisions get made early so they do not become expensive later.
Iterative delivery with something runnable at the end of each stage. You see progress.
Linux servers, certificates, backups and monitoring. Handover documentation, or ongoing maintenance if you prefer.
Describe the problem in whatever words you have. The technical translation is my job.
Tell me who's asking and the PDF is ready in seconds.