Confession time. For over a decade this site ran on Drupal 7 and PHP 5.6 on a legacy server, untouched since roughly 2021. For someone who spent years of his life in the Drupal ecosystem (speaking at DrupalCons, building government platforms, winning agency awards with it), there is something poetic about being the last person to migrate off it.
What it is now
The site you are reading is fully static: React and Vite, plain CSS, no database, no PHP, no admin interface to patch. The 24 legacy posts and their media were extracted from the old Drupal database, cleaned, and compiled into JSON that ships with the site. It is served by nginx from our own Hetzner infrastructure, the same self-hosted setup that runs a growing share of our products.
A static site cannot be hacked through a login form, has no plugins to update, and loads in milliseconds. For a personal blog that gets updated a few times a year, a CMS was always the wrong trade. It just took me fifteen years to admit it.
How it was rebuilt
This is the part I actually want to write about. The migration was done almost entirely by AI agents: one wrote and ran the extraction script against the legacy MySQL database over SSH, one rewrote the old file paths and cleaned the markup, one built the new front end, and one researched and drafted the backfill posts that now fill the seven-year gap in this blog's archive, working from our internal documents and the public record, with me reviewing everything before it went live.
I have written about what an AI-native company looks like from the inside. This site is a small, complete example. The work that would have been a weekend of manual migration drudgery was a supervised afternoon.
The archive stays
All the old posts are still here, back to the Drupal Government Days and the startup guides for Kyiv, Lviv, Kharkiv and Sofia. Some of them aged strangely, all of them are honest snapshots. A blog that only shows your current self is a brochure. The archive is the proof that the current chapter, building AI-native systems and backing the founders who do the same, is a continuation and not a rebrand.
The writing habit is officially back. The next posts will keep documenting the machinery: the agents, the infrastructure, and what it is like to run a venture portfolio this way.