ROOKON prepares the fix. You swipe right to approve it. Nothing merges without your tap.
rookon · acme-cloud · commit requests
Simulated data
Livenew requests arrive while you review
6-day streak2 reviewed today0/6
#130
Add “Just me” and make “Company size” optional
#129
Batch the customer lookup in /api/reports
#128rookon/fix-legacy-billing-interval → main
Fix upgrade failure for customers with a legacy “yearly” billing interval
low riskconfidence: high+20−1 · 3 files
What happened
“Upgrade to Pro” throws for customers whose browser still stores the old “yearly” interval.
Expected benefit
Customers with the old setting can upgrade again; future missing prices are reported, not silent.
212 users affected typecheck unit tests build
Drag the card, or use ← → ↑ and Z
Pick your Rooky
You decide Rooky’s access level.
Start hands-off and give Rooky more room as his track record grows.
Watch-Rooky
Watches and reports. No pull requests.
Co-RookyDefault
Prepares pull requests. You merge in GitHub.
Trusted-Rooky
One tap merges small, low-risk changes you accepted.
Insane-Rooky
Full autopilot: one tap merges every accepted change that passes your guardrails.
Impact
Every change, measured.
ROOKON compares before and after, and tells you plainly. If it was better before, you can go back.
rookon · acme-cloud · impact of changes
Simulated data
Each change: 14 days before vs. 14 days after.
12 NovLive
Conversion rate · pages ROOKON changed
4.67% →5.85%
+1.2 pp since the first ROOKON change
Bounce rate · same pages
41.4% →38.5%
−2.9 pp since the first ROOKON change
ROOKON changes
2 improved of 3 measured
1 no significant change · 0 worse · 1 collecting
Conversion rate · /billing · 7-day rolling
1.7%3.4%5.0%
#131note#130#129v2.15#128
14 Sept12 Nov
conversion rate on /billing over 60 days, with change markers
Time
conversion rate
14 Sept
3.1%
15 Sept
3.1%
16 Sept
2.7%
17 Sept
2.5%
18 Sept
2.5%
19 Sept
2.4%
20 Sept
2.5%
21 Sept
2.8%
22 Sept
2.7%
23 Sept
2.7%
24 Sept
2.9%
25 Sept
2.9%
26 Sept
2.9%
27 Sept
3.0%
28 Sept
2.9%
29 Sept
3.2%
30 Sept
3.5%
1 Oct
3.4%
2 Oct
3.6%
3 Oct
3.7%
4 Oct
3.5%
5 Oct
3.6%
6 Oct
3.5%
7 Oct
3.4%
8 Oct
3.7%
9 Oct
3.3%
10 Oct
3.1%
11 Oct
3.5%
12 Oct
3.8%
13 Oct
3.9%
14 Oct
3.7%
15 Oct
3.2%
16 Oct
3.6%
17 Oct
3.9%
18 Oct
3.9%
19 Oct
3.7%
20 Oct
3.7%
21 Oct
3.8%
22 Oct
4.4%
23 Oct
4.6%
24 Oct
4.5%
25 Oct
4.3%
26 Oct
4.3%
27 Oct
4.3%
28 Oct
4.4%
29 Oct
3.9%
30 Oct
3.7%
31 Oct
3.6%
1 Nov
3.7%
2 Nov
3.8%
3 Nov
3.7%
4 Nov
3.7%
5 Nov
3.8%
6 Nov
3.7%
7 Nov
3.7%
8 Nov
3.6%
9 Nov
3.7%
10 Nov
3.6%
11 Nov
3.7%
12 Nov
4.1%
Shaded: baseline and after windows of the selected change.
It was better before
“Release v2.15.0: new onboarding checklist”
Bounce rate +2.6 pp (32.9% → 35.5%)
p < 0.001 (Holm-adjusted) · 14 days before vs. after
Either way, ROOKON won’t propose this exact change again. A different approach to the same page is still allowed.
Metric
Before
After
Change
p (adj.)
Verdict
Conversion · Upgrade completed
2.75%
3.49%
+0.7 pp
0.027
Improved
Bounce rate
40.3%
36.1%
−4.2 pp
<0.001
Improved
Avg. session duration
2m 31s
2m 28s
−3 s
0.294
No significant change
Sessions per day
491
464
−5.4%
n/a
No significant change
Overlaps with “Release v2.15.0: new onboarding checklist”, so part of the difference may come from that change.
Observed changes between equal windows before and after each change, tested for significance (two-proportion z-test for rates, Welch’s test for durations, Holm-adjusted, p < 0.05). This shows association, not proof of cause: seasonality, campaigns and other releases can contribute, so overlapping changes are flagged.
ROOKON is an autonomous intelligence platform for SaaS products. It monitors your application, understands how people use it, detects problems before your customers report them, explains them in plain language and prepares the fix, so you spend less time maintaining your product and more time growing it.
How long does setup take?
Connecting your website is one script tag, which the setup guide estimates at about 3 minutes. Everything else (goals, your AI provider, the AI budget, alerts, GitHub) is optional and guided one step at a time, and each step completes itself once ROOKON has verified it works.
Does ROOKON modify my code automatically?
No. ROOKON proposes a change and, when you authorize it, opens a pull request on a separate branch. You accept every change first, and nothing merges without a person tapping Merge. In Co-Rooky, the default, you merge in GitHub yourself; in Trusted-Rooky or Insane-Rooky your tap lets ROOKON perform the merge. Branch protection, checks and required reviews always apply.
Will ROOKON run up my AI bill?
No. Each workspace sets an AI budget: a monthly cap, what ROOKON may analyze on its own and how many automatic analyses run per day. New workspaces start conservatively (critical issues only, at most 3 automatic analyses a day and 1,000,000 tokens a month), the most impactful issues are handled first, and ROOKON reserves the worst case before every call so a single analysis can’t push you over the cap.
Is my data secure?
Security is designed in from the start: tenant isolation on every record, role-based access control, encrypted connections, encryption at rest for credentials, audit logs and configurable data retention. Session data is masked in the browser before it is sent, and sensitive fields are never collected.
How does pricing work?
ROOKON is a monthly subscription priced by monthly tracked users: the users of your product observed in a month (an estimate, since ROOKON uses no cookies), counted across your organization. Team members and projects are unlimited on every plan, optional add-ons can be purchased, and products above 100,000 monthly tracked users get custom pricing.
Stop managing every detail. Start building a better product.
ROOKON watches your product, explains what’s wrong and prepares the fix. You decide what ships.