Skip to content

Desktop app ​

Aurora has a native desktop app for macOS, Windows, and Linux, built with Tauri. It's smaller and faster than Electron-based alternatives.

Public beta: new desktop releases come to Apple Silicon Macs first. Builds for Intel Macs, Windows and Linux may lag behind or be temporarily unavailable. See Beta limitations and the live download page.

Download ​

Download the latest release from aurora.ink.

PlatformFormat
macOS (Apple Silicon).dmg (released first)
macOS (Intel).dmg (may lag behind in beta)
Windows.msi / .exe (may lag behind in beta)
Linux.AppImage / .deb (may lag behind in beta)

Installation ​

macOS: Open the .dmg, drag Aurora to /Applications.

Windows: Run the .msi installer.

Linux: Make the .AppImage executable (chmod +x) and run it, or install the .deb with dpkg -i.

Onboarding hub ​

A fresh install opens on the sign-in screen. Choose Use without account (workspace files) there and the desktop shell shows a hub titled "How do you want to start on this desktop?" with three entry points:

EntryStorage modeNotes
Sign in to AuroraCloudAuroraCloudUse your existing account. You can enable Local folders later when you also want a folder-backed working copy.
Create a new Aurora folderOffline foldersPick an empty folder on disk; it becomes your workspace. No account needed.
Open an existing Aurora folderOffline foldersReconnect to a folder you already use on another device; saved local settings come back automatically.

The hub is shown once per device. Once you have made that first choice, Use without account (workspace files) with no folder open shows "Choose a folder for your workspaces" instead, with Choose folder and Sign in. Choose a folder that already has Aurora workspaces to open them, or an empty folder to start a new workspace in it. If the folder belongs to an AuroraCloud account, Aurora says so and offers Sign in or Choose another folder.

See Sync & storage for the full storage-mode model and how to upgrade Offline folders to Local folders later.

Signing in ​

The desktop app uses the same account as the web app. You can:

  • Log in with your Aurora email and password. If Aurora asks you to verify, enter the code sent to your email. You can choose Trust this device to skip the code here for a while.
  • Use a provider under Continue with, when AuroraCloud offers one. The desktop app opens your system browser to finish signing in, then returns you to the app. If provider sign-in is not available in the desktop app, Aurora says so and you can use email and password instead.
  • Skip the account and choose Use without account (workspace files) to work in an Offline-folders workspace.

Settings → Desktop → Desktop sign-in shows whether your sign-in is remembered in the operating system's keychain or kept for this session only.

Local file activity log ​

