- Frequency definitions, sets, and profiles
- Selection, ordering, provenance, and capacity policy
- Radio inventory and managed image history
- Explainable omissions and degradations
Open-source radio configuration
Maintain the intent.
Compile for the radio.
RigManifest keeps frequency definitions, sets, and profiles independent of any one device. When it is time to program a radio, it compiles that reusable intent against the exact capabilities CHIRP detects from the radio image.
Local-first · GPLv3 · Windows, Linux, and macOS
New image + explainable diagnostics
The working model
One catalog. Many radio-specific results.
RigManifest starts with the way operators describe a useful loadout, then leaves device-specific representation to a capability-aware compile.
- 01
Define frequencies once
Keep receive and transmit behavior, signaling, mode, step, label, priority, and notes in a shared catalog—not inside one radio image.
- 02
Organize reusable intent
Group definitions into ordered sets, then combine sets and individual frequencies into profiles for places, trips, events, or operating roles.
- 03
Add a CHIRP image
RigManifest asks CHIRP to identify the exact radio driver, imports existing memories and banks, and retains the source image unchanged.
- 04
Compile, review, export
Compatible intent becomes a new CHIRP image. Renames, omissions, bank changes, and other compromises are shown as explicit diagnostics.
Shared frequency library
Define RF intent without committing it to a memory slot.
A frequency definition can carry receive and transmit behavior, access tones, receive squelch, mode, tuning step, priority, and notes. Sets keep those definitions ordered and reusable.
- User-owned sets remain editable.
- Built-in service presets remain read-only.
- Advisory plans warn without blocking a valid compile.

Profiles and prospective banks
Describe a place, trip, event, or role.
A profile combines ordered sets and individual definitions. Its preview shows grouping intent, while final memory positions and bank behavior are resolved only after a target radio is selected.

A deliberate handoff
RigManifest and CHIRP do different jobs.
RigManifest is a configuration-management frontend for CHIRP, not a replacement for it.
- Radio drivers and normalized capabilities
- Target-memory validation
- Radio-specific image formats and settings
- Communication with the hardware
Explainable compilation
See what changed and why.
RigManifest resolves duplicates, checks the selected target’s capabilities, maps banks where possible, and applies deterministic capacity policy. Catalog data is never changed by compilation.
Included Compatible with the selected target.
Adjusted A label, grouping, or feature was safely degraded.
Omitted The target cannot safely represent the intent.

Packages
Download the latest release.
Windows
Installer or portable ZIPThe portable build keeps its workspace beside the application.
Choose packageLinux
AppImage or Debian packageAppImage is portable; the Debian package uses normal application data.
Choose packagemacOS
Apple Silicon or Intel DMGUnsigned builds require one-time approval in Privacy & Security.
Choose packageDocumentation
Read the model before changing the radio.
The project documentation covers both everyday use and the architectural boundaries behind the compiler.
Getting started
Install the desktop app, add a radio image, organize a library, and complete the first export.
User guide
A page-by-page reference for the frequency library, radios, profiles, compilation, and settings.
Core concepts
The boundaries between definitions, sets, profiles, banks, radio images, and CHIRP.
Project roadmap
Current priorities, deferred work, synchronization research, and intentionally excluded scope.