Fugu

fugu.lol ↗

Count product events and inspect their properties in a small self-hosted analytics app.

SI Score
75/100
Pricing
Free AI reading, not confirmed
Free plan
Yes AI reading, not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about Fugu

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Fugu homepage

What it does

Fugu collects named events through an API and breaks them down by supplied properties or time periods. It focuses on a limited product-analytics workflow rather than broad user-profile reporting.

A completed document export can carry a format property in Fugu; counting export-button presses would answer a different question. The event API accepts the event name, properties and an API key. Reports break those events down by property and aggregate them by day, week, month or year.

Fugu does not track unique users. An event total counts actions, so ten exports can include repeated work by one person. Saved dashboards, complex reports, external integrations and single sign-on are outside its deliberately small feature set.

The application is free and distributed under the GNU AGPL version 3. Hosting is the user's responsibility. Its setup uses Ruby on Rails and PostgreSQL, with a Docker Compose route that includes the database and migrations.

After deployment, open the application's URL and create a local user account. Initial administrator credentials can also be supplied through the documented environment variables. The hosting guide recommends disabling public registration after that account is created.

Strengths

  • Keeps event and property analysis focused.
  • Provides a documented, free self-hosting route.

Watch out for

  • Does not track unique users or provide saved dashboards and external integrations.
  • Requires operating the application and PostgreSQL database.

Best for

  • Small product teams wanting self-hosted counts of defined actions

Sources