Open Source

Tools built from problems I wanted to solve properly

I publish libraries and self-hosted products that come from real application and infrastructure work. Everything here is free, installable today, and maintained by me.

github.com/golovanov-dev · MIT-style licensing · Self-hosted by design

traceloom · install
# PHP
composer require golovanov/traceloom


# JavaScript / Node
npm install @rgolovanov/traceloom


# Go
go get github.com/golovanov-dev/traceloom-go

One event format and the same API in PHP, JavaScript and Go.


Featured repositories

Three repositories, all running in production

This site runs on Weft, traces with Traceloom and alerts through AlertLoop. None of them started as an open-source project: each began as something I needed and could not find in a form I trusted.

Open Source · Self-hosted

AlertLoop

Released

A self-hosted event and notification center for software teams.

Problem
Important incidents and business events disappear across logs, inboxes and disconnected channels.
Result
AlertLoop ingests events, routes notifications to email, Telegram and webhooks, and keeps failures recoverable with retries, dead-letter processing and replay.
Stack
Go · SQLite or PostgreSQL · OpenAPI / Swagger · embedded admin console.
Status
Community edition v0.1.0 released and self-hostable today. Pro and Enterprise editions are planned, not built.

Open Source · Developer Tool

Traceloom

Released

Structured JSONL event timelines, grouped by trace_id, without a heavy framework.

Problem
Plain logs lose the context that connects one request to everything it touched.
Result
Traceloom writes structured events to a JSONL timeline grouped by trace, so a single execution reads as one story instead of scattered lines.
Languages
PHP v0.4.0 · JavaScript / Node v0.1.0 · Go v0.1.0. One shared event format.
Status
All three libraries released. The event format is the contract between them.

Open Source · PHP Engine

Weft

Released

A lightweight PHP 8.4 engine for quickly launching simple, content-first websites.

Problem
Every small site re-solves the same layer: clean URLs, locale prefixes, a correct head section, sitemap, spam-resistant forms.
Result
A convention-driven core where a page file is the whole route, with SEO, optional i18n, caching, tracing and form protection out of the box. Deliberately no ORM, DI container or admin panel.
Stack
PHP ≥ 8.4 · Composer golovanov/weft · deps: firebase/php-jwt, golovanov/traceloom · MIT.
Status
v0.1.1 alpha released 2026-07-22, with a 160-test PHPUnit suite and CI from the first tag. Pre-1.0 the API may change. This site runs on Weft in production.

Why open source

Publishing the code is part of the engineering

Open source is not only a distribution model. It is a way to document engineering decisions, expose quality to public review and create reusable solutions instead of solving the same problem repeatedly.

Roman Golovanov

There is a second reason, and it is more practical. A self-hosted tool asks a team to run someone else's code next to their incidents and their data. That trust is not something I can claim in a marketing sentence: it has to be readable. If AlertLoop is going to receive your production events, you should be able to see exactly what it does with them.

Public code also changes how I write it. Decisions that would survive unexamined inside a private repository do not survive a README that has to explain them.

Contribution

Found a bug, a missing use case or a design issue?

Open an issue or start a discussion. A well-described problem is as useful to me as a pull request, often more: it tells me what the tool is missing before I choose how to fix it.

Read the code before you read anything else I wrote.

Every claim on this site is easier to check on GitHub than to argue about here. Start with any of the repositories and judge from there.