Skip to content
MOITOITECH
EET--:--:--
SUN--:--

Independent product engineering practice

Systems that meet the real world.

I design and ship complete operational products — business model, software, infrastructure and the physical signal layer. Three decades of production experience provide the quality gate for AI-assisted development.

MoiToi reduces the distance between what happens in the real world and what the system knows. A berth sensor verifies occupancy. A fleet unit verifies location. A booking state machine replaces phone-and-spreadsheet ambiguity. A modernised commerce stack preserves years of business knowledge.

Live pilot

hara.mervare.app

Hara harbour, Gulf of Finland. A live berth-booking pilot designed for hardware-verified availability.


How I work

One operable product, not a stack of handoffs.

Most teams split the business model, the software, the infrastructure and the hardware across four groups that never quite meet. I hold the whole line.

I start with the operation, not the interface. Before a screen exists I map how the business actually runs — who does what, where money changes hands, what breaks at 2am — and design the system around that reality rather than around a template.

AI carries much of the implementation velocity. I stay responsible for architecture, constraints and judgement: the decisions that determine whether a system survives contact with real users and real money. Thirty years of running production systems is the quality gate on everything the tooling accelerates.

I work across the boundary most product teams divide up — business model, software, infrastructure and, when the product needs it, the physical signal layer. The result is one product you can operate, not a set of handoffs between people who each own a slice.

Operating depth

Production infrastructure since 1995 — Linux, databases, distributed systems, observability.

Business judgement

EBS BA completed alongside senior engineering and live ventures.

End-to-end range

Payments and interfaces through MQTT, ESP32 and production operations.

Trust over novelty

A long-term Zoovet relationship: modernisation without stopping the business.

Shipping velocity

MerVare v1: 5 days, 206 commits across product, state, payments and hardware.

Working stack

Product
TypeScript · Next.js (App Router) · React · Tailwind · Supabase / Postgres · Stripe Connect · Vercel
Languages
Python · Go · bash
Infrastructure
Docker · Kubernetes · Terraform · Ansible · ArgoCD · Jenkins · AWS
Data
Distributed SQL · MySQL · Postgres
Observability
Prometheus · Grafana · VictoriaMetrics
Hardware
MQTT / EMQX · ESP32 · Victron Venus OS · NMEA
Machine interfaces
MCP · OpenAPI · llms.txt

Selected systems

Four operations, four working systems.

Each one starts from a real operation, a defined user and a route to revenue. Status is stated honestly — a pilot is a pilot, not a launch.

MerVare

mervare.app · mervare.io · since 2026
Live pilot

A marina system that knows whether the berth is actually free.

Problem
Finding a berth in the Baltic still means calling a harbourmaster on VHF and hoping someone answers, while the harbour itself runs on a paper book and a phone.
System
A two-sided product: mervare.app is sailor-facing, mervare.io is the marina back office, and every harbour gets its own subdomain, branding and operator accounts. A full booking state machine with role-based access sits behind it, Stripe Connect moves money straight to the harbour rather than through me, and a custom Go/ESP32 bridge into a Victron Cerbo GX over EMQX MQTT is built to report whether a berth is physically occupied — so availability can be verified by a sensor rather than by a form someone forgot to update.
My part
I designed the data model and the booking state machine, built both products and the hardware bridge, and operate the live pilot.
Next.jsSupabase / PostgresStripe ConnectRBACEMQX / MQTTGo on Venus OS (ARM)ESP32Victron Cerbo GX
  • Live pilot: hara.mervare.app — Hara harbour, Gulf of Finland
  • First version: 5 days, 206 commits — auth, payments, booking state, MQTT, hardware bridge
  • Model: 5% commission plus marina SaaS
Become a founding marina

loksa.camp

loksa.camp · since 2026
Live platform · Host onboarding in progress

A Baltic rental marketplace designed for people, fleets and agents.

Problem
Camper and motorhome supply in the Baltics is fragmented across owners with no shared inventory.
System
A marketplace with real host economics and a fleet view, built on the bet that a meaningful share of travel demand will arrive through an AI agent rather than a browser. So it ships an MCP server, an OpenAPI specification and an llms.txt as first-class surfaces, letting an agent discover inventory and complete a booking without scraping a page.
My part
I built the marketplace and its machine interfaces. Supply-side onboarding is in progress — no traction claims yet.
Next.jsSupabaseVercelMCPOpenAPIllms.txt
  • Platform: live
  • Supply-side onboarding: in progress
See the system

Zoovet

zoovet.dev · since 1998
Client system

Long-term stewardship of a business-critical commerce platform, modernised without stopping the business.

Problem
A long-lived Django/Oscar commerce stack has to keep taking B2B orders while it is modernised — nothing here can be rewritten from scratch, because the business does not stop.
System
Long-term stewardship of business-critical commerce and the infrastructure around it for a B2B veterinary wholesaler: incremental migration of the Django/Oscar stack onto a supported footing without a freeze window, and the supporting servers kept patched and running.
My part
I modernise and operate the platform and its infrastructure. I am the person they call.
DjangoOscarPythonPostgresWindows ServerLinux
  • Relationship: Client since 1998
See the system

PiratesEye.club

pirateseye.club · since 2026
In development · Creator-owned

Turning attention into a community the creator can own and operate.

Problem
A large English-speaking audience built over a thousand videos lived entirely on someone else's platform, with no membership, no product and no direct relationship.
System
Product, brand architecture, membership funnel and revenue model for an independent creator business — memberships, sponsorship inventory and digital products — designed to be handed over so the creator operates it without me.
My part
I designed the product, the brand architecture and the revenue model. The deliverable is an operating business, not a website.
Next.jsSupabaseStripeVercel
  • Status: in development — creator-owned
See the system

Background

Thirty years in production, five in business school — at the same time.

Two tracks that ran in parallel and now operate as one practice. Engineering gives the systems credibility; the degree is why each venture has a price, a customer and a route to market.

Degree, alongside the job →

Work

System engineer 1995–2000
HNS (Hackers Night System), then Estonian Telephone Company
Senior Linux system administrator 2000–2013
Elion
System developer 2013–2017
Telia
Self-employed developer 2016–2019
Python / Django
Infrastructure project manager 2018–2020
Veebimajutus.ee
SRE, then SRE Team Lead 2020–2022
Entigo
Database Reliability Engineer 2022–
Bolt

Study

BSc, Computer Science 2015–2019
Estonian IT College
Coaching Skills Certificate 2018
Academy of Executive Coaching (AoEC)
Leadership Development Programme 2019
EBS Executive Education
BA, Business Administration and Management 2021–2026
Estonian Business School
Volunteer maritime rescuer, level 1 2022
Estonian Voluntary Sea Rescue
19952000200520102015202020252026

Contact

What’s your next build?

Bring me an operation that deserves a better system. If you run something real — a harbour, a fleet or a platform that has outgrown its spreadsheet — let’s talk.
Practice
MoiToi OÜ · Loksa / Tallinn, Estonia
Web
moitoi.tech