Keypup retrieves data from your GitLab account

Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Slack) your dev team uses. Connect my GitLab
We fetch the following entities
Comments: used for display in the dashboard
Issues: used for display and auto-linking to merge requests. Due dates on issues are factored when evaluating the due date of related merge requests.
Labels: used for display in the dashboard. Labels on issues are also applied on related merge requests.
Milestones: used to retrieve the due date of items.
Merge requests
: used for display on the dashboard. Merge requests can reference issues via auto-linking (title or description) and nest them in the Priority Inbox.
Merge request approvals (GitLab paid edition): used to evaluate the review/approval status of merge requests and recommend actions.
Using GitLab free edition? See how you can still adopt an approval workflow using Keypup.
Merge request build status: used to evaluate the readiness of a merge request and recommend actions.
Suggested reviewers: used to detect who are the reviewers of a given merge request. If reviewers are on Keypup then the item will appear in their Priority Inbox.

Security matters!

Keypup does not fetch, copy, duplicate, modify or store any parts of your source code. Keypup only accesses metadata such as pull requests, issues, milestones etc.

Our products support single sign on (SSO) via the repositories for authentication. It is the only way for users to access the Keypup platform.

We understand that security is critical, and we follow best practices and strict procedures to keep our systems, and your data, safe. We perform regular penetration testing and audits of Keypup and its infrastructure.

See our full security policy here

Connect my GitLab