comm.ee — Gravitational Wave OÜ

What we've built

Four systems, all live.

A property portal, a mail system, a site builder with a shop and a spatial engine that draws a room from a sentence. Written here, running now, ours to keep running.

Community · Virtual broker

Susanne

A virtual broker for all of Estonia, running today at susanne.ee: an owner sells and searches for free, through the assistant. On it, 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.

—One filter row over the list and the map.
—Addresses checked against the national register as you type.
—Estonian, Russian, English and Ukrainian.
—Invoices its users and matches payments off the bank statement.

Show details →

Susanne — Lumi Kodud's nine flats to rent in Tallinn as cards, each with a photograph, price and address

Filtering — Lumi Kodud's two-room flats in Tallinn under 900 a month, five of them, at Manufaktuuri and Aiandi

The map — Tallinn searched and drawn to the window's edge, Lumi Kodud's nine flats gathered into one pin on the city at this zoom

One listing — Manufaktuuri 14-15, a three-room flat from Lumi Kodud: its photographs, the floor plan, the 3D tour, the price, the facts and the street

Susanne beside the portal, asked for a two-room flat in Tallinn under 700 a month: she counts Lumi Kodud's five, draws them as cards and opens that search on the page

The assistant opened the publish form beside the chat — Manufaktuuri 14-15, Tallinn in the address box, Üür and Korter pressed, the register's card under the address and the year, floors, size and floor already in their boxes

susanne.ee/search?deal=rent&areas=tallinn

susanne.ee/search?deal=rent&areas=tallinn&rooms=2&priceMax=900

susanne.ee/map?q=Tallinn

susanne.ee/listing/715174

susanne.ee/provider/lumikodud?deals=rent

susanne.ee/search?deal=rent&types=apartment&areas=tallinn&rooms=2&priceMax=699

susanne.ee/publish?deal=rent&type=apartment&address=Manufaktuuri+14-15%2C+Tallinn

Communication · Mail, end to end

The mailbox

Mail written, delivered and read by software we wrote. The server, the client and the screen. It ships with every site.

—A list of people, not subject lines.
—Tags, files and tasks stay with the message.
—Reply in the thread, from your own address.
—A stranger's first message is screened before it lands.

Show details →

The mailbox — a list of correspondents newest first, one of them open with her thirty threads beside

One thread, thirty messages — Marie and the owner settling Jürgen's party, the earlier half of it on the page and the ten before that a press away

The assistant found when and where the party is and opened the conversation it was said in beside itself

The assistant lists the month's bills from what the mail said — electricity, phone and water, each with its due date — sums them, and opens the electricity bill beside the chat

A reply prepared by the assistant, shown as a card — To: Marie, the words, Dismiss and Yes, send it — nothing sent yet

mail.comm.ee/?c=140

mail.comm.ee/?c=140&t=221

mail.comm.ee/?c=87&t=87

Commerce · Site and shop

A site and a 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.

—Pages that change live as you type.
—Categories, discounts, cart, orders.
—Visitor numbers counted here, sold to nobody.
—Every manual carries a Test panel you can press Run on.

Show details →

Adding a page in the console — pages on the left, the real page in the middle

Registering a site — a name typed in, the address it will take worked out under it, and the four prepared looks to start from

Editing a product in the console — name, description, price, category and cover picture, the shop's own answers down the right

The shop as a visitor sees it — the products in their categories, each with a picture and a price

The assistant beside the console, asked which of the roastery's products cost under 15 euros, answering from the catalogue with a link to each

console.comm.ee/sites/14/pages

console.comm.ee/sites/14/products/42

roastery.demo.comm.ee/

console.comm.ee/sites/14/products

Spatial engine · Rooms and yards

Miiu

A spatial reasoning engine, running today at miiu.ee. A room or a yard is objects with sizes and places, the maths runs over them, and the picture is an output — for you on the screen, and for an agent over the wire.

—Every length a whole millimetre: a couch is 2200 by 900 at 1400, 3000, and the plan is the numbers.
—The maths is the product — distance, overlap, through, connected — asked of the plan, never of the pixels.
—REST and MCP, so an agent holding a key builds the same room the browser does.
—WebGPU first and WebGL2 when it is refused: Wire, Shaded, Ultra quality, and two tracers with a clock on them.

