One-person software studio, building since 2016
I design, build, host and support everything on this page. Each product has a case study that shows how it works, what went wrong on the way and what was decided.
Discord music botLive in 20,000+ servers
Plays from six music services, with 20+ audio filters and a dashboard for the queue and settings. Premium members can run up to three Mikos in one server.
Rhythm game for WindowsDemo out. Launches November 19
Four arrow lanes, 55 songs with four difficulties each, a 3D neon highway or a Classic view, and a built-in chart editor.
Twitch chat overlay editorLive
Game-style Twitch chat overlays: 82 looks to start from, hand-painted frames with your channel name on the plaque, and one link to paste into OBS.
Web app for field-service crewsIn development
A phone-first web app where a crew logs each stop of the day and sees estimated pay build up, and the office builds routes and schedules.
Browser arcade gameLive
A pixel-art beach brawler starring Kitty: waves of beachballs, upgrades on every level-up and a boss. Written in Python and compiled to WebAssembly.
11 World of Warcraft addons
Small interface tools for WoW Forever and Retail: aggro counts, dungeon timers, leveling routes, keybind backups and more. Written in plain Lua with no external libraries, tested outside the game, and each one has a full guide.
4 coloring books
Coloring books with kittens, dragons and spooky cats, in print on Amazon.
These are things I already do for my own products. Each one names what is included and where you can see it done.
01
Music, support, moderation and custom commands, with a web dashboard when the bot needs one.
02
Desktop games released on Steam, and browser games that open from a link. Design, code, store page and release.
03
Phone-first apps, dashboards, product sites and documentation. A framework when the app needs one, plain static HTML when it does not.
04
Agents that take over repeatable work under written rules, and assistants built into a product. A person approves anything that ships.
ChatSkins was built by a team of Codex agents that I directed.
05
The part after launch: hosting, proxies, process management, health checks and a status page.
Every product on this page is hosted on a VPS I run.
The same six steps on every project, mine or yours.
You tell me what it has to do, who uses it and where it has to run. I write back what is in, what is out and what I need from you.
On record: This site was built from a written brief.
The first version is small, and it runs where the finished one will run. Problems with hosting, sign-in or a third-party API show up in the first week, not the last.
On record: Every product here is live at its own address.
Each piece of work is written down before it is built, whether I build it or an agent does. Small tasks are easy to review and easy to undo.
On record: ChatSkins keeps one prompt file per task in its public repository.
Automated tests cover the logic. Then the build is checked where it will be used: in a browser, on a live Twitch chat, on a phone, against the game’s own API.
On record: RouteTimecard has 121 test files. Miko Rhythm has more than 100.
Releases go out with versioned assets and a check of what is actually live. Health endpoints and a status page say whether it is still working.
On record: Miko Radio publishes its status page.
I host and support what I build. Mail and Discord come to me, not a queue.
On record: Miko Radio has been live since 2023.
Nothing here is a mock-up. Each link goes to the running product, its public store page or its source.
Korivash is one self-taught developer who has been building things since 2016. Design, frontend, backend, deployment and the server underneath are all done in-house.
Everything here runs on one VPS I pay for. If something I built is useful to you, this is the easiest way to say so.
Tell me what it needs to do and where it has to run. I answer email myself.
