Tribeco

Tribeco Case Study: Anonymous Video Conferencing Without Registration

Brief description

A free service for anonymous calls without registration

Task

Create an anonymous analogue of ZOOM

About the project

Tribeco is a free service for anonymous, encryption-protected video conferences.Security is a key aspect of development: it protects both users and platform owners. Call recording and eavesdropping are impossible, user tracking is excluded — calls are fully anonymous.To create complete anonymity, we built a service without registration — Tribeco does not collect data about the user, their device, or other information, and intentionally has no registration to ensure the maximum level of anonymity. To create a call you can use any browser, any device, and you only need to press one button — without verification or registration.For the Tribeco application, transit encryption of data was developed for transmission to the server, so your messages are encrypted before leaving your device. A system for generating unique room addresses was also created — the same approach used when encrypting a crypto wallet with a seed phrase, the method most resistant to brute-force guessing.

Business benefits

•ELIMINATING THE RISK OF THIRD PARTIES EAVESDROPPING ON CALLS

•THANKS TO ENCRYPTION AND ANONYMITY, YOU SAVE MILLIONS

•FULL ANONYMITY OF PARTICIPANTS AND USER DEVICES

•THE SERVICE WAS READY IN 5 MONTHS AND DEPLOYED ON THE CLIENT'S SERVERS

•SAVINGS FROM PREVENTING DATA LEAKS THROUGH CALLS OF MORE THAN $4.88M

•52% OF SUCCESSFUL CYBERATTACKS — ANONYMIZATION AND ENCRYPTION SYSTEMS NEUTRALIZE THE THREAT

Features

Create a meeting without registration

Join a call without registration

Create a new meeting in one click without an account

No verification steps (phone/email)

Unique room link generation

Participants join via link from any device and any browser

Join a meeting via link

Enter a room without login or confirmations

Fast join flow — open the link and join

Protection from accidental access via a unique room address

Room creation and joining via link

User creates a room and receives an invite link

Participants join via link without signing in

Fast usage flow: create meeting => send link => participants join

Connection security and encryption

Unique room address IDs generated similarly to crypto seed phrase generation

Address logic designed to resist brute-force guessing

Lower risk of random guests joining by guessing the link

Encrypted communication channel (transit encryption)

Data is encrypted before leaving the user's device

Network transmission happens in a protected form

No user data collection

No registration mechanics = no account storage

The service does not collect user or device data as a requirement to work

Minimizing traces that could lead to deanonymization

Privacy at the platform architecture level

The service cannot record or listen to a call on the platform side

No cloud recording or server-side storage of call content

Security extends to both users and platform owners

Meeting management (organizer)

Manage basic room parameters as the creator

Control participant access and behavior within the meeting

Quick organizer actions for running the session

Participant management

Participant list display

Control participant state (microphone, camera)

Basic management actions within the meeting

Video call and in-call communication

Holding a call in a room as the primary usage scenario

Ability to create additional breakout rooms inside one video meeting, for example for a one-to-one talk during a general call

In-call chat

Shared text chat inside the room

Messaging during the call

Private messages

Direct messages between participants inside the call

Used for private clarifications not visible to the whole room

In-call reactions

Reactions and emoji as quick interaction

Feedback without interrupting by voice

Screen sharing

Ability to share the screen during a call

Participant-side sharing control (turn on/off)

Simultaneous sharing by multiple participants, configured by the meeting admin

Call recording only on the user's device

Recording is possible only locally on the device

Call recordings are not stored on the service servers

Multilingual interface (40+ languages)

Support for multiple interface languages

Ability to switch to the needed language in settings

Noise suppression and audio quality improvement

Noise suppression to improve speech clarity

More stable call quality in real conditions (office/street/home)

Technology stack

The main technology stack used in the Tribeco project includes the following components:

1. Frontend:

React (version 18.2.0) - the basis of the frontend.

Material-UI (@mui/material) - a component library for interface styling.

Emotion (styled components) - for styling with CSS-in-JS.

WebRTC - for organizing video calls.

Redux and redux-thunk - for application state management.

2. Libraries and API:

Amplitude - for analyzing user interactions.

Giphy API - for integrating gifs into the application.

3. Backend and utilities:

Node.js (>=14.0.0) - the main runtime environment.

@rtcstats - for collecting and analyzing RTC statistics.

@tensorflow/tfjs - for integrating machine learning models.

Microsoft Graph API - for working with Microsoft data.

4. Development tools:

Babel - for code transformation.

ESLint - for checking code for errors.

Webpack - for building the application.

TypeScript - for static typing of code.

Jetifier - for migrating libraries to React Native.

Work with the client

*Important: this is not project work — it is work with the client specifically, and it is not included in the estimate or commercial proposal. This is what we do to increase the probability of product success.Development for us is only the tip of the iceberg. The main work was around helping the client's team adopt the product as their own and understand it down to the last button. We ran multi-hour sessions with the owner and key employees, explaining the logic of every module: why interfaces are structured this way, which user behavior patterns we embedded, and how to use them for conversion growth. Separately, we covered operational risks: we modeled a seasonal demand drop, a contractor failure, and the departure of a key employee — and for each scenario the team now has an action plan. The result is a client who does not depend on the developer at any stage of operation.Our goal is not just development — it is our client's success.

Design goals:

•GET THE USER TO A CALL QUICKLY, WITHOUT REGISTRATION OR EXTRA SCREENS

•CONVEY A SENSE OF PRIVACY AND SECURITY AT FIRST GLANCE

Design results:

•THE FASTEST POSSIBLE CALL START IN ONE SCREEN WITHOUT REGISTRATION OR EXTRA STEPS

•VISUAL FOCUS ON PRIVACY AND TRUST, MINIMAL FIELDS, CALM INTERFACE, NO DISTRACTIONS

•FAMILIAR CREATE AND JOIN FLOWS SO THE USER DOES NOT NEED TO LEARN THE PRODUCT

•CLEAR HIERARCHY AND ONE PRIMARY CTA ON EACH STEP TO KEEP CONVERSION

•UNIVERSAL SUPPORT FOR ANY DEVICES AND BROWSERS SO PEOPLE CAN JOIN VIA LINK WITHOUT BARRIERS