Rize currently truncates tracked URLs to the root domain (e.g. example.com), stripping the subdomain entirely. This makes it impossible to distinguish between different environments or tools running on subdomains of the same domain.
When Rize displays a tracked website or app, it only shows the root domain — the subdomain is cut off. For example:
I visit n8n.example.com
Rize shows example.com
This is a problem anywhere domain names appear in the UI, including:
Calendar view → Activities column — subdomains are not visible in the activity list
Review Time Entry — the domain shown doesn't reflect the actual subdomain visited
Any other place across Rize where domain names are displayed
Primarily developers and technical users who rely heavily on subdomains — for example:
Staging vs. production environments (staging.client.com vs. client.com)
Self-hosted tools running on subdomains (n8n.example.com, grafana.example.com)
Multiple client projects each on a different subdomain of the same root domain
For these users, the root domain alone carries no useful information — the subdomain is what identifies the context.
Add an opt-in setting (off by default) that enables full subdomain display across the entire Rize UI. Users who don't use subdomains wouldn't be affected.
Does Rize currently use the subdomain as part of keyword matching when auto-assigning tasks, clients, or projects? If not, it would make sense to also include subdomains in that matching logic — so that n8n.example.com and example.com can be treated as separate entities and assigned to different projects or clients.
Low implementation complexity (display change + optional setting), high value for developer users. Subdomains are a standard part of how web infrastructure is organized — not an edge case.
Please authenticate to join the conversation.
In Review
Feature Request
About 5 hours ago

Matúš Karak
Get notified by email when there are changes.
In Review
Feature Request
About 5 hours ago

Matúš Karak
Get notified by email when there are changes.