Calls that stay yours

Your cloud can do more than hold files. With chat and calls switched on, it becomes the place where your team writes to each other and sees each other — inside the same private space where the documents already are. No third company in the middle, no account to create somewhere else, no meeting link that expires.

What you get

• Conversations — one to one, or a room per team or project, with the history kept.
• Video and voice calls, straight from the browser. Nothing to install.
• A call from a file. You are looking at a document together and you start talking about it — in the same place.
• A link for guests, so someone outside your organisation can join a call without an account.

All of it runs on your machine, in your cloud, under your address.

Why calls are harder than they look

Sending a file to a server is easy: the server has a fixed address and it is listening. A call is a different shape of problem — two people have to reach each other, and neither of them is a server. Both are usually sitting behind a home or office router, which is very good at letting you out and, by design, very reluctant to let anyone in.

Think of two people in two large buildings, each with a receptionist who will pass messages out but will not put strangers through. Most of the time the two sides manage to arrange a direct route between them, and the call goes straight across — fast, and touching nobody else. Sometimes, particularly on stricter office networks or certain mobile connections, no direct route can be found at all.

The relay

For those cases there has to be somewhere in the middle that both sides can reach: a relay that takes the picture and sound from one and hands it to the other. It is unglamorous, it has no interface, and nobody ever thinks about it — until a call fails, and it turns out this is the piece that was missing.

Most services solve this by using a relay that belongs to somebody else. That works, and it means your conversation passes through a machine you do not control.

MAESTRO puts the relay on your own machine, as part of your cloud. It is small — a few megabytes of memory, less than almost anything else you run. It gets a long secret of its own, generated and sealed, and your cloud is told about it so the two recognise each other. You tick one box while installing, and it is there.

The honest part

A relay is only useful if people outside can actually reach it, and that needs one port open: 3478, both TCP and UDP. MAESTRO opens it on your machine — but your provider may well have a firewall in front of you that we cannot see from inside.

So we do not assume. After it is running, MAESTRO knocks on that port from the outside, over the real internet, and puts the answer on the service's card:

• It answers from the internet — calls will connect from anywhere.
• Still closed from the internet: 3478/udp — and then a sentence saying calls will work on your own network, but not from outside, and that this is your provider's firewall to open.

That distinction matters more than it sounds. A relay that is running but unreachable looks perfectly healthy from every direction except the one that counts. Telling you now costs a sentence. Telling you never costs you a call with a client, and an afternoon working out why.

The point

Nothing here is exotic. Chat and calls have existed for years, and so has the relay that makes them work. What is usually missing is someone doing the whole job: installing it, giving it its secret, telling the cloud it exists, opening the port, and then honestly checking whether the world can get in.

You tick a box. Your calls stay yours.

← all articles