Quickstart
Get from a fresh account to your first journey analysis. The whole setup is four steps, and you only need one connected source to start.
1. Sign up
Go to skene.ai/signup and enter your email. Skene signs you in with a magic link: no password to create, nothing to remember. Click the link in your inbox and you land in your own workspace, created for you on first login.
If a teammate invited you, the same link drops you into their workspace instead. Setup is handled by the workspace owner, so you can skip the rest of this page.
2. Tell us about your company
Setup opens with a short Company step. The answers shape which tracking gaps Skene looks for:
| Question | Options |
|---|---|
| What kind of software do you build? | B2B software, B2C software, Both B2B and B2C |
| What is your role? | Founder / CEO, Engineering, Product, Data / Analytics, Design, Marketing / Growth, Other |
| What best describes your software? | SaaS, E-commerce, Marketplace, Developer tools, Consumer app, Fintech, Other. Optional. |
The first two are required. Click Continue to move on; you can change these answers later under Company profile in Settings → General.
3. Connect your sources
Next, Skene asks you to connect your sources. Your codebase and your database are what Skene checks your analytics against, so this is where the product starts being useful.
Two cards, GitHub repository and Supabase project, each open their own connection dialog. A third option, the Skene TUI, sits underneath them as a link. Any one of them is enough to continue, and Back returns you to the Company step.
Connect a Git repository
Click the GitHub repository card, then Connect Git repository. A popup takes you to GitHub, where you install the Skene GitHub App:
- Pick the account (personal or organization) where your repository lives.
- Choose which repositories the app can access: all of them, or just the ones you select.
- Back in Skene, select the repository you want and click Confirm repository.
Each workspace links one repository. Skene scans it for analytics events and tracking calls, and (once you enable PR reviews) flags pull requests that silently remove tracking. The full flow, permissions, and settings are covered in GitHub Integration.
Connect Supabase
Click the Supabase project card, then Connect Supabase. A popup takes you through Supabase OAuth in read-only mode: Skene reads your schema (tables, columns, types), never row data. Pick the project you want and click Confirm project. Details in Supabase Integration.
Or push from the terminal
The link under the two cards, Install the Skene TUI instead, is for working locally: the skene CLI analyzes your codebase on your machine, builds a journey file, and pushes it to your workspace. The dialog waits for the push and flips to Journey ready once it lands, and the link then reads Journey pushed via TUI.
One source is enough. Any connected source makes the Continue button available. Connecting both the repository and the database gives the analysis the most to work with. At least one is required: Continue stays disabled until something is connected.
4. Continue
Click Continue. Skene takes you to the Lifecycle page and, if you connected a repository or a database, kicks off your first analysis automatically. The result is a customer lifecycle map built from what your product actually does, grounded in your code and schema.
What's next
- Turn on PR reviews. In Settings → GitHub, enable PR reviews so Skene checks every pull request for removed or broken tracking. See GitHub Integration.
- Explore the lifecycle: the canvas and the questions your data should answer.
- Check your events: every code and database event in one table, gaps counted.
- Write a plan in Evaluator: state what your next feature should change and which events must exist, so the missing event turns up before launch.
- Turn on Flows: one script tag, and you see how users actually move through your product.
- Invite your team: members, roles, and API keys.
- Connect your coding agent: point Cursor or Claude Code at your workspace over MCP.
