Keypup logo blue paw
keypup
pending peer tab

The first automation tool that empowers tech leads

Manage your and your team's Pull Requests, Issues & reports.

Automate follow ups on development items.

Reclaim your own development time.
Sign up for free

Keypup integrates with...

Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
GitHub

Keypup retrieves data from your GitHub account

Connect my GitHub
We fetch the following entities
Comments: used for display in the dashboard
Issues: used for display and auto-linking to pull requests. Due dates on issues are factored when evaluating the due date of related pull requests.
Labels: used for display in the dashboard. Labels on issues are also applied on related pull requests.
Milestones: used to retrieve the due date of items.
Pull requests: used for display on the dashboard. Pull requests can reference issues via auto-linking (title or description) and nest them in thePriority Inbox.
Pull request build status: used to evaluate the readiness of a pull request and recommend actions.
Review requests: used to detect who are the reviewers of a given pull request. If reviewers are on Keypup then the item will appear in their Priority Inbox.
‍Review: used to evaluate the review/approval status of pull requests and recommend actions
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
GitLab

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.
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
Bitbucket

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.
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
JIRA

Keypup retrieves data from your JIRA account

Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Slack) your dev team uses. Connect my JIRA
We fetch the following entities
Comments: used for display in the dashboard
Issues: used for display and auto-linking to pull requests. Due dates on issues are factored when evaluating the due date of related pull requests.
Labels: used for display in the dashboard. Labels on issues are also applied on related pull requests.
Sprint due dates: used to infer the due date of items if they are scheduled in a sprint. Sprint due dates take precedence over item-specific due dates.
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
ClickUp

Keypup retrieves data from your ClickUp account

clickup-logoConnect my ClickUp
We fetch the following entities
Comments: used for display in the dashboard
Issues: used for display and auto-linking to pull requests. Due dates on issues are factored when evaluating the due date of related pull requests.
Labels: used for display in the dashboard. Labels on issues are also applied on related pull requests.
Priority flags: issue priorities are retrieved and displayed as labels priority:<priority_name> in Keypup.
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
Trello

Keypup retrieves data from your Trello account

trello-logoConnect my Trello
We fetch the following entities
Comments: used for display in the dashboard aggregated with all other comments and discussions from all other apps. All in one place for a consistent global visibility.
Cards: used for display and auto-linking to pull requests.
Labels: used for display in the dashboard. Labels on issues are also automatically applied on related pull requests.
Lists: lists are retrieved and displayed as labels list: <list_name> in Keypup.
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
Slack

Make Keybot your new personal assistant with Slack

Slack-logoSign up
What data do we collect?
Users: we fetch the IDs and timezones of users having access to your Slack workspace. We do not fetch personal data such as names and email addresses.
Actions, priorities and reminders
Morning digest: Keypup users on Slack receive a morning digest every day at 9:05am with the top priorities of their Priority Inbox.
Merge recommendations: When pull requests are mergeable, have a green build and have been approved, Keybot will send a notification to project maintainers and propose to merge them.
Asking questions to Keybot: You can ask questions to Keybot to get an update on pull requests and issues.
feature-carousel-6
icon-close-thin
Our platform integrates with your repositories (GitHub, GitLab) and project management tools (Jira, ClickUp, Trello, Slack) your dev team uses.
coming soon

Make Keybot your new personal assistant with Slack

Slack-logoSign up
What data do we collect?
Users: we fetch the IDs and timezones of users having access to your Slack workspace. We do not fetch personal data such as names and email addresses.
Actions, priorities and reminders
Morning digest: Keypup users on Slack receive a morning digest every day at 9:05am with the top priorities of their Priority Inbox.
Merge recommendations: When pull requests are mergeable, have a green build and have been approved, Keybot will send a notification to project maintainers and propose to merge them.
Asking questions to Keybot: You can ask questions to Keybot to get an update on pull requests and issues.
feature-carousel-6
icon-close-thin
Automatically prioritize Pull Requests & Issues for your team.

Generate automated follow ups.

See all your and your team's activity in one place, even if they are not on the Keypup platform.

The Keypup Priority Inbox works alongside your usual repositories and management tools.

