Projects

Here you’ll find a selection of personal and professional projects — tools I’ve built, ideas I’ve explored, and systems I’ve shaped along the way. Some were born from necessity. Others from curiosity. All of them reflect my approach to engineering: thoughtful, practical, and focused on clarity.

I don’t believe in building things just to build them. I believe in building things that matter — and sharing what I learn along the way.

Open Source Projects

OpenMiso

A developer-centric deployment platform inspired by Vercel and Heroku — but designed to be fully self-hosted, plugin-driven, and cloud-agnostic.

OpenMiso is my attempt to rebuild a tool that once existed — and was quietly killed. It’s a spiritual successor to HashiCorp Waypoint: a brilliant project that tried to simplify deployments without sacrificing control. Waypoint was ahead of its time — elegant, powerful, and full of potential.

Unfortunately, it was discontinued shortly after HashiCorp changed its open source licensing model in 2023. The project was archived, and its community faded away.

I couldn’t let it end there.

OpenMiso is my way of bringing those ideas back — but on different terms. From-scratch, open source (MIT), and deeply hackable.

One of my key goals is to preserve compatibility with the original CLI and manifest structure — so teams familiar with Waypoint can transition easily. At the same time, I’m simplifying the internal architecture: replacing the original plugin system with a cleaner, more idiomatic implementation, and gradually decomposing the monolith into a fully pluggable execution model.

I can’t wait for the day it can deploy itself.

After OpenTofu and OpenBao… it’s time for OpenMiso. 😄

Licensed under the MPL-2.0 License.

PlugKit

PlugKit is a lightweight plugin system built as the foundation for OpenMiso — but designed to be useful far beyond it.

It was created to solve the real-world pain points I encountered while working with HashiCorp’s go-plugin, which, while brilliantly conceived and battle-tested in tools like Terraform, Vault, and Vagrant, tends to be overly complex for smaller or more focused projects.

PlugKit takes a different approach. It aims to keep the philosophy of message-based plugin communication, but with less ceremony and fewer assumptions.

Instead of relying on protobuf definitions and gRPC codegen, PlugKit uses CBOR for lightweight, binary-safe message exchange — allowing developers to define their own payloads, including Protobuf, JSON, or custom formats. We don’t impose any specific serialization structure: you are free to speak whatever language your plugin understands.

In the upcoming v0.2 release, PlugKit will also introduce built-in support for bidirectional streaming of messages — a feature that was possible but cumbersome to implement in go-plugin, and is still not natively supported by most plugin frameworks including grpcplugin.

Our goal is to make streaming first-class — intuitive, fast, and reliable — without requiring boilerplate or deep protocol hacking.

This is a personal project and a bit of a love letter to clean protocol design. I built it for myself — but I’d love to see others use it too.

Try it. Break it. Hack it. Let me know what you think.

Closed Source Projects

Goldeneye

A custom dashboard wall system developed for Polkomtel — designed to go beyond what Grafana could offer at the time.

Goldeneye is a video-wall-style telemetry system displaying selected Grafana dashboards and custom visualizations across multiple tiled displays. It was built using Chromium Embedded Framework (CEF) and .NET to provide precise control over rendering, layout, and data integration.

The project was born out of real-world limitations in Grafana: certain data sources weren’t well supported, and some visualizations had to be custom-rendered or composed from multiple backend systems.

The result? A responsive, real-time telemetry display inspired by the iconic control room wall from GoldenEye — hence the name.

Yes, that GoldenEye — the first Bond film starring Pierce Brosnan, featuring a massive wall of screens in the Severnaya control center. It felt like the right metaphor for a system that keeps watch over a nationwide mobile infrastructure.

It’s robust, relatively easy to use, and still running today in Polkomtel’s operations environment.

Tech stack: .NET, Chromium Embedded Framework, custom APIs, dashboard integrations