Show details →

Miiu — a living room 5,2 × 4 m as a wireframe: the walls, the window, the door and every piece of furniture as edges, each one a box the plan holds in millimetres

The same room in Ultra quality — the light gathered off a cloud of the room itself, the window lighting the floor and the furniture shadowing it

The same room ray traced on WebGL2 with a sixty-second budget, the card over the picture saying how many rays a pixel the sixty seconds bought

The assistant docked beside the room, asked to add a dining table 1200 × 800 mm in the middle — the table is in the plan and drawn on the picture, the robot saying where it put it

miiu.ee/p/175

Heavy AI integration

An assistant that works the screen, not a chatbot in the corner.

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.

Both pictures were taken on a running system, the assistant answering for real; the address bar names where.

In the products

—It steers the page: it names a screen and what the screen takes, and the product opens it — a search with the filters lit, a listing, a form filled from the register.
—It remembers: what a thread said is kept as facts, found by the words, by the sound of them or by what they mean, each naming the message it came from.
—It asks first: a send, a publish, a delete arrives as a card with one press on it, and the press is the owner's.
—It runs where you say: a local model on your own machine, Google's over the wire, or one for the chat and the other for the reading — per deployment, per kind of work.

In yours

—The same assistant over your data: your tables read through the tools your product already has, with the gates your product already keeps.
—Screens it can open, not text it can paste: the answer is your own page, drawn by your own code.
—An MCP surface for the agents your customers bring, every write a link their owner confirms.
—A memory where it earns one — facts out of documents, mail or tickets, screened before anything reads them, embedded on your machine.

Why hire us

Rust, all the way down.

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.

Types do the checking

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.

Screens checked as they compile

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.

One database, normalised

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.

Architecture that stays put

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 to work with us

Use one. Licence one. Or have one built.

Most of what a company needs, we have already written. Whichever you choose, we stay with it: analysis, development, maintenance and customer support come from the same people.

Use01

A ready product, today

Our own products, ready to use. Pick a name and you get an address, a mailbox, a website and a webshop. Nothing to install, nobody to book.

—Pages that change live as you type.
—Categories, discounts, cart, orders.
—Visitor numbers counted here, sold to nobody.

Licence02

A finished system under your name

Susanne is a virtual broker for a whole country: a property portal where owners sell and search for free, through the assistant. It exists and it runs. Licensing it costs a fraction of building it again.

—The whole of it: model, screens, API, tests.
—Your name, your hostname, your accounts.
—Hosted here, or handed over.

See Susanne →

Build03

Your problem, solved in software

Hired for the whole thing, not a sprint. From the first call to launch day and every day after.

—Analysis: what the problem really is, before a line is written.
—Development: written in Rust, built to outlive the project.
—Maintenance and support: we keep it running and answer your users.

Book a free consultation →

How it's built

We host it. We prove it.

Anyone can write software. The question is who keeps it standing, and how anybody else builds on it.

script to a running machine

One script turns a clean server into the whole platform. Our machines, our deploy.

browser specs

Real Chrome against a real database, reset before every run. A button wired to nothing fails here, not in front of a customer.

2,700

checks underneath

Every model, every route, called with no credential and with somebody else's before it ships.

Run

documentation you can press

Every manual carries a Test panel. Pick an operation, press Run, and the call goes to the live server as you.

REST manual with a test panel open — an operation, its parameters and a Run button — **REST.** The manual, called: an operation arrives prefilled, Run, and 200 OK.

MCP manual with a test panel open — a tool call and its answer — **MCP.** The same panel over the tools an agent calls. A write asks first.

Who you'd be talking to

The person who writes the code answers the mail.

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.

reg 12475903margus@comm.ee

07 — CONTACT

Tell us about the problem.

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.

margus@comm.ee +372 5384 3837

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.

We solve problems.

Four systems, all live.

Susanne

The mailbox

A site and a shop

Miiu

An assistant that works the screen, not a chatbot in the corner.

In the products

In yours

Rust, all the way down.

Types do the checking

Screens checked as they compile

One database, normalised

Architecture that stays put

Use one. Licence one. Or have one built.

A ready product, today

A finished system under your name

Your problem, solved in software

We host it. We prove it.

The person who writes the code answers the mail.

Tell us about the problem.