The Inbox provide an aggregated and prioritised view of development activities to you and your team members. All related issues and pull requests are automatically linked and grouped as a unified discussion feed.
‍
No source code fetching. Just a development management tool to help with tracking tasks, pull requests and team work - from a developer's point of view.
Sounds great. Sign me up!
Keypup is a totally free service for Developers. No catch. No hidden prints. No credit card. We do not sell, distribute or monetize your data. We are just free for developers and that's it. We make money through large enterprise paid plans - not through you.
"Having more than 10 years experience as a developer and tech leader I am so happy our community finally has a specific tool to help us track efficiently our work and get clear visibility on all activities going on at once. That's why we created Keypup!"
Arnaud LACHAUME, CTO Keypup

Focus on development

Stop wasting time organizing your team's tasks and reduce your workload. Keypup automatically prioritizes your team's data, tasks and actions. Work knowing the mess is under control.
Automatically prioritized

Issues, pull requests and reviews prioritized based on due date, actions, criticality & more. Implement your own priorities for you and your team.

Unified team discussions

Pull requests and issues are automatically grouped based on links. All information synced in one place. Your team's discussion in a unified feed for each Pull Request.

Remote actions

All items have clear actions such as implement, review, merge. Action and Keypup disseminates in your tools.

Get notified

Have Slack? We'll remind you of important actions and follow ups.

keypup-screenshot3

How does Keypup help teams daily?

Let us show you how Keypup works through a real-life use case that might look familiar to you
Meet...
Jenny, she is a tech lead
Bob, he is a frontend developer working with Jenny
...they already use...
github-logo
GitHub
jira-logo
Jira
slack-logo
Slack
Jira and Slack are not required to use Keypup. GitHub or GitLab alone is sufficient.
...and working with Keypup looks like
1

It's sprint time!

Jenny logs into JIRA and assigns a couple of issues to Bob for this week.
Layer 1
All issues from his different apps in one place
2

Bob is ready to work!

Bob sees two issues in his Keypup priority Inbox with all the details he needs: description, comments, due date, labels etc.
step-2-priority-inbox
Layer 1
3

A pull request is opened

Bob opens a Pull Request on GitHub with his items and links both JIRA issues using auto-linking keywords.
step-3-open-pull-request
Layer 1
PR and issue discussions gathered in a single feed
4

Issues get grouped automatically

Thanks to auto-linking Bob only needs to follow a single item in his Keypup Priority Inbox instead of tracking his pull request and the two issues individually in his other tools.
Layer 1
Automated reminder of daily priorities
5

Next morning at 9am

Bob receives a digest via Slack with a reminder on his current priorities.
Go for it Bob!
keybot-conversion
Layer 1
6

Time for review!

Bob is finished with his pull request. He assigns it to Jenny for review. The item is automatically moved from his prioritized list to the Pending Peer tab.
‍
This keeps Bob's prioritized list actionable and clean!
Layer 1
Automated assignment for PR actions
7

Jenny's turn to review

Because Bob assigned Jenny on his pull request, it automatically appears in Jenny's Priority Inbox with an action set to Review.
Layer 1
Efficient collaboration between team members
8

Changes required on Bob's pull request

Jenny has made her review and requested Bob to change a few things. The pull request comes back to Bob's Priority Inbox with action Address review changes.
Layer 1
Centralized view of all PR status and progress
9

Meanwhile Jenny keeps an eye on all pull requests

The Review & Merge board allows Jenny to quickly review the status of pull requests across the team. No more stale PRs due to information spamming!
Layer 1
No more useless back and forth during reviews
10

Bob assigns Jenny for re-review...but wait..what?

Looks like the build is failing now. Despite having assigned Jenny for review the item remains in Bob's Priority Inbox with action Fix build.
Layer 1
Quick merge in one click
11

Ready to merge!

After Bob fixes his build, Jenny approves the pull request.

Because Keypup has automatically detected that Jenny was the project maintainer, the PR is moved to Jenny's Priority Inbox with action Merge.
Layer 1

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

‍
I know you take security seriously! Take me to my Keypup account
A word from our CTO
arnaud-lachaume
"I know how busy development can get. We use multiple tools, and there are multiple people involved. But at some point, it gets really messy and it's easy to loose track of what matters, what needs to be followed up or actioned individually and collectively.
We created Keypup to solve this. A platform where information is clear, sorted, actionable from end-to-end during the development cycle from the lead to all team members. I am excited to see our community  growing!"
Arnaud LACHAUME
CTO Keypup
©2019-2020 by Keypup SAS