Skip to content

Cloudlog

Cloudlog is a logbook you run yourself. You open it in a web browser, at home or from the other side of the world, and the contacts stay on your server. It was started by Peter Goodhall, MM9SQL, and a lot of the code since has come from other amateurs.

You need a web browser. The radio, the cluster, and LoTW are optional extras you switch on when you want them.

Two ideas come up on every page.

A station location is one place you operate from, with the callsign you use there. Home is one. A summit with /P is another.

A station logbook is a group of those locations that you want to see together. The list of contacts, the awards, and the charts all follow the logbook that is active. A location that is not linked to it stays in the log, and simply does not appear in that view.

Where to start

If the site is not on a server yet, start with Installing. If you can already log in, set a station location, put it in a station logbook, and log a contact.

The sidebar is the order of the guide. Previous and Next at the bottom of each page follow it.

  • Install. Docker on the dev branch, Linux, a Raspberry Pi, Windows, FreeBSD, OpenBSD, and how an update works.
  • Your station. A location and a logbook.
  • Logging. A contact, callbook lookup, the contact itself, search, a contest, and typing a paper log in afterwards.
  • Notes. The station diary, when you have switched it on.
  • Import and export.
  • Awards. DXCC, SOTA, POTA, and the other chases you have switched on.
  • Analytics. The same logbook drawn as charts: months, grids, distances, continents, and the rest.
  • Callsign menu. The menu under your callsign, your account, the bands you use, widgets, and Call History.
  • Radio and the cluster. CAT, Aurora, the DX cluster, and the bandmap.
  • Sending the log elsewhere. LoTW, eQSL, Club Log, QRZ, HRDLog, and QO-100.
  • Handling QSL cards. Uploading a card and marking it sent, received, or requested, then OQRS, printing, and labels.
  • Admin. Users, options, modes, country files, a backup of your log, and the debug page.
  • Developers. How another program talks to Cloudlog, using an API key, and how to write a plugin.

If you would prefer someone else to run the server, magicbug offer hosted Cloudlog.