Web agency · Tallinn, Estonia
And the software behind them. We write our own stack in Rust and run it on our own machines, so the site, the shop and the mail come from one place — and so does the answer when something breaks.
What we've built
A property portal, a mail system and a site builder with a shop. Written here, running now, ours to keep running.
Community · Property portal
A property portal for all of Estonia, running today at kodu.comm.ee with its first partner's listings — Lumi Kodud's, read off their own site by a feed. The one system here you can licence and run under your own name.
kodu.comm.ee/search?deal=rent&areas=tallinn
kodu.comm.ee/search?deal=rent&areas=tallinn&rooms=2&priceMax=900
kodu.comm.ee/map?q=Tallinn
kodu.comm.ee/listing/15
kodu.comm.ee/provider/lumikodud?deals=rent
kodu.comm.ee/search?deal=rent&areas=tallinn&rooms=2&priceMax=670
kodu.comm.ee/publish?deal=rent&type=apartment&address=Manufaktuuri+14-15%2C+Tallinn
Communication · Mail, end to end
Mail written, delivered and read by software we wrote. The server, the client and the screen. It ships with every site.
mail.comm.ee/?c=140
mail.comm.ee/?c=140&t=221
mail.comm.ee/?c=140&t=221
mail.comm.ee/?c=140
mail.comm.ee/?c=140
Commerce · Site and shop
Pick a name and you have an address, a mailbox, a website and a webshop. Nothing to install, nobody to book. The console is where you run it.
console.comm.ee/sites/14/pages
register.comm.ee/
console.comm.ee/sites/14/products/42
roastery.demo.comm.ee/
console.comm.ee/sites/14/products
Heavy AI integration
Every product here has the same assistant beside it. It reads what the product holds, it opens the product's own screens next to the conversation, and nothing it writes leaves without the owner's press. The same tools are on MCP for an agent of your own.
«Leia mulle kahetoaline üürikorter Tallinnas, üür alla 670 €» — six, counted, Lumi Kodud's flats as cards beside the words, and the portal's own search open on the page with those filters lit.
«Millal ja kus on Jürgeni sünnipäev?» — found in the thread, named with the message it came from, and that conversation opened beside the chat.
Both pictures were taken on a running system, the assistant answering for real; the address bar names where.
Why hire us
The mail server, the DNS, the HTTP, the portal, the shop and the page you are reading are one Rust workspace. Not because it is fashionable: because a wrong state that does not compile is a bug nobody has to find at three in the morning.
An address, a money amount, a listing's deal and a mailbox's screen are types, not strings, and a closed set of values is an enum in the database too. No null, no exception, every match exhaustive — a case forgotten is a build that fails, not a customer that does.
Every screen is written in our own html! macro, and the markup is checked while it compiles: an unclosed tag, a nested <a> or a stray </nav> is a compile error. One set of controls — one field, one button, one gallery — and every product wears the same ones.
PostgreSQL, one schema, no ORM. Every query is a file, compiled into typed Rust before the server starts, so a column renamed is a build that fails. Enums where the values are closed, indexes where the numbers said so — a search that took 1.8 seconds takes 60 milliseconds now — and migrations in one sequence nobody edits after they have run.
Protocols know no product. Platform knows no application. An application never names another, and a feature — the assistant's memory — names none. A landing page is a tier of its own. Rules like these are written down under stable numbers, and every change cites the one it bends.
html! {
section(class="ui-gallery", data-testid=section, data-slides=n) {
for (nth, s) in slides.iter().enumerate() {
a(class="ui-gal-shot", href=esc(s.src)) {
img(src=esc(s.src), alt=esc(s.alt),
loading=[(nth > 0).then_some("lazy")]);
}
}
if several { emit(arrows(&words, section)) }
}
}Maud's shape, none of its magic. A splice is raw unless esc says otherwise, an attribute in brackets is there only when its option is Some, and a tag that does not close does not compile.
Three ways in
Most of what a company needs, we have already written. The first question is which of these three you are asking for.
Take01
Pick a name. You get an address, a mailbox, a website and a webshop. Nothing to install, nobody to book.
Licence02
Kodu is a property portal for a whole country. It exists and it runs. Licensing it costs a fraction of building it again.
Build03
Hired for the whole thing, not a sprint. From the first call to launch day and every day after.
How it's built
Anyone can write software. The question is who keeps it standing, and how anybody else builds on it.
One script turns a clean server into the whole platform. Our machines, our deploy.
Real Chrome against a real database, reset before every run. A button wired to nothing fails here, not in front of a customer.
Every model, every route, called with no credential and with somebody else's before it ships.
Every manual carries a Test panel. Pick an operation, press Run, and the call goes to the live server as you.
Who you'd be talking to
Gravitational Wave OÜ is a small software company in Estonia. Margus Pärt founded it and writes most of what it ships. The awkward parts — mail, invoicing, the national registers, the shop — are written here rather than bought in. That is why there is one place to ask.
Hire us and Margus is who you talk to. There is no account manager.
07 — CONTACT
A few lines about the problem is plenty. No brief, no procurement, no discovery phase. The reply comes from the person who would write the code — usually the same day.
Free 30-minute consultation. Pick a day and a rough time and we'll confirm by mail. No obligation, and you talk to the person who would build it.