Whenever the desktop app reads, writes, imports, or skips a file in your Aurora folder, it records a structured entry in the activity log. Settings → Desktop → Recent file activity shows:

  • External edits picked up by the watcher (Finder edits, another device's writes via cloud-drive sync, etc.)
  • Manual rescan results (X imported, Y removed)
  • Files Aurora skipped because it had just written them itself
  • When the workspace entered or left read-only safe mode

The panel is exportable as JSON for support purposes (Settings → Desktop → Recent file activity → Export JSON).

Desktop sync center ​

Settings → Desktop → Desktop sync center covers the active workspace. It shows queued desktop sync work, recent queue items with status/age/failure messages, and native folder actions for the Local files root, workspace folder, and Markdown mirror target when those folders are available.

Use Re-scan now or Re-authorize folders when local-files permissions drift or you need Aurora to import fresh disk state without restarting.

The sync center also summarizes which workspaces are using AuroraCloud, Local folders, or Offline folders, including Markdown mirror state and whether watching is intentionally blocked by E2EE or owner offline-download policy.

Read-only safe mode ​

If the desktop app loses write permission on your Aurora folder (folder revoked, drive unmounted, encrypted volume locked), the workspace flips into a read-only safe mode:

  • An overlay banner appears explaining the cause (folder permission denied / offline-download disabled / workspace folder unavailable)
  • Aurora keeps reading and rendering the workspace but blocks every write attempt with a clear error
  • AuroraCloud sync, if active, continues uploading already-staged changes but does not pull new content into the broken folder
  • When permission is restored, Aurora clears safe mode automatically and resumes normal operation

This prevents silent data loss when the disk goes unwriteable mid-session.

Encrypted folder workspaces ​

Folder-backed encrypted workspaces reopen in a locked state and must be unlocked on the device before content can be read or exported. The on-disk workspace files remain encrypted, and Aurora restricts the automatic watcher/import loop while the workspace is encrypted. See Security & encryption for the full flow.

Clean Markdown ​

Desktop Local folders can use Aurora JSON or Clean Markdown. Aurora JSON is the safest native format. Clean Markdown is plaintext and intended for people who want editable .md files alongside Aurora's hidden sidecar state. See Sync & storage.

Secret storage on desktop ​

Sensitive desktop-only secrets (e.g. AI provider keys you opt into persisting) are stored in the OS keychain — Keychain Access on macOS, Credential Manager on Windows, Secret Service / libsecret on Linux. If the OS keychain is unavailable, Aurora does not silently downgrade to plaintext storage; it surfaces a visible Settings warning and keeps the secret in session memory only.

Custom AuroraCloud endpoint (self-hosting) ​

The desktop app reads an optional config.json from the platform-specific app-data directory at launch and uses any apiUrl it finds to override the AuroraCloud endpoint. This lets a packaged build talk to your own AuroraCloud backend without rebuilding.

OSPath
macOS~/Library/Application Support/com.aurora.docs/config.json
Windows%APPDATA%\com.aurora.docs\config.json
Linux$XDG_DATA_HOME/com.aurora.docs/config.json (defaults to ~/.local/share/com.aurora.docs/config.json)

Shape:

json
{
  "apiUrl": "https://cloud.example.com"
}

Trailing slashes are trimmed. An empty string or missing apiUrl clears any previously stored override and falls back to the default, https://api.aurora.ink. The file is read once at startup — relaunch Aurora after editing.

https://api.auroradocs.eu, the API's name before the rename to Aurora, reaches the same AuroraCloud. An install that is still signed in there with no endpoint set stays on it, so the session and its folders keep working; Settings shows it as Production. After you sign out and restart Aurora, the next sign-in uses https://api.aurora.ink.

The override is intended for self-hosted deployments and managed support scenarios. Most users should leave it unset.

You can also switch endpoints under Settings → Desktop → Updates (the API endpoint box). Aurora signs you out, clears the old server's cached data and restarts. It stops first while edits on this device have not synced, and says which ones:

  • Edits from this account sync once AuroraCloud can be reached. The Desktop sync center lists them while their workspace is open.
  • Edits by another account that used this device, and edits saved while no one was signed in, are only counted. Only an edit's own record says who wrote it, and these name no account that is signed in now. The switch never shows, exports or deletes them. Their account can sign in and let them sync.
  • This account's edits in workspaces it no longer has cannot be sent to this server.

You can wait for them to sync, or choose Keep them here and switch. Aurora then sets every one of these edits aside on this device, unchanged, for the server you are leaving. Set-aside edits are out of sight: no page, search, folder export or assistant shows them, and no account on the new server can see, take over or send them. When this device is on that server again, they come back as they were, and their accounts can sync them. A set-aside edit never replaces an unsent edit made since; it stays set aside. An edit made after Aurora stopped the switch is not covered: the switch stops again and offers the choice again. Unsent AI usage records still have to sync first. Offline and local-only workspaces this device keeps are not touched.

api.aurora.ink and api.auroradocs.eu are two names for the same AuroraCloud, and so are localhost and 127.0.0.1 on the same port. Switching between two names of the same server skips this check and keeps the cached data, because the same edits sync there.

Reset local cache deletes set-aside edits too. Its warning counts them as edits kept for another server.

Updates and release channels ​

The app checks for updates on launch and prompts you to install them. You can also check manually under Settings → Desktop → Updates, where Aurora shows the update status, available version details, release notes, and when it last checked.

There are two release channels:

ChannelWho it is for
StableEveryone. This is the default.
PreviewPeople who want to try pre-release builds before they reach Stable.

Switch channels under Settings → Desktop → Updates → Release channel. Most people should stay on Stable. Preview builds get new changes earlier and may have more rough edges.

Offline use ​

The desktop app stores a local copy of every workspace and works fully offline regardless of storage mode. Changes sync to AuroraCloud the next time the device is online (in Local folders / AuroraCloud modes).

Differences from the web app ​

The desktop app has the same features as the web app and adds:

  • Onboarding hub with three storage modes, including no-account Offline folders.
  • Native file dialogs for saving exports and opening folders.
  • Folder watcher that picks up external edits to your Aurora folder in real time, with a visible activity log.
  • OS keychain integration for sensitive secret storage.
  • Auto-update with Stable and Preview channels.
  • Desktop shortcuts: ⌘T opens a new tab, and on macOS File → New Page (⌘N) creates a page. See Keyboard shortcuts.
  • System tray Quick Capture — four capture actions directly from the menu bar / system tray (see below).
  • Read-only safe mode when the workspace folder loses write permission.

System tray Quick Capture ​

The desktop app adds a system tray icon with four dedicated capture actions:

Tray itemWhat it creates
New Inbox NoteA note dropped straight into the Inbox
New PageA new page
New NoteA new note
New TaskA new task

Clicking any of these opens a small, borderless, always-on-top capture window (420 x 320 px) with a title field and body area. Three actions are available:

  • Save (⌘Enter / Ctrl+Enter) — saves the page and closes the window.
  • Open — saves and navigates the main window to the new page.
  • Cancel (Escape) — closes without saving.

The tray also shows Open Aurora (brings the main window to front), an Open at Login toggle, and Quit Aurora.

Companion app trays ​

The companion apps have simpler tray menus:

  • AuroraNotes — Open AuroraNotes, New Note (⌘N), Quit.
  • AuroraTasks — Open AuroraTasks, New Task (⌘N), Quit.

Diagnostics ​

The desktop app keeps a diagnostics log on your device. If you need to share diagnostics for support, Settings → Desktop → Diagnostics → Export diagnostics saves the log together with non-sensitive details about the app. Secrets are never included.

Aurora is in public beta and free while beta.