We built helloLOG because we needed it ourselves

The problem

Activity logging for WordPress isn't a new idea — established plugins have done it for years. The trouble is how they do it: they write every event straight into your WordPress database. On a busy site that's a table that keeps growing, more rows to back up, and one more thing for wp-admin to query every time someone loads a screen.

There's a sharper problem underneath that. If the log lives in the same database as the site, an attacker who compromises that site can see — and sometimes edit — its own audit trail. The evidence sits on the machine that just got broken into.

We looked for a plugin that solved both halves of that: works well as an activity log, and doesn't make the WordPress site itself worse to run. We didn't find one, so we built it.

Who we are

We're WordPress developers. We originally built helloLOG for ourselves — to keep track of what happens on the sites we run and maintain for our clients. Our clients liked it so much that we decided to open it up to everyone.