Developer · aviation · simulators · infrastructure
Vladimir Kolosov
I build software for flight-training teams, flight simulators, Discord and Telegram, the web — and the love of it.
Programming isn't my day job — it's where my curiosity goes. Nearly everything below started as a real problem for the people who keep flight simulators running — or as something I simply thought could work better — and ended up in production.
Selected work
Grouped by what belongs together, newest first inside each.
SimUptime
A private service for flight-training operations, and the tools wired into it.
-
Pilot-support bots
Internal Telegram tooling for two flight-training companies
Bots the pilot-instructors of both companies use every day. An internal staff product rather than a chat toy: roles and permissions, generated reports, careful handling of personal data, and a small HTTP API of its own — all running on infrastructure we host ourselves, with nothing third-party in the middle.
-
SimUptime Fleet
The portal that watches a fleet of simulators
Every simulator reports in on its own, and the portal turns that into one picture: live state, history you can zoom into, and uptime over time. Built to keep working when the network doesn't — a machine that loses the link back-fills everything it collected once it returns — and the browser never talks to anyone but us: the charts are drawn by hand rather than pulled from a library.
How it's built -
SimUptime Control Panel
A browser panel on every simulator
A self-contained Go binary that puts a simulator's routine operations behind a simple browser panel: tap a button on a tablet and the machine carries out a pre-defined action, safely and without touching a keyboard. The web interface is built right into the binary and installs as a PWA — bilingual, with a live status dashboard, and it's the same binary that feeds the fleet portal. Locked down by design: it only ever runs fixed, whitelisted actions, never anything arbitrary.
-
SimUptime
A one-screen landing page for a private service
The public face of SimUptime — bilingual (English / Russian), fully dark, built from scratch with no frameworks and no third-party requests. One full-screen scene with a subtle great-circle flight path drifting across it, self-hosted fonts, and a matching 404. Restrained by design: flight simulator support, a private service, and a way to get in touch — nothing more.
simuptime.com
Other work
-
Barbara Swan — Modeling Portfolio
My wife's site — private and secure by design
Designed, built and run end to end. The visible part is a fast, elegant portfolio — the part that matters is everything protecting it: hardened single sign-on, intrusion bans and rate-limiting, encrypted off-site backups, and careful handling of personal data.
barbaraswan.ru -
docker-backup
Backup and restore for Docker stacks
A suite of scripts that backs up any Docker compose stack to S3: it finds the projects itself, dumps the databases, and ships every archive to two independent providers with checksums and generational rotation. The other half is getting it back — restore from either store, and a job that proves the copies really are restorable. It's what keeps my own infrastructure safe.
-
Voxhail
Where it all began — a Discord bot
It started as a joke on the server where my friends and I hang out, and turned into a bot anyone can add. It notices when people join voice and hails them back, then keeps score: time in voice, streaks, achievements, a weekly digest. One in-chat panel sets it all up, notifications mirror to Telegram, and it speaks six languages.
voxhail.com
About
I'm Vladimir, and aviation runs through most of what I do — I've worked the apron as a ramp agent, my day job in IT is around a fleet of a dozen training simulators, and off the clock I'm often flying one at home. Code is the thread that ties it together: it started with a Discord bot that noticed friends joining voice and welcomed them back, and it kept going from both directions — the people around me kept having problems worth solving, and I kept wanting to build the better version of what we already had.
The habits are easier to show than to claim: backups I trust only because a job restores them and checks the result, a control panel that can run a fixed list of actions and nothing else, and the analytics on this page that stay off until you say yes. I'd rather understand a system to the bottom than glue something together and hope.
Let's talk
Got a problem that looks like one of these — or just want to compare notes on aviation and code? Either way, say hello.
- Email me@v-kolosov.ru
- Telegram @kolosovv