11/17/2026 updated


100 % available
Ruby on Rails Developer & System Administrator
Tallinn, Estonia
Worldwide
MA in unrelated fieldBusiness DevelopmentBusiness Workflow AnalysisPostgreSQLLinux AdministrationRuby On RailsAnsibleRubyStakeholder CommunicationsDocker SwarmDockerCi Server
From 2013 to 2017 I led system operations at a PCI DSS regulated fintech. Since then I have built,
taken over and operated Rails applications for clients, alongside my own hosting services WellHost and WellPress.
I prefer plain, conventional Rails, upgrade step by step and start every engagement with a written review. As I run the servers myself, deploys, background jobs and backups are part of every change.
I enjoy communicating and developing ideas to real business problems directly with stakeholders. I provide external insights and a objective second opinion to your business pains.
Experience
Professional experience10+ years
Freelancer since2017
Languages
GermanNative speakerEnglishFluent
Project history
The non-profit ran its core process by hand in spreadsheets and email,
with a WordPress plugin managing students, groups and timetables. Double
entries and errors cost the team 16 hours a week, and nobody had a
reliable overview of what the software could do.
I worked out the requirements directly with the stakeholders: short
sessions, written specifications and small releases they could try out
early. I built the application as a conventional Rails monolith. I also
set up hosting, CI and monitoring, so the client had one contact from the
first conversation to operation.
Live after 12 weeks, with 2 people using it daily. Manual work dropped by
two thirds.
The application was in production, but database queries got slower with
every competition. Framework upgrades had been applied, but syntax and
code style drifted further and further apart. There were no functional
tests, and the framework was tightly entangled with the operating system.
I started with an in-depth review: reading the code and the
infrastructure, then a written report with the risks ranked by severity.
Before changing anything, I covered the business-critical paths with
tests. I then completed the Ruby and Rails upgrades, replacing deprecated
and broken syntax, and swapped custom workarounds for Rails conventions
along the way. Deploys now run through a CI pipeline with staging and
rollback, and backups have a restore procedure that has actually been
rehearsed.
The application is back on a supported version (Rails 7 → 8.1), and I
resolved almost all N+1 queries. Deploys take 4 minutes from git instead
of 30 minutes by hand. The client kept its application instead of paying
for a rewrite estimated at €45,000.
Small companies ran their applications without operations staff: hand-built servers, manual deploys, no separate staging, and backups nobody had ever restored.
A failed server or a bad deploy meant days of downtime and possibly lost data.
I built a standardised container platform on Docker Swarm, with CapRover as management layer and servers set up by Ansible. Each client gets
staging and production separated at infrastructure level, with Backing Services running outside the application containers. Deploys run
from git through CI (Woodpecker, GitHub Actions, GitLab CI) with rollback.
Hourly encrypted off-site backups are restored in regular drills, and TLS,
monitoring and weekly updates are part of the service.
At most one hour of data can be lost, and restores are proven rather than
assumed. 10 applications (i.e. Rails, Symfony, Django, Wiki.js, GitLab, Plausible) run at 99.95% availability. Clients pay from €50 a
month instead of a multiple for dedicated OPS personal.