I posted a while back about online amateur radio logging (here) and wanted to do a follow up on some of the client software I've been using to log contacts and sync to both LOTW and QRZ.
I used to use CQRLOG, which is still a great logger, but it is primarily intended to be installed directly on the PC you're logging from. If you want to view QSOs or add a new entry, you need to have access to that PC.
For greater flexibility, there are now self-hosted server-based logging platforms which allow access from any device with a web browser and internet access, such as Wavelog and Cloudlog. I'm going to refer to Wavelog throughout this post, but the features are similar between them both Wavelog and Cloudlog (the former being a fork of the latter).
Wavelog is a PHP application intended for a LAMP stack, although it actually works on a variety of systems: more on that at the end.
To start, here's a quick screenshot of the QSO entry, on both desktop and mobile:
At a glance, you can see all of the details of the station as soon as you enter the callsign. If the station has a QRZ profile, it will even display their profile photo!
Once you start building your logs, Wavelog can create a number of reports and analytics based on your logbooks, such as:
Or band usage:
It can also track progress towards awards, such as:
One of the features that I particularly enjoy is that you can upload QSL cards into your logbook, attached to the QSO entry:
It can also automatically retrieve eQSL cards, as well! As I mentioned before, Wavelog can sync entries to LOTW, QRZ, eQSL and more, and will show you the confirmation status for each.
If you happen to use Gridtracker, it can log directly to Wavelog. There is also a small helper application which will allow you to log directly from wsjtx and automatically sync your qso entry page to your radio via FLRig (freq, band, etc).
I've been running a Cloudlog server for both myself and my father until about a month or two ago when I switched to Wavelog. The migration from one to the other was fairly straight forward, and the Wavelog wiki provides instructions. I'm running Wavelog on an Nginx webserver with a MariaDB backend, but there is also a Docker image if you want something simpler. I did test Cloudlog on a lighttpd server, as well, and encountered no problems.
So far, I'm happy to report that Wavelog has been quite reliable. The only downtime I've encountered is when I've accidentally broken the webserver itself, and that's certainly not the fault of Wavelog.
If you're looking to try a new logging solution, Wavelog would get a strong recommendation from me.
Check it out at Wavelog.org