Skip to content
Get started

Live demo · no signup

Take ROOKON for a test drive.

This is a working workspace for a fictional product, Acme Cloud. Everything is clickable, and all data is simulated. Nothing here is real customer data.

Hi, I’m Rooky! I’ll show you around. Click anything, you can’t break it.

1 · Watch the autopilot

Rooky: Pick an issue and I’ll take it from the first signal to a pull request. You stay in charge of every step.

rookon · acme-cloud / production · autopilot

Simulated data

Product health

Live

Health

86/100

Error rate

0.42%

Active users

1,284

Errors · last 24 h

Detected issues

Autopilot run

  1. 1

    Detect

  2. 2

    Investigate

  3. 3

    Analyzevia your AI provider

  4. 4

    Propose fix

  5. 5

    Your review

Select an issue or press Run to watch ROOKON investigate it.

2 · Explore the workspace

Rooky: This is Acme Cloud’s workspace. Click around: the numbers move like they would on a real product.

app.rookon · acme-cloud / production

Simulated data

Overview

Live

Health score

86/100

−6 since v2.14.0

Error rate

0.42%

5× baseline

p75 LCP

2.1 s

Good < 2.5 s

Conversion

3.8%

Upgrade flow

Errors / hour ▲ spike at 12:00

Active users 1,284 now

Needs attention

3 · Swipe through ROOKON’s commit requests

Rooky: These are fixes I prepared. Swipe right to approve, left to ask for changes. Empty the deck and I’ll take a nap.

rookon · acme-cloud · commit requests

Simulated data
Livenew requests arrive while you review
6-day streak2 reviewed today0/6

#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+3 tests typecheck unit tests build

4 · Read your traffic, without cookies

Rooky: Visitors, sessions and conversions, counted without cookies.

rookon · acme-cloud · web analytics

Simulated data

38 visitors nowLive

Bounce rate38.0%▼ 7.5% vs prev.
Avg. visit3m 23s▲ 12.2% vs prev.

Visitors · 7 days

visitors Previous period
visitors over the last 7 days, compared with the previous period
TimevisitorsPrevious period
6 Nov1,3111,260
7 Nov1,025826
8 Nov975921
9 Nov1,4941,442
10 Nov1,3791,474
11 Nov1,6091,391
12 Nov1,4421,432

Click a row to filter everything above.

Right now

38

visitors in the last 5 minutes

Visitors per minute, last 30 minutes
Timevisitors / min
16:3011
16:3111
16:3213
16:3315
16:3416
16:3513
16:3613
16:3719
16:3812
16:3913
16:4015
16:4111
16:4212
16:4312
16:4412
16:4510
16:469
16:4710
16:489
16:4910
16:5011
16:514
16:526
16:538
16:5410
16:557
16:568
16:5710
16:5810
16:5916
  • /12
  • /pricing7
  • /features4
  • /blog/launch-week3
cookieless

No cookies or device storage. Visitors are counted with a salted hash that rotates daily, so they can’t be followed across days. Raw IP addresses are never stored.

5 · See what every change did

Rooky: After every change I compare before and after. If it was better before, I’ll say so and offer to 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

conversion rate on /billing over 60 days, with change markers
Timeconversion rate
14 Sept3.1%
15 Sept3.1%
16 Sept2.7%
17 Sept2.5%
18 Sept2.5%
19 Sept2.4%
20 Sept2.5%
21 Sept2.8%
22 Sept2.7%
23 Sept2.7%
24 Sept2.9%
25 Sept2.9%
26 Sept2.9%
27 Sept3.0%
28 Sept2.9%
29 Sept3.2%
30 Sept3.5%
1 Oct3.4%
2 Oct3.6%
3 Oct3.7%
4 Oct3.5%
5 Oct3.6%
6 Oct3.5%
7 Oct3.4%
8 Oct3.7%
9 Oct3.3%
10 Oct3.1%
11 Oct3.5%
12 Oct3.8%
13 Oct3.9%
14 Oct3.7%
15 Oct3.2%
16 Oct3.6%
17 Oct3.9%
18 Oct3.9%
19 Oct3.7%
20 Oct3.7%
21 Oct3.8%
22 Oct4.4%
23 Oct4.6%
24 Oct4.5%
25 Oct4.3%
26 Oct4.3%
27 Oct4.3%
28 Oct4.4%
29 Oct3.9%
30 Oct3.7%
31 Oct3.6%
1 Nov3.7%
2 Nov3.8%
3 Nov3.7%
4 Nov3.7%
5 Nov3.8%
6 Nov3.7%
7 Nov3.7%
8 Nov3.6%
9 Nov3.7%
10 Nov3.6%
11 Nov3.7%
12 Nov4.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.

  • MetricBeforeAfterChangep (adj.)Verdict
    Conversion · Upgrade completed2.75%3.49%+0.7 pp0.027 Improved
    Bounce rate40.3%36.1%−4.2 pp<0.001 Improved
    Avg. session duration2m 31s2m 28s−3 s0.294 No significant change
    Sessions per day491464−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.

6 · Set up with a guided journey

Rooky: When you sign up, I guide you through setup one integration at a time.

rookon · setup · acme-cloud

Simulated data

1 · What do you want ROOKON to do?

Level 1 · Getting started

0%

Next: Watching after connect your website.

Unlocked

Nothing yet. Connect your website to start.

2 · Your setup path

about 10 min left (estimate)
  1. 1Connect your website

    Everything starts with data. Add one script tag and ROOKON starts watching.

    <script defer src="https://api.rookon.example/t.js"
  data-key="pk_demo_placeholder"></script>
    ~3 min (estimate)
  2. 2Monitor your API routesoptional
  3. 3Add an alert channeloptional
  4. 4Pick goals and funnels
  5. 5Connect your AI provider
  6. 6Set your AI budget
  7. 7Install the GitHub appoptional
  8. 8Connect your Shopify storeoptional
  9. 9Connect Google Search Consoleoptional
  10. 10Connect Slackcoming soon

    Get critical issues and new commit requests in a channel of your choice. Available in a later release; it won’t block your setup.

  11. 11Connect your support inboxcoming soon

    Gmail, Outlook, Intercom, Zendesk, Help Scout and Freshdesk are planned. Until then, import a CSV export of your support tickets under Opportunities. Names, emails and numbers are stripped before anything is stored. Available in a later release; it won’t block your setup.

  12. 12Invite your teamoptional
  13. 13Turn on the feedback widgetoptional

Simulated. In ROOKON every step completes when ROOKON verifies the real thing, never because someone ticked a box.

7 · Install with one snippet

Rooky: Pick your framework and copy one snippet. That’s all I need to start learning.

rookon · new project · install

Simulated data

1 · Add the snippet

app/layout.tsx
import Script from "next/script";

export default function RootLayout({ children }) {
  return (
    <html lang="en">
      <body>
        {children}
        <Script src="https://api.rookon.example/t.js" data-key="pk_demo9fK2xQ7mL3vR8tYwB4n" strategy="afterInteractive" />
      </body>
    </html>
  );
}

Client-side navigations are tracked automatically through the History API.

  • no cookies
  • loads with defer
  • respects Do Not Track by default

2 · Verify the installation

Waiting for your first event

Open your site after deploying the snippet. This demo can simulate a first visit.

Simulated. The key and URL above are placeholders. Your workspace shows your own snippet.

8 · Go deeper

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.

Get started with ROOKONExplore live demo