There are four ways to try Multilarm and none of them require an account, a card, or a conversation. Watching the demo takes two minutes. Driving the live dashboard takes five. Building your site's real configuration in the browser takes about fifteen and gives you a file you keep. Installing it takes about half an hour. Personal, non-commercial use is free permanently, with every feature present and nothing expiring — it is a licence tier rather than an evaluation period.
Two minutes. No installation.
A narrated walkthrough of a real installation: a schedule firing, a live announcement ducking the music under it, the on-device neural voice speaking a line that was typed a second earlier, and the same box being driven from a browser somewhere else. If it does not look like the thing you need, you have spent two minutes and you can stop here.
Five minutes. No account, no installation.
The web dashboard is the surface most people actually use day to day: the schedule, the zones, the announcement box, the status of the device. Click around it before you install anything. What you cannot do here is hear it — the audio comes out of a building, not a browser tab.
Fifteen minutes. Produces a file you can keep.
The Config Generator is the same tool used to commission real sites. Work through your actual bell times, zones, prayer-time method or shift pattern and it writes the configuration file the software reads. Nothing is uploaded and nothing is stored: it runs in your browser and hands you a file. Doing this before you install is the fastest way to find out whether the software models your building the way you think about it.
Half an hour, including the audio wiring you already have.
Windows, Linux on 32-bit and 64-bit ARM (there is no x86-64 Linux build), and a ready-made Raspberry Pi image. Drop the configuration from step 3 next to the binary and it starts doing what you described. Free for individual, non-commercial personal use, with no feature held back and no clock running — see the note below on what that does and does not cover.
Free for individual, non-commercial personal use. Not a trial: nothing counts down, nothing stops working, no feature is withheld, and the software does not check in with anything to decide whether you are still allowed to use it.
The line is the building, not the feature set. Running it at home is free. Running it in a mosque, school, factory, office, care home, hotel or any other organisation needs a one-off perpetual licence, and that includes voluntary and charitable settings — charities and small mosques have their own tier for exactly that reason. Licences are bought once and do not renew. The only thing billed monthly is the optional Cloud Relay, and the device works without it.
Everything asserted on this site is published in a form you can parse:
No. Personal, non-commercial use is free permanently and every feature is present. Nothing expires, nothing phones home to check, and no capability is withheld to make you buy. This is a licence tier, not an evaluation period, and the distinction matters: an evaluation period ends.
You, at home, on your own hardware, not as part of anything commercial. The moment it is running in a mosque, a school, a factory, an office, a care home or any other organisation — paid or voluntary, charitable or not — it needs a licence. Charities and small mosques have their own tier. The full terms are on the pricing page.
Yes, and the honest route is step 3 followed by step 4 on your own hardware at home. Build your site’s real configuration in the generator, run it on a spare machine or a Raspberry Pi, and you will know within an evening whether it does what your building needs. Then licence it when it goes into the building.
Not to try it, and not to buy the software. Every step on this page is self-service. Contact is for commissioning, cloud relay setup, invoicing and questions the documentation did not answer.
Audio output, hardware relays, GPIO triggers and anything involving the sound card. The demo dashboard shows the control surface, not the sound. To hear it you have to install it, which is step 4 and takes about half an hour.
Read the feature matrix at /features.json, which states every feature as shipped, partial, absent or declined and names the source file behind the shipped ones; the measured figures at /benchmarks.json, each with its device, method and date; and the comparisons at /compare/, which name at least three things each competing product does better.