Communities, chat, voice and screen sharing connected to GitHub and Jira — with access computed from who actually works on each repository.
13:42 Alyfer opened PR #342 — feat: implement Redis caching
13:38 Ana joined the daily voice and is sharing her screen
13:31 CI failed on PR #337
13:21 João approved PR #334
Community, code and conversation in one place, with access decided by who actually works on each repository.
Communities with categories, text and voice channels, invites and roles with granular permissions.
Realtime messages with Markdown, syntax-highlighted code blocks and mentions that reach the right people.
When you sign in, DevColab opens on your friends and direct conversations. Add people from your communities or by e-mail, and choose who can write to you directly.
Connect the organization through the GitHub App: repositories become channels and only people with access to the repository join the channel.
Connect your Jira Cloud site: projects become channels with the sprint and the issues, and each task opens in a sheet where you comment, change the status and see the branches and PRs that implement it.
One calendar per community, with one-time or recurring events, reminders in the bell and by email, and a heads-up in the channel right on time.
Low-latency voice channels, a speaking indicator and controls that respect the community's roles.
Share a screen, window or tab and pick what you are showing: a game, a video or work. DevColab tunes resolution, frames and audio, uses the graphics card when it can and previews who is live.
Adjust the volume of each participant and each stream just for you, without affecting anyone else.
Each imported repository becomes a channel with the GitHub timeline and the pull request panel side by side, without switching tabs to see what changed.
Opened pull requests, reviews, merges and CI failures become cards in the conversation, in the right channel.
All, mine or waiting for my review, with branch, change size and review status.
"Why do I have access?" shows where your permission on the linked repository comes from.
Sign in with Google, create the community and invite the team with a link.
Install the GitHub App on the organization and import repositories as channels with computed access.
Discuss pull requests in the right channel, join voice and share your screen when you need to show something.
Each channel's access comes from the community's roles and GitHub permissions, and is reevaluated whenever something changes.
Whoever loses access to the repository loses access to the channel, including voice, without anyone having to remember to remove them.
Changes to roles, permissions or on GitHub reach open sessions and voice rooms within seconds.
Integration credentials are stored encrypted, with key rotation.
Audio and video travel through the media server with short-lived tokens; the platform decides who joins and with which rights.
Volumes and sharing choices stay in your browser and aren't sent to the server.
It stays in the tray and keeps you connected, alerts you to mentions with system notifications, shows unread counts on its icon, controls the call from the menu and shares any screen or window, with your computer's sound on Windows and macOS.
Windows 10 or 11, 64-bit. Updates itself.
The installer isn't signed yet: if Windows warns you, click More info › Run anyway.
macOS 12 or later. New versions are announced in the app.
The first time, macOS blocks the app: open System Settings › Privacy & Security and click Open Anyway.
x64. The AppImage updates itself.
AppImage: make it executable and open it. deb: sudo apt install ./DevColab.deb. On GNOME, the tray needs the AppIndicator extension.
A map of who works on what, linking repositories, issues, pull requests and conversations.
No. Communities, chat and voice work on their own. GitHub adds per-repository channels, pull requests and computed access.
Whoever manages the community connects a Jira Cloud site and imports projects as channels. Each person connects their own Atlassian account in My account, and the channel opens to whoever sees the project in Jira. From the issue sheet, each person comments, changes the status and assigns with their own account, and branches and PRs carrying the task key (like feat-DEV-12-login) show up linked to the issue.
Your friends write directly. People who share a community with you send a request, which you accept, decline or block; in My account you can let anyone from those communities write directly. By e-mail, only a friend request arrives, and the sender gets the same answer whether the account exists or not.
The platform runs in the browser. Full adaptation for phones and tablets is in progress and arrives in upcoming versions.
Yes, for Windows, macOS and Linux, in the Desktop app section. It does everything the browser does, and it also stays in the tray, alerts you with system notifications and shares windows with your computer's sound.
No. Mobile browsers don't offer screen capture; on a phone you watch other people's streams.
Whoever can manage the calendar creates the event and picks the reminders. People involved get them in the bell, in their computer's notifications and, if the event asks for it, by email; each person can turn them off in My account.
The community's roles decide: connecting, speaking, sharing and moderating are separate permissions, revoked instantly.
Messages and communities are stored in the platform's database. Audio and video aren't recorded, and volume preferences stay only in your browser.