Projects and sources

Project

A project is one real thing you ship and care about as a unit — an app, a SaaS, a website, a service, or a combination. Grill Me is a project. So is Last30, which is a website and an iOS app.

A project is the umbrella under which all of its sources are grouped. It has a name, an icon, platform labels, a Pulse, metrics, events and attention items. It is always your record: when Ubrella says “project”, it never means something RevenueCat or PostHog calls a project.

Source

A source is one thing discovered inside a connected provider that belongs to a project:

Project: Grill Me                  iOS · Web
├── Source  RevenueCat   Grill Me
├── Source  GitHub       grill-me            (olivermark)
├── Source  GitHub       grill-me-api        (olivermark)
└── Source  PostHog      GrillMe Production

Sources are discovered through an integration and assigned to a project by you. Every metric and event Ubrella stores carries the source it came from, so you can always trace a number back.

Platform

A platform is a label on a project: iOS, Android, Web, Website, API. A project can carry several. Platforms are descriptive — they never hold sources and never split numbers. If you want revenue per store, that comes from the RevenueCat source’s own breakdown, not from a platform.

Unassigned source

A source under no project. Visible, assignable, silent: no metrics, events or attention items until it is assigned.

Why the words matter

RevenueCat, PostHog and Vercel all call their things “projects”. If Ubrella did too, project_id would mean two different things and every conversation would start with “which kind?”. So inside Ubrella there is exactly one kind of project — yours — and everything from outside is a source. The glossary lists every term.