Scryable Support

Go to Repositories and click + Add repositories. A picker lists every repo your connected account has access to. Select one or more and click Connect & start sync. The initial sync begins immediately.

The number of repositories you can connect depends on your plan: 3 on Free, 10 on Pro, unlimited on Business.

It depends on the size of the repository's git history. Small repos (a few hundred commits) typically complete in under a minute. Larger repos with several years of history may take a few minutes. The dashboard becomes available once the first commits have been ingested, so you don't need to wait for the full sync to complete.

The most likely reason is that it hasn't been added yet. Once you've authorised a provider, Scryable holds a token that can request any repo your account has access to at any time, so there's no need to re-authorise when new repos are created. Go to the Repositories page and use + Add repositories to find and connect it.

For organisation-owned repositories, check that Scryable has been granted access to the organisation in your GitHub, Bitbucket or GitLab OAuth settings. Organisation admins may need to approve third-party access separately.

Scryable requests read-only access to your repositories. It reads git commit history, author metadata, and pull request data where available. It does not access your source code content, only the structural data in commit objects: timestamps, authors, line counts, commit messages, and PR state.

Scryable never writes to any repository and never accesses any repository you have not explicitly connected.

From the Repositories page, click Sync on the repo you want to update. This fetches any new commits since the last sync and your dashboard will reflect the updated data once it completes.

Scryable does not currently run automatic background syncs. You control when data is refreshed.

An auth error means Scryable has lost access to that repository. This usually happens when your GitHub or GitLab OAuth token has expired or been revoked, or when your permissions for that repo have changed.

To fix it, go to the Repositories page and click the Reconnect button on the affected repository. Once the connection is restored, syncing will resume.

Removing a repository is permanent. All commit history, contributor data, and PR data for that repository are deleted from Scryable's database. Any saved reports that included that repository will have it removed from their filter configuration.

The removal confirmation screen shows you exactly how many commits, PRs, and saved reports will be affected before you confirm.

No. Removal is a hard delete and we don't retain the data after you confirm. If you want the repository back in Scryable, reconnect it from + Add repositories and it will re-sync from your git history.

If you downgrade your plan, repositories connected beyond your new plan's limit become locked. They remain visible in your list but their data no longer appears in the dashboard or reports.

Locking is based on connection order, so the most recently added repositories are locked first. To unlock one, either upgrade your plan or remove another connected repo to bring the total within the new limit.

The AI baseline date marks when your team started using AI coding tools. Setting it tells Scryable where to draw the dividing line in your git history. Everything before is the pre-AI period; everything after is post-AI.

Once set, every metric in the dashboard shows both periods side by side with deltas, so you can see exactly how your team's patterns have shifted since AI tooling was introduced. Without it, the dashboard shows aggregate history only.

The AI baseline feature is available on Pro and Business plans.

Go to Repositories and find the AI Baseline card on the right side of the page. Enter a date in the global baseline field and click Save. This applies across all connected repositories by default.

You can also set per-repository overrides from the same card, which is useful when different teams or services adopted AI at different times.

Yes. Per-repository overrides let you set a different baseline date for specific repositories. The dashboard uses that date for all metrics on that repo, and the global baseline for everything else.

Manage overrides from the AI Baseline card on the Repositories page. Each override shows the repo name, the date, and a remove button. Add a new override using the inline + Add form.

Every metric calculated for the current (post-AI) period is shown alongside its pre-AI equivalent for the same contributor or team. The delta tells you whether the metric is up, down, or stable since your baseline date.

Metrics covered include commit volume, commit size, cadence, churn, and PR cycle time. The comparison helps you answer the question most engineering teams are now asking: is AI tooling making our code better, faster, or neither?

Set up the dashboard with your chosen repositories, date range, authors, and any other filters, then click Save report in the dashboard toolbar. Give it a name and confirm. The report is saved to your Reports page and can be reopened at any time.

Reports are saved filter configurations, not static snapshots. They always show fresh data from your latest sync. Saved reports require a Pro or Business plan.

Git commits are authored using whatever name and email is configured in a contributor's local git settings. If someone commits from two machines, two email addresses, or both a work and personal account, Scryable sees them as separate identities by default.

To merge them, click the Contributors button at the top right of the dashboard. From there you can assign multiple git identities to a single display name, and all metrics will be aggregated under that name. This is particularly useful for teams where contributors' identities aren't consistent across repos.

Toggling outlier filtering hides statistically large commits from charts and lists. You can choose to filter at the 95th or 99th percentile by commit size. This reduces visual noise caused by one-off large commits such as dependency additions, generated file changes, and data migrations, so typical working patterns are easier to read.

The filter is purely visual and doesn't delete any data. Toggle it on or off from the dashboard toolbar.

Churn refers to commits with a high ratio of additions and deletions relative to net change: lines written and then rewritten or removed in quick succession. High churn often indicates rework and code that didn't survive long enough to be useful.

This matters in the context of AI tooling because research (GitClear, 2025) shows AI-assisted commits have on average 2× higher churn rates than human-authored commits. Scryable surfaces churn rates per contributor so you can see if this pattern is showing up in your own codebase.

Burstiness measures how unevenly distributed a contributor's commit activity is over time. A high burstiness score means commits cluster in short, intense windows separated by quiet periods. A low score means activity is spread more evenly.

Neither is inherently better. Context matters. The value is in spotting changes over time, particularly relative to each contributor's own pre-AI baseline.

The heatmap in a contributor's profile visualises when they commit, broken down by day of the week and hour of the day. Darker cells indicate higher commit activity at that time. It's a quick way to understand someone's working rhythm: when they're most productive, whether they commit on weekends, and whether their patterns have shifted over time.

Go to Account → Plan & Billing. The plan grid shows your current plan and the options available. Click the upgrade button for the plan you want, choose monthly or annual billing, and you'll be taken to a Stripe Checkout page to complete payment. Your new plan takes effect immediately once payment is confirmed.

Go to Account → Plan & Billing and click Manage in Stripe portal ↗. From there you can update your payment method, download invoices, change your billing cycle, and cancel your subscription.

Cancellation takes effect at the end of your current billing period. You keep full access until then. After that, your plan reverts to Free and any repositories beyond the Free limit will become locked.

Your data is not deleted when you downgrade. Only access to certain features changes:

• Repositories over the new plan's limit become locked (data retained, not shown).
• AI baseline settings are preserved but the before/after comparisons are not visible on Free.
• Saved reports are preserved but can't be opened or created on Free.

Upgrading again immediately restores everything.

On Business, one account (the leader) can cover other Scryable users under a single subscription. Each covered team member gets full Business-plan access (unlimited repos, AI baseline, and saved reports) without needing their own paid subscription.

Billing is per user via Stripe. When you add a member, your subscription quantity increases by one and you're charged the pro-rated difference for the remainder of the billing period. When you remove a member, the change takes effect at the start of the next billing cycle.

Each team member keeps their own separate Scryable account and data. There is no shared workspace.

Go to Account → Team. Enter the GitHub or GitLab username of the person you want to invite and click Send invite. Scryable autocompletes from contributors already visible in your connected repos.

If the person already has a Scryable account, they're added immediately and your user count increases. If they don't, the invite stays pending until they sign up, at which point it's accepted automatically.

You get full Business-plan features at no cost to you. Your Account → Plan & Billing page will show a "Covered by @username" badge. Your own account and data remain yours and nothing is shared with the person covering you.

If you already had a paid plan when you were invited, your subscription is paused for the duration of the coverage and resumes automatically if you're removed from the team.

No. Scryable reads the structural metadata in your git history: commit timestamps, author names and emails, line change counts, commit messages, branch names, and PR state. It does not access or store the content of any file in your repository.

This means Scryable works fine with private, proprietary codebases. The data it holds would not be meaningful to anyone who didn't already have access to your repository.

For each connected repository, Scryable stores:

• Commit SHA, timestamp, author name and email, commit message, line additions and deletions.
• Pull request number, title, state (open/merged/closed), and dates where the provider makes this available.
• Derived contributor identities based on the author name/email combinations found across commits.

No file contents, diffs, or code are stored. Your account settings, saved reports, and AI baseline configuration are also stored.

Go to Account → Profile and scroll to the danger zone at the bottom. Click Delete account and confirm. This permanently deletes your account and all data associated with it: repositories, commits, saved reports, and billing records.

If you're a Business leader with active team members, their memberships are revoked and their own subscriptions (if any) are resumed before deletion completes. Account deletion is immediate and irreversible.

Our full privacy policy is available at scryable.com/privacy. It covers what data we collect, how it's stored, how long we retain it, and your rights under GDPR and applicable regulations.