Is there any plan for self-hosted generic OpenID authentication?

I see that there is an outstanding PR (#192) for this, but it has stagnated to the point that it is no longer a trivial merge.

Clarify self-hosted feature policy and remaining IS_CLOUD UI gates

## Question

Mobile app tracking: app version, device model, and site icons

> **Updated 2026-08-06.** Most of what this issue originally proposed now ships in Rybbit itself. v2.7 added the mobile site type and the React Native SDK, so #921 was rebuilt on top of `master` (v2.8.0) and only keeps the parts upstream does not cover. The original scope is kept at the bottom for context, but the sect

Self-host: Query and Dashboards missing from sidebar since v2.9 (NEXT_PUBLIC_DEPLOYMENT baked empty in published client image)

### Describe the bug

Show the Integrations (Google Search Console) tab on self-hosted when Google OAuth is configured

First off - thanks for Rybbit. The self-hosting story is genuinely good, and getting an instance up behind our own ingress was painless.

[Feature Request] Cloud data export.

Hi! Thanks for this amazing project! Appreciate all the time and effort. I want to kindly ask if there is a way to export data from the free service? I am self-hosting a rybbit instance, and would love to export data from the free service and merge into my own instance.

Configurable data retention for events (default: none)

**Is your feature request related to a problem? Please describe.** On self-hosted instances, the core `events` ClickHouse table (and its `sessions_mv_target` rollup) has no TTL — pageview/event data, including the raw `ip` column, is retained indefinitely by default. By contrast, `session_replay_events`/`session_replay

Events generated on scroll

I have a SPA built with Zensical (https://doco.cd/). In the events view there is a new Pageview event appearing every time someone just scrolls on a page, even when the URL does not change.

@rybbit/node: all events rejected with 400 "Unrecognized key(s) in object: 'api_key'"

**Describe the bug** `@rybbit/node` (1.0.0, the latest published version) no longer works against the current backend. Every `pageview()` / `event()` call is rejected with HTTP 400 because the SDK sends `api_key` in the JSON body, and the tracking payload schemas are now `.strict()` and no longer contain `api_key`:

Rybbit instance shows "New Update" banner before release exists

**Describe the bug** The rybbit ui seems to show the update hint too early. I just noticed the update banner to 2.9.1

First visit is the earliest event in the selected range, on Users and on Retention

**Describe the bug**

Embedded widget does not show any data

**Describe the bug** When creating a new embedded widget, no data is shown. I'm self hostng Rybbit with Dokploy, I have set it up with a custom subdomain, everything works just fine except for this widget. In the environment variables I have set up DOMAIN_NAME and BASE_URL. The embedding script itself looks fine:

Support Cloudflare visitor location headers with GeoLite2 fallback

## Feature request

feat: saved segments (named, reusable filter sets)

## Summary

feat: timeline annotations on the overview chart

## Summary

feat(date-selector): two-pane picker with typed dates and times

## Why

Alias/merge endpoint to stitch an anonymous identity to an account on login

**Is your feature request related to a problem? Please describe.**

Umami export/import format

Hey there,

feat(storage): support any S3-compatible provider for session replays

# feat(storage): support any S3-compatible provider for session replays

feat(clickhouse): Add ability to use custom clickhouse user

## Why should this be accepted?

Enhance Docker entrypoint and update migration process

- Added a wait mechanism for PostgreSQL readiness in the Docker entrypoint script to ensure the database is available before running migrations. - Changed the migration command from `db:push` to `db:migrate` for improved migration handling. - Updated Dockerfile to include the drizzle directory, ensuring all necessary

Clickhouse does not prune session replays after the set amount of days

I connect Rybbit to a site with around 8mn events/month, and have session replays enabled. The VPS I host on has 160 GB disk space, which I figured out handles 2 days of sessions replays, so I set: