Roadmap

Where the project is headed

KE8YGW Logger is being built in phases, starting from a locked core architecture. Here's the order things are coming together in.

Phase 1

MVP

In progress

Casual logging, POTA/SOTA support, LAN-first sync, ADIF import/export, roles & permissions, a GUI shell, and built-in diagnostics — the core experience the rest of the platform builds on.

Phase 2

Interoperability

Planned

Auto-discovery and import from other logging software, plus QRZ logbook integration, so switching to KE8YGW Logger doesn't mean losing your existing log.

Phase 3

Expanded operations

Planned

First-class support for club and event logging, net control workflows, emergency communications logging, and contest logging.

Phase 4

Remote & relay sync

Planned

Relay-based and self-hosted sync options for operators and stations that fall outside LAN range.

Locked architecture, evolving feature set

The core is deliberately locked down early: an append-only hash-chained event log, tombstone deletes, proposal-based plugin writes, LAN-first sync, multiple operator accounts, and an event bus with projections. New features build on top of that foundation rather than around it.

AI can assist with logging, but it never mutates the official log directly — every AI-assisted entry goes through the same proposal path as everything else.

Follow along

Development happens in the open on GitHub. Star the repo or watch releases to get notified as each phase lands.

GitHub Releases