Skene Cloud

Skene Cloud maps your customer journey from what your product actually does. Connect a GitHub repository and a Supabase project: Skene reads the tracking calls in your code and the tables in your schema, builds the journey from them, and shows you what's tracked, what's missing, and what breaks when the code changes.

New here? The Quickstart walks you from signup to your first journey analysis.

How it works

Connect sources -> Analyze -> Work the lifecycle -> Plan features -> Keep tracking honest

1. Connect your sources: a GitHub repository so Skene can scan your codebase for analytics events and tracking calls, and a Supabase project via OAuth (read-only: your schema, never row data). Prefer the terminal? Push a journey from the skene CLI instead.
2. Analyze. Skene introspects your schema, matches it against the events in your code, and generates your customer lifecycle: stages, steps, and the evidence behind each one.
3. Work the lifecycle. Edit the canvas on the Lifecycle page and keep a list of the questions your data should answer. Events shows which steps have tracking and which don't; Flows shows how users actually move through your product.
4. Plan the next feature. Before you ship, write a plan: what the feature should change, which questions the data has to answer, and which events must exist. Skene checks those requirements against your code, so the missing event turns up before launch.
5. Keep it honest. Turn on PR reviews so every pull request is checked for removed or broken tracking, and ask questions from your coding agent (over MCP).

Documentation

Setup

• Quickstart: Signup, connecting your sources, first journey analysis
• GitHub Integration: Link a repository, app permissions, PR reviews
• Supabase Integration: Connect your project read-only, schema grounding

Using Skene Cloud

• Lifecycle & Analysis: Analysis runs, the lifecycle canvas, questions
• Events: Every code and database event in one filterable table, gaps counted
• Plans: Make one product change measurable before you launch it, then check whether the metric moved after
• Flows: How users actually move through your product, captured by one script tag

Administration

• Workspace: Members, API keys, connections

Optional

• Automations: Rules that react to changes in your database, deployed as Postgres triggers (read-write mode)
• Logs: Monitor automation events and decisions

Related

• skene CLI: Analyze codebases locally and push journeys from the terminal