macOS · Apple silicon
Macs with an M-series chip.
Disk image (.dmg)
Desktop client
The same Mirket, in a window of its own.
The desktop client connects to the Mirket installation your institution runs. You give it that address once. Nothing in the client decides where your course work lives, and it never routes anything through us.
Recommended for this computer
Checking which build fits this computer
All builds
Pick by operating system and processor. The checksum for every file is published alongside it.
macOS · Intel
Macs with an Intel processor.
Disk image (.dmg)
Windows · 64-bit
Almost every Windows PC.
Installer (.exe)
Windows · ARM
Windows on ARM, such as Copilot+ PCs.
Installer (.exe)
Before you install
- An installation to connect to
- The client is a shell, not a service. It needs the web address of the Mirket installation your institution runs — your administrator has it. There is no Mirket account to create and nothing to sign up for here.
- macOS 13 or later, or Windows 10 or later
- On a Mac, Apple silicon and Intel are separate downloads. On Windows, so are 64-bit and ARM. If you are unsure, the recommended build above is chosen from what your browser reports.
What the client adds
Everything Mirket does in a browser, it does here. These four are the things a browser tab cannot do.
- Screen sharing that lists your windows
- Presenting in a live session opens the client’s own picker of screens and windows, instead of the browser dialogue that leads with a list of tabs.
- Notifications while the windows are closed
- The client asks your installation how many notifications are unread and tells you the count. It never puts a message title or a sender on your lock screen.
- It still opens when the server does not
- After the first connection the client keeps a copy of the interface. On a dropped network it opens and says it cannot reach your installation, rather than failing like a browser tab. Course data is never served from that copy — stale coursework read as current is worse than none.
- Updates come from your institution
- The client asks the installation you connect to whether a newer version is published, and never contacts Mirket to do it. An installation with no route to the internet keeps working.
Opening it the first time
These builds are not yet signed with a developer certificate, so both systems stop the first launch and ask you to confirm. Each asks once. Signed builds are coming, and this step disappears with them.
- macOS
- Open the disk image and drag Mirket to Applications. The first launch is refused with a message saying macOS cannot verify the developer. Open System Settings, go to Privacy & Security, scroll to the note about Mirket, and choose Open Anyway.
- Windows
- Run the installer. SmartScreen shows “Windows protected your PC” because it does not recognise the publisher yet. Choose More info, then Run anyway.
Verifying a download
Every release publishes a SHA512SUMS file beside its binaries. On macOS run shasum -a 512 against the file you downloaded and compare it; on Windows, Get-FileHash -Algorithm SHA512. These builds are not code-signed yet, so this checksum is the check that matters.
Where updates come from
This page is where a person downloads the client the first time. After that the client checks your own installation, not this site. That keeps a client on an isolated network working exactly like one with internet access, and it means your client version tracks the installation it belongs to.