Holy ResourceHoly Resource
Getting Started

Installation

Install Holy Resource and complete a clean first launch.

Holy Resource runs as a desktop app on Windows, macOS, and Linux. Installation is local to the device. Your first launch then walks you through license validation or free mode, church setup, and account creation.

Use an internet connection on first launch when possible

Paid-license validation, owner verification, invite redemption, update checks, and some join flows work best online the first time. After setup, Holy Resource is designed to continue operating locally.

Download the Installer

Get the latest release from the official download page.

👉 Download Holy Resource

The download page automatically prioritizes the best match for your current OS and architecture, and it also exposes previous releases when they are available.

Current Installer Types

  • Windows: .exe installer or .msi package.
  • macOS: .dmg installer, and .pkg when published for that release.
  • Linux: .deb and .rpm packages.

If you are installing for a church that is moving from another machine, export a full backup from the old device first.

Run the Setup

Once the download is complete, open the file to begin the installation process.

  • Windows: Run the .exe or .msi, review the Terms of Use, and follow the setup wizard. Depending on the bundle and machine state, required runtime components such as WebView2 may also be installed.
  • macOS: Open the .dmg, move Holy Resource into Applications, then launch it from Applications.
  • Linux: Install the package that matches your distribution family, such as .deb for Debian/Ubuntu or .rpm for Fedora/RHEL.

Complete First Launch

When Holy Resource opens for the first time, onboarding begins.

  • Enter your paid license key, or continue in Free mode.
  • If the license is unclaimed, onboarding continues in owner claim flow.
  • If the license already has a super admin on another device, onboarding switches to Join and asks for an invite code.
  • In Claim and Free mode, enter church details and create the first local account for this device.
  • In Join mode, redeem the invite, verify the code sent to the invite email, then create or recover the local account that will sign in on this device.

See First Launch & Onboarding for the full setup flow.

Security Prompts

Desktop operating systems may still show trust or reputation prompts, especially on first launch or when running a newly downloaded build.

  • Windows: Click "More info" then "Run anyway".
  • macOS: Go to System Settings → Privacy & Security → "Open Anyway" if Gatekeeper blocks the app.
  • Linux: Some environments require you to trust or approve newly installed packages before first launch.

Security Prompt

If macOS blocks Holy Resource after it has already been moved into Applications, use the fallback steps shown on the download page.

Before You Install

Prepare these items before first launch:

  • your church name and primary church email
  • the paid license key, if this device will use paid mode
  • the owner email used at checkout, if you expect to claim or recover ownership
  • an invite code, if this device is joining an already claimed license
  • access to the invite recipient email inbox, if this device is joining with a license invite
  • the existing password for that email, if you expect to recover a saved account during paid-license onboarding
  • a current backup, if you are replacing or migrating from another device

System Requirements

Recommended baseline:

  • OS: Windows 10/11, macOS 11+, or modern Linux distro.
  • RAM: 4GB minimum (8GB recommended for larger congregations).
  • Storage: 500MB for app files, plus room for backups.

Moving to a New Computer

Installation does not automatically move your local database from an old machine.

  1. Export a full backup on the old device.
  2. Install Holy Resource on the new device.
  3. Complete the correct license flow: claim, recovery, transfer, or invite join.
  4. Restore your data after the new device is ready.

If ownership or device access is involved, review Licensing before you switch machines.

Last updated on

Was this helpful?

On this page