LogRaker Features Pricing Documentation Blog Download

← Documentation

Supabase Sources

A Supabase source follows the logs of one hosted Supabase project - API requests, Postgres, Auth, Edge Functions, Storage, and Realtime. Add one from the sidebar's + menu ▸ New Supabase Source…, then add a stream per log source you want to watch.

How it works

Supabase has no live "tail" API, so LogRaker polls: on an interval (10 seconds by default, adjustable per stream) it queries the project's logs through the Supabase Management API and appends anything new. Expect entries to appear a few seconds behind live, set by the poll interval - that's the platform's query-only design, not a LogRaker delay.

Personal Access Token

LogRaker authenticates with a Personal Access Token from your Supabase account: in the Supabase dashboard, open Account ▸ Access Tokens and generate one (it starts with sbp_). Paste it into the Token field.

  • The token is stored in your Keychain, never in the source's saved data or a configuration backup, and syncs via iCloud Keychain so the source connects on your other Macs. After restoring a configuration on a machine without iCloud Keychain, re-enter it once.
  • Treat the token like a password: Supabase scopes it to your whole account, not just one project, so anyone holding it can manage all your projects. LogRaker only ever uses it to list your projects and read logs.

Project

The Project field takes the project ref - the 20-character id that forms your project's <ref>.supabase.co domain. You don't have to type it: click Test Connection and LogRaker fills the picker with every project your token can see (and selects it for you when there's exactly one).

Test Connection

Click Test Connection. LogRaker lists your projects with the token. Two outcomes:

  • ✓ Connected - the token is valid; the result names the projects it can see and fills the Project picker.
  • ✗ Test failed - the token was rejected, the network is down, or another error. The message carries the details.

Streams under a Supabase source

Each stream under a Supabase source follows one log source of the project - see Supabase Streams for the source picker, the poll interval, and how seeding on connect works.

© 2026 Thomas Gumz · Native macOS log monitoring Features Pricing Download Documentation Blog Changelog Privacy

Amazon Web Services, AWS, Amazon CloudWatch, and Amazon S3 are trademarks of Amazon.com, Inc. or its affiliates. Google Cloud and Firebase are trademarks of Google LLC. Supabase is a trademark of Supabase, Inc. LogRaker is an independent product and is not affiliated with, endorsed by, or sponsored by Amazon, Google, or Supabase.