Deploying Mimiq to a hundred edit suites is a one-day job, not a rolling project. One installer, a handful of scripted defaults, and a JSON file on your storage. Every editor on your floor is ready to go.

This is a guide for the people responsible for making that happen.

Installing Mimiq at Scale

Mimiq ships as a standard macOS or Windows installer and fits into any MDM workflow you already have: Jamf, Mosyle, Kandji, Intune, or otherwise. Push it to as many machines as you need. Everything else (activation, behavior, Workspaces) gets configured remotely.

License Activation Without Touching the Machine

Activating Mimiq doesn't require an editor to do anything. The app exposes a URL scheme that accepts a license key directly:

mimiq://activate?key=[your license key]

Deactivation works the same way:

mimiq://deactivate

Both can be scripted and pushed via MDM alongside the initial install, so machines come up fully licensed on first boot.

The License Manager

All of your licenses are manageable from account.hedge.video. From there you can see how many activations are in use, add more seats, deactivate individual machines, or do a full reset if a machine is lost or reassigned. No need to touch the machine. Remote deactivation is a single click.

Local License Server

Keep licensing on your own network. No dependency on the internet, no external service. Mimiq's Local License Server (LLS) runs on practically any hardware (a Linux box, a Raspberry Pi, a Mac Mini, a Windows Server) and serves licenses to clients over your local network.

Point each Mimiq installation at it with:

open "mimiq://licenseactivation?mode=local&ipAddress=192.168.1.10&port=1234"

Or, if you prefer pushing a preference directly (also MDM-friendly on macOS):

defaults write video.hedge.Mimiq.Mac LocalLicenseServerSettings -string '{"port":1234,"ipAddress":"192.168.1.10"}'

The LLS supports both online and fully offline (challenge/response) activation. It can also run as a launchd daemon on macOS, a systemd service on Linux, or a Windows Service, so it starts automatically with the system and requires no ongoing management. You can parse its log files to track lease usage per machine if you need that visibility.

Controlling the Experience

Mimiq lives in the menu bar and stays out of the way. All of the settings below are scriptable and MDM-friendly, so you can push them alongside the installer and never think about them again.

Autostart

Mimiq launches at login by default. To override this on macOS:

# Disable autostart
defaults write video.hedge.Mimiq.Mac launchAtLogin -bool false

# Enable autostart
defaults write video.hedge.Mimiq.Mac launchAtLogin -bool true

On Windows, autostart is controlled via the standard HKCU\Software\Microsoft\Windows\CurrentVersion\Run registry key.

Suppress the Startup Popup

When Workspaces are already configured, there's no reason for Mimiq to announce itself every login. Suppress the startup window and it'll mount everything quietly in the background:

# macOS
defaults write video.hedge.Mimiq.Mac disableWindowPopup -bool true

On Windows, set StartupWindowPopupEnabled to 0 in HKCU\Software\Mimiq. Mimiq still runs in the menu bar and is accessible whenever needed. It just doesn't pop up uninvited.

Suppress Update Notifications

You control when updates roll out — not the app. Disable the built-in update prompts so editors don't see anything you didn't schedule:

# macOS
defaults write video.hedge.Mimiq.Mac disableUpdateNotifications -bool true

On Windows, set CheckForUpdatesOnStartupEnabled to 0 in HKCU\Software\Mimiq.

Workspace Limits

The default cap on macOS is 8 simultaneous Workspaces (macFUSE has overhead). Raise it for high-spec machines, lower it where resources are tighter:

defaults write video.hedge.Mimiq.Mac workspacelimit

On Windows, where Workspaces consume drive letters, you can set the starting letter to avoid conflicts with other mapped drives:

New-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "WorkspaceStartDriveLetter" `
  -Value "W" -PropertyType STRING -Force

Setting Up Workspaces for the Team

Having each editor configure their own Workspaces is asking for inconsistency. Shared Workspaces fix that: set them up once, and every editor on the same storage sees the same configuration automatically.

How Shared Workspaces Work

Sharing a Workspace writes a config file to the root of the parent volume at:

/Mimiq Settings/MimiqEnabled.json

Every machine that mounts that volume picks it up automatically. No agent, no database, no sync service. The storage is the source of truth. The JSON is human-readable and can be written by hand, by Mimiq, or generated by an orchestration system:

{
"version": "26.2.0",
"ignore": false,
"workspaces": [
	{
		"path": "Jobs/ShowA/Bins",
		"group": "Show A",
		"disabled": false
	},
	{
		"path": "Jobs/ShowA/Media",
		"group": "Show A",
		"disabled": false
	}
]
}

One important detail: the folders referenced in path must actually exist on the volume. The JSON tells Mimiq which folders to expose as Workspaces. It doesn't create them. If you're generating this config from an orchestration system, make sure folder creation is part of the same job setup step.

Auto-Mount

Shared Workspaces can be set to auto-mount, so Mimiq picks up exactly where it left off each time an editor logs in. Combined with the suppressed startup popup, the whole process is invisible to editors. Their storage is just there.

Disabling Volumes

Not every volume on a machine should be accessible to Media Composer. Mimiq lets you selectively disable volumes or Workspaces (the disabled flag in the JSON config), which is useful for backups, test drives, or anything outside the current workflow. Disabled volumes don't show up in Media Composer but remain listed in Mimiq for easy re-enabling.

Workspace Groups

When your team is running dozens of Workspaces across multiple jobs, editors need a way to find and mount the right ones without digging through a long list. Workspace Groups solve that.

A Group is a named set of Workspaces. An editor opens Mimiq, finds their show's Group, and mounts everything in it with one click. No hunting, no manual setup on each machine.

Groups are just another key in the same MimiqEnabled.json config, so they require no additional infrastructure. Just write the JSON. If you're creating jobs in an orchestration system, you can automate Workspace Group creation as part of your job setup workflow. Ortana's Cubix and StorageDNA's DNAFabric both already offer native integrations for exactly this.

Groups can span multiple storage volumes, so a show that's spread across a NAS and a cloud drive can still be one Group as far as the editor is concerned.

Workspace Discovery

If you're migrating an existing infrastructure or inheriting a storage layout that wasn't set up with Mimiq in mind, Workspace Discovery lets Mimiq scan a volume and automatically identify all folders that contain Avid MediaFiles, the natural candidates for Workspaces. Select the ones you want, and they're added in one pass.

Discovery also detects existing SANFusion bundles, so if you're moving off SANFusion, there's no migration work required.

One Setup to Rule Them All

MDM handles the install and activation. A few scripted defaults take care of the startup popup and update notifications. The Local License Server (if you need it) keeps licensing on your network. And when a new job spins up, your orchestration platform writes the MimiqEnabled.json, with Workspaces and Groups ready to go before the editor's first login.

Editors see storage that's just there. IT sees a tool they control end to end.

Questions about your specific setup? Drop us a line. We're happy to help ✌️