Sync
Once a day
Section titled “Once a day”Ubrella runs one complete sync per day for your workspace, at 06:00 in your time zone. Every integration is read, metrics and events are normalised, snapshots are written, attention rules are evaluated, and the daily brief is generated.
There is no polling in between and there are no webhooks yet.
What that means for you
Section titled “What that means for you”- A build that fails at 14:00 is in tomorrow’s brief. If you need to know within minutes, GitHub’s own notifications remain the right tool — Ubrella is the morning view, not the pager.
- Every timestamp in Ubrella is a sync day: today, yesterday, Thursday. You will never see “37 minutes ago”, because nothing in Ubrella is 37 minutes old.
- Numbers are consistent across the whole portfolio. Everything on the screen is from the same moment.
What a sync stores
Section titled “What a sync stores”| Concept | What it is | Example |
|---|---|---|
| Metric | a normalised number for a project over a period | revenue · 7d · €312 |
| Event | something that happened at a specific moment | PR #182 merged |
| Snapshot | the set of a project’s metrics for one day | 19 Sep 2026: revenue €44, users 1,284, open PRs 0 … |
Ubrella keeps aggregates, not raw data. A PostHog project with millions of events contributes a handful of counts per day. Source code, customer records and payment details are never read.
Failures
Section titled “Failures”If a provider cannot be read — rate limit, outage, expired token — the sync continues with the others, and an attention item in the integration category is opened for every project with a source from that integration. It resolves itself when the next sync succeeds. You can trigger a manual sync from Settings → Integrations, at most once per hour.
What is planned
Section titled “What is planned”Faster paths for GitHub — 15-minute polling first, then webhooks — are the first upgrade after the beta. They will only add an inbound path: the rules, the brief and the Pulse will not change.