Is my product growing?

Every number that matters, from every source, in one sentence.

One email when it ships. Nothing else.

  • No backend
  • No account
  • No telemetry
  • Keys stay in the Keychain
Acme App

hourdayweekmonth

  • Active users1.2K+8.1%
  • New users312−2.4%
  • Returning users847+0.9%
  • Signups (db)96+12.5%

+3 more on the dashboard

Read 2m ago · read-only, always

A mock of the Analytic Vibes glance screen.

Try it

Push revenue down. Watch the vanity metrics fail to save it.

Revenue up, errors down, one slip left on the record.

Before: the raw numbers

  • MRRrevenuecat×3€2,580

    last week €2,400+7.5%

  • Active usersposthog1,180

    last week 1,120+5.4%

  • New usersposthog296

    last week 310-4.5%

  • Failed jobssupabase24

    last week 31 · down is good-22.6%

After: the glance

Things are

GROWING

this week.

3 improving 1 worsening · weighted move +7.7%

Computed, not chosen. The app’s own rules, on sample numbers.

How it works

Step 1

Paste a read-only key.

PHPostHogeu.posthog.com · query:read
SBSupabasepublishable key only
RCRevenueCatyour own revenue

Verified with a real query.

Step 2

Pin what matters.

MRR×3rc
Active usersph
Signupssb
Failed jobssb

The top one counts triple.

Step 3

Read one line.

Things are

GROWING

today.

day · read 2m ago

No account, anywhere.

The verdict

Four rules decide the word.

×3
Your top-pinned metric outweighs the rest
±100%
One comeback cannot drown out four steady numbers
< 20
Counts too small to mean anything are excluded
±1%
Below this is noise, not a direction
GROWING
an improvement above 1%
SLOWING DOWN
a regression above 1%
MIXED
real movement both ways that cancels out
FLAT
nothing moved beyond noise
TOO EARLY
the numbers are still too small to read

Improvement, not rise. A falling error count is good news.

Dashboard

Acme App

Good evening, Sam

Acme App

Updated 2 minutes ago

HourDayWeekMonth
7 metrics5 rising2 fallingWeek

Active users

posthog
1.2K +8.1%

Last 12 weeks · peak 1.2K

New users

posthog
312 −2.4%

Last 12 weeks · peak 340

Signups

supabase
96 +12.5%

Last 12 weeks · peak 96

Failed jobs

supabase
4 −38.0%

Last 12 weeks · peak 31

Privacy

What stays on your device, and what leaves itYour API keys, your metrics and the verdict computation all sit inside the device boundary. Read-only queries go out to PostHog, Supabase and RevenueCat. The only other thing that leaves is an anonymous purchase receipt to the App Store, never a key and never a number.YOUR DEVICEKeychain: every API keyYour metrics & historyThe verdict, computed hereWidgets · WatchNo account. No backend. All local.read-onlyPostHogSupabaseRevenueCatApp Storeanonymous receiptnever a key, never a number

Read-only by construction.

service_role keys refused before any request.

Nothing phones home.

No analytics SDK. It sends no events of its own.

Sources

The rest are named, not promised.

PH

PostHog

Available

Active, new and returning users. Top events.

SB

Supabase

Available

Row counts, or a function you wrote.

RC

RevenueCat

Available

Your own revenue, read from the Keychain.

On the roadmap

  • Stripe
  • App Store Connect
  • Sentry
  • Plausible
  • Fathom
  • Umami
  • Cloudflare
  • Vercel
  • Firebase
  • GitHub
  • Google Sheet
  • Custom JSON API

In arrival order. No connector is ever paid.

Everywhere you already look

Home Screen

Things are

GROWING

today.

▲ 3 ▼ 1 · 2m

Things are

GROWING

today.

▲ 3 ▼ 1 · 2m

  • MRR€2.6K+7.5%
  • Active users1.2K+8.1%
  • Failed jobs24−22.6%

Daily digest

Analytic Vibesnow

Things are GROWING

MRR €2.6K, up 7.5% on yesterday.

Best-effort. iOS decides when it runs.

Wrist

Acme App

Things are

GROWING

▲ 3 ▼ 1

iPhone
iOS 26.2+
iPad
iPadOS 26.2+
Apple Watch
watchOS 26.0+

Questions

Does it send my API keys anywhere?

No. Every vendor credential is written to the iOS Keychain on your device and read from there when a query runs. There is no backend to send them to. The app has no server, no account system and no analytics SDK of its own.

Can it change anything in my PostHog or Supabase project?

No. It only ever reads. The PostHog key needs exactly one scope, Query Read. A Supabase service_role key is rejected before any network request is made, because it bypasses row level security and this app has no business holding one.

How does it decide GROWING or SLOWING?

Not by a show of hands. Every pinned metric contributes its actual percentage move, the metric you dragged to the top counts triple, and a number coming back from almost nothing is capped at ±100% so it cannot drown out the rest. Counts below twenty are left out entirely. Three users becoming four is a 33% rise and means nothing.

What if a number going up is bad news?

You say so when you make the card. Errors, refunds and churned accounts are better going down, and telling the app that is what stops it painting a rising error count green or calling it growth.

Do I need an account?

No. There is nothing to sign in to. Your name stays on the device, and support works through a copyable Support ID rather than an email address on a server.

What happens on a new device?

Your subscription follows you. Restore it from the App Store and Pro comes back. Your projects, connections, cards and history do not, because they were never on a server. That is the same decision that keeps your PostHog key off one.

Does it work offline?

The last numbers stay on screen and the widgets and Watch keep showing them, marked as stale rather than silently pretending to be current. Launch never waits on the network, and a failed refresh is never treated as a cancelled subscription.

When does it ship?

There is no date yet, and this page will not invent one. The waitlist is the announcement channel: one email when it is real, nothing before.

Something else? hello@aurenix-cl.com

Stop opening two dashboards to find four numbers.

One email, the day it ships.

One email when it ships. Nothing else.