MAIN OÜ / About

About

MAIN OÜ is a one-person software company in Estonia. It is founded and run by Alexander Moon, who has been building software since 1998.

Who writes this

Everything on this site - the products, the code behind them, and the guides - is written by one person. That is worth stating plainly, because it explains both what you can expect and what you cannot.

What you can expect: the technical writing here describes systems I built and can answer questions about. When the security page lists an iteration count or a nonce length, it is the value in the shipped code, not a figure copied from somewhere else. When a guide says a technique has a limit, it is usually because I hit that limit.

What you cannot expect: a support rota, an on-call engineer, or a same-day reply. One person reads the email.

What MAIN OÜ makes

Both are built on the same principle, which is less a philosophy than a design constraint: if the data never reaches me, I cannot lose it, leak it, be compelled to hand it over, or be tempted to monetise it. classified holds ciphertext it cannot read. DashCam has no server at all. An Android version of DashCam is in progress.

How they are built

For anyone evaluating whether the technical writing here is first-hand: classified is a Vue 3 front end on Cloudflare Pages with a Cloudflare Worker API over KV, R2 and D1, sharing one frozen AES-256-GCM implementation with a Tauri desktop client so that both produce byte-identical output. DashCam is Swift and SwiftUI over AVFoundation, with the Android port in Kotlin and Compose. This site is hand-written static HTML on nginx - no framework, no build step.

The company

Legal name
MAIN OÜ
Registry code
11272196
Jurisdiction
Republic of Estonia
Registered office
Soosepa tee 46-2, Pärnamäe küla, Viimsi vald, Harju maakond, 74020, Estonia
Form
Private limited company (osaühing), one person

The registry entry is public and can be checked against the Estonian Business Register using the code above.

Editorial approach

The guides are written to be useful to someone deciding whether a technique fits their problem, which means they state limitations as prominently as capabilities. Where a guide describes something I have implemented, it says so. Where a claim rests on a specification rather than on my own testing, it cites the specification. Where something is best-effort rather than guaranteed, it says best-effort.

Nothing here is legal, security, or compliance advice, and reading it creates no professional relationship. If a page contradicts what a product actually does, the product is right and the page is a bug - tell me and I will fix it.

Get in touch Read the guides