Getting started

Connecting your repositories

Scryable reads your git history to surface engineering intelligence. Setup takes a few minutes. No agents to install, no webhooks to configure, and no changes to your existing workflow.

What Scryable reads

When you connect a repository, Scryable reads commit metadata: the SHA, timestamp, branch name, author name, author email address, commit message, and the number of lines added and deleted in each commit.

Scryable does not read your source code. File contents, diffs, and intellectual property in your codebase are never accessed or stored. Everything in the dashboard is derived entirely from metadata.

Author names and email addresses are personal data under UK GDPR. If you're an engineering manager connecting team repositories, you're responsible for ensuring your developers are aware that this analysis is taking place. See our privacy page for more detail.

Connecting your first repository

From your dashboard, select Add repository and authenticate with GitHub. Scryable will request read-only access to the repositories you choose. You can connect multiple repositories and filter between them at any time.

Once connected, Scryable reads the full git history for paid repositories, or the most recent 90 days for repositories on the free tier. The initial import typically completes within a few minutes for most codebases.

Your repositories appear in the sidebar filter immediately after import. Any commits pushed after connection are ingested automatically.

Setting your pre-AI baseline

The pre-AI baseline is the most important configuration decision you'll make in Scryable. It's the date you started using AI coding tools across your team. Every metric in the dashboard is shown both for the current period and against this baseline, so you can see what has actually changed since AI adoption began.

The baseline date is visible in the top bar of your dashboard. To set or update it, go to Settings and choose Pre-AI baseline date.

How to choose the right date. Pick the date when AI coding tools (Copilot, Cursor, Claude Code, or similar) became part of your team's regular workflow, not when you first enabled a licence. If adoption was gradual across different team members, use the date when the majority were actively using tools. A rough date is more useful than no date.

If you're unsure of the exact date, look at your git history for the period when commit volume or line change patterns shifted noticeably. That's often a reliable signal of when AI tools started influencing output.

Free tier and paid repositories

Your first repository is free, permanently. Paid repositories are billed at £10 per repository per month from the date of connection.

Free tier repositories display the most recent 90 days of history. Paid repositories display the full history from connection date. Disconnecting a repository removes its data from your dashboard within 30 days. If you reconnect it later, history is re-imported from scratch.

What happens next

Once your repositories are connected and your baseline date is set, your dashboard will show the full picture: commit volume, line change trends, churn ratio, and per-author breakdowns, all compared against your pre-AI baseline.

Start with the Metrics explained page to understand what each number means before drawing conclusions.