Everything your team needs
Built for engineering teams that need more than a backlog dump.
How it works
You
Connect your repo
Link GitHub in 2 minutes.
Gate reads signals immediately.
You
Define objectives
Set measurable goals.
Stale PRs, lead time, alerts.
Gate
Govern and plan
Gate classifies work
and plans what to ship next.
What you get
Objectives, not opinions
Define measurable delivery goals — stale PR thresholds, lead time targets, alert resolution. Governance becomes quantifiable.
Live repo signals
Gate continuously reads your repos — open alerts, merge times, stale PRs — and maps signals to your objectives in real time.
Governance-informed plans
Gate recommends what should move next based on your current objectives and signals. Not a backlog dump — a plan.
A PR arrives. Gate decides what it means.
Gate reads signals, classifies work, and surfaces what should move next.
Signal · Classify · Plan
Live repo state
From GitHub metadata only
Decision funnel
Objective: lead time < 3d + alerts
Governance plan
What to ship next, and why
fix: auth token scope (#341)
security alert → high priority
fix: stale session clear (#317)
stale 9 days → over threshold
chore: dep bump (#329)
lead time objective
Every PR gets a verdict.
Work that belongs here moves. The rest is governed, not forgotten.
* Illustrative example — Gate connects to your live repo on setup.
Frequently asked questions
What is the difference between Gate and Sweep?
Sweep is an execution engine — it automatically merges safe pull requests and flags risky ones. Gate is a governance layer — it helps you define objectives, monitor signals, classify work, and generate plans. Sweep moves work forward. Gate decides what should move.
Do I need Sweep to use Gate?
No. Gate and Sweep are independent products. You can use Gate on its own to govern your backlog and track objectives. You can use Sweep on its own to automate PR merging. When used together, Gate's governance decisions can inform where Sweep focuses its execution.
My backlog is chaotic — does Gate help with that?
Yes. Gate is specifically designed for teams with noisy backlogs. It replaces ad-hoc triage with signal-based governance: you define what matters (objectives), Gate classifies incoming work against those objectives, and surfaces what actually deserves attention. Work that doesn't match any active objective is explicitly marked out of scope — not lost, governed.
What kind of objectives can I set?
Gate comes with templates for common objectives: keeping merge lead time under a target, reducing stale PRs, resolving security alerts, and maintaining CI reliability. You can also define custom objectives with your own metrics and thresholds.
How does the decision funnel work?
Gate classifies incoming pull requests through a multi-stage funnel based on your active objectives. PRs are categorized as incoming, evaluated, in scope, or actionable. Work that doesn't match any active objective is explicitly marked out of scope — not ignored, but governed. The plan output shows you exactly which PRs Gate recommends moving next and why.
Does Gate read my source code?
Gate reads pull request metadata, file paths, diff statistics, branch references, and CI status — the same data model described on our Trust page. It does not store source code. See /trust for full details.
How quickly can I get started?
About 2 minutes. Connect your GitHub account, select a repository, and Gate starts pulling live signals immediately. Use one of the built-in objective templates to define your first governance goal, or create a custom one.
What happens to work Gate marks out of scope?
Out-of-scope PRs are not deleted or hidden — they stay in your repo. Gate marks them explicitly so your team knows they were reviewed against active objectives and didn't match. When your objectives change, Gate re-evaluates them automatically.
Governance,
not guesswork.
Gate reads signals, classifies work, and surfaces what ships next.