Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.granola.ai/llms.txt

Use this file to discover all available pages before exploring further.

We know many IT teams prefer to manage app rollouts centrally. If you use an MDM or patch-management tool, this guide can help you package and distribute Granola through your own setup. Granola does not yet offer dedicated MDM configuration profiles, policy keys, or step-by-step support for tools like Jamf, Kandji, Omnissa Workspace ONE, FleetDM, or winget. However, many teams can still deploy Granola successfully by downloading our latest installers and managing rollout through their existing tooling.

​
Downloading the latest Granola installers

You can always fetch the latest public Granola installers from these unauthenticated endpoints:
  • macOS: https://api.granola.ai/v1/download-latest
  • Windows: https://api.granola.ai/v1/download-latest-windows
Both endpoints redirect to the current installer file:
  • macOS: .dmg
  • Windows: .exe
Make sure your download tool is set to follow redirects. 
# macOS
curl -L -o Granola.dmg https://api.granola.ai/v1/download-latest

# Windows
curl -L -o Granola.exe https://api.granola.ai/v1/download-latest-windows
If your network uses egress filtering, please allow access to:
  • api.granola.ai
  • dr2v7l5emb758.cloudfront.net
The CloudFront domain hosts the installer files that the Granola download endpoints redirect to.

​
Checking when a new version is available

To check whether there is a newer Granola release, use our public versions endpoint. No authentication is required. 
curl -s https://api.granola.ai/v1/get-versions
The response looks like this: 
{
  "production": "7.205.0",
  "beta": "7.205.0"
}
For most managed deployments, compare the production version with the version you currently distribute. You can poll this endpoint on a schedule, such as daily or weekly. When the production version changes, download a fresh installer for each platform you support. Some deployment tools prefer POST requests. If that is easier for your setup, the endpoint also accepts an empty JSON body: 
curl -s -X POST https://api.granola.ai/v1/get-versions \
  -H "Content-Type: application/json" \
  -d '{}'
We recommend resolving the latest installer URL each time you prepare a deployment, rather than storing an older versioned installer URL long-term. If your deployment tool validates an old installer URL after a newer Granola release has shipped, that old URL may no longer be available.

​
How Granola auto-updates normally work

For most users, Granola keeps itself up to date automatically. While the desktop app is running, it checks for updates roughly every 10 minutes. When an update is available, Granola downloads it in the background and installs it when the app can safely restart, or when the user chooses to install the update. For auto-updates to work smoothly, users need a setup where Granola is allowed to update itself:
  • On macOS, Granola should be installed in the Applications folder, and the signed-in macOS user needs permission to replace the Granola app bundle.
  • On Windows, Granola’s default installer is per-user, so auto-updates are most likely to work when Granola is installed somewhere the signed-in Windows user can update.
  • On both platforms, the device needs network access to Granola’s update and download services.
If an MDM policy, OS restriction, or system-wide installation prevents the signed-in user from updating the app, Granola may not be able to auto-update itself. In that case, your IT team can distribute newer versions using the managed installation workflow below.

​
Managing updates centrally

If your organization prefers to test and promote app updates centrally, you can manage Granola updates yourself:
  1. Poll https://api.granola.ai/v1/get-versions on a schedule.
  2. Compare the production version with the version currently approved in your deployment system.
  3. When a new version appears, download fresh installers:
    • macOS: https://api.granola.ai/v1/download-latest
    • Windows: https://api.granola.ai/v1/download-latest-windows
  4. Test the new version with your chosen pilot group.
  5. When you are ready, promote the same installer through your MDM or patch-management tool.
This lets your IT team keep control of rollout timing while still picking up new Granola releases from the latest supported installer URLs.