Alpenglow

Menu

Lights what moved.

AI analytics that reads every metric overnight.

Request access

Concept project by al. Fictional product and data.

Alpenglow is the light that touches the highest peaks first. Your morning should work the same way.

This morning’s reading

Sample workspace, Tuesday at 06:40. Three findings out of 2,140 metrics, each with its cause and its size.

Renewal rate, GermanySample data
Yesterday
74.6%
Usual
91.2%
Declined
212 of 1,277
At risk this week
€184,000

German renewals fell

212 invoices went out without VAT numbers after Friday’s billing change.

Checkout conversion, iOSSample data
Yesterday
44.6%
Usual
38.2%
Weekly sessions
41,250
Gain per week
2,640 purchases

iOS checkout climbed

Yesterday’s one-page checkout added 6.4 points. Android has not changed.

Support tickets, CRM syncSample data
Yesterday
132
Usual
63
Extra tickets
69
Accounts affected
38

CRM tickets doubled

A vendor API change broke contact sync for 38 accounts.

Every metric, last nightSample data

The other 2,137 stayed dark

They moved inside their usual range, so they get no alert and no paragraph.

First it reads all 2,140 metrics

What it reads, and when

Sample night schedule: 2,140 metrics read between 00:00 and 02:10
MetricsSourceCountRead between
Money, 612 metrics
RenewalsBilling14800:00–00:14
New contractsBilling9600:14–00:23
Refunds and creditsBilling8400:23–00:31
Invoices and dunningBilling13200:31–00:43
Revenue by planWarehouse15200:43–00:57
Product, 884 metrics
Sign-up and activationEvents21400:57–01:08
CheckoutEvents17801:08–01:17
Feature useEvents33601:17–01:34
Speed and errorsLogs15601:34–01:42
Support, 236 metrics
Tickets by integrationHelp desk12401:42–01:49
Time to first replyHelp desk7201:49–01:53
SatisfactionSurveys4001:53–01:56
Marketing, 408 metrics
Paid channelsAd accounts24401:56–02:05
Organic and referralAnalytics16402:05–02:10

One price

Per workspace, billed monthly. Sample figures.

Questions

Does our data leave our warehouse?

No. Alpenglow runs its queries inside your warehouse through a read-only role. The model receives aggregates and metric names, never customer rows.

Why only three findings?

Three is the limit we set, so each one gets a cause, a size and an owner. The rest wait in an appendix you can open.

What if nothing moved?

The reading says so in one line. Some mornings have no findings, and those are good mornings.

How does it decide what is normal?

Each metric gets its own seasonal baseline from at least 13 months of history. You can pin known events, such as a launch or a price change.

Can we check how it reached a finding?

Yes. Every finding links to the SQL it ran and the metrics it ruled out, so your analysts can repeat it.

How is this different from a dashboard?

A dashboard lights everything and waits for you to look. Alpenglow does the looking and shows you what changed.

Tomorrowat 06:40?

or See the reading

Your first reading arrives within a week of connecting.