Branding through config
Logo, favicon, colours, page title, welcome page text, default language, which toolbar buttons show. No code changes, so upgrades stay trivial.
Jitsi service
We change Jitsi Meet until it looks and behaves like your product. Logo, colours, domain and welcome page, up to new React components and plugins. You keep the source, and it still upgrades.
Most requests land in one of three buckets, and the price difference between them is large. So it helps to know which one you are in before you ask for a quote.
Logo, favicon, colours, page title, welcome page text, default language, which toolbar buttons show. No code changes, so upgrades stay trivial.
New layouts, redesigned toolbar and prejoin screen, your own icon set, removed features. This means a fork of the jitsi-meet front end.
Database-backed polls and voting, quizzes, file sharing, custom moderator tools, integrations with your login or LMS.
This is the cheap part, and for a lot of teams it is all they need. Jitsi Meet reads most of its look from
config.js and interface_config.js, so a rebrand is mostly a set of config values
and image files on the web server.
The watermark in the top-left corner is an image file served by the web server, and the link behind it is a setting. Swap both and the Jitsi logo is gone. Do it in your deployment scripts, not by hand on the server, because a package upgrade puts the default image back.
If you run Jitsi for several clients, dynamicBrandingUrl lets each meeting pull its logo and
background from a JSON file you host. One deployment, many brands. We set this up with the JSON served from
your own API, so a new client is a new record, not a new server.
Meetings run on meet.yourcompany.com with your SSL certificate, and the Jitsi landing page is
replaced with yours or skipped entirely so links go straight into a room.
Past config, you are editing the jitsi-meet source itself. It is a React and Redux app, and it moves fast: expect changes upstream every few weeks.
That is the real cost of deep Jitsi customization. The first build is not the hard part. Keeping your changes working across new releases is. Our changes go in as commits in the same repository, so taking a new Jitsi release means merging it in and testing, not starting again.
If you would rather do it in-house, our front-end customization guide walks through the build setup and the files you will touch.
Jitsi Meet already has simple polls in the chat panel. Teams usually want more than that: quizzes with scoring for classrooms, polls saved to a database for reporting, voting for board meetings. Those are custom features, and they carry across upgrades the same way.
Jitsi Meet is Apache 2.0 licensed. You can rebrand it, run it as your own product and charge for it. No per-host fees, no vendor logo you are not allowed to remove.
Compared with a white label video conferencing platform you rent, you trade a monthly per-seat bill for owning the servers and the upgrades. For a product with thousands of users that trade is usually worth it. For a five-person team, it is not, and we will tell you so.
Branding is one piece of a production setup. We also handle hosting on AWS, Azure or GCP, recording, scaling and ongoing support. Want a scheduling and admin console with your brand on it? Look at the Jitsi Meet Admin Panel.
Yes. On a self-hosted server you replace the watermark image and point the default logo setting at your own file. On an iframe embed you can also pass a logo through dynamicBrandingUrl. Neither needs a rebuild of the front end.
It is a config.js setting that points to a JSON file with your logo, background colour, background image and a few other branding values. Jitsi Meet fetches it when a meeting loads, so you can brand rooms differently without redeploying.
Jitsi Meet has built-in polls in the chat panel, with multiple-choice answers and live results. It has no quizzes: no scoring, no correct answers, no timer. Those need a custom plugin, which is work we do.
Config and branding changes do. Changes to the React source are commits on top of the Jitsi code, so a new release is merged in and tested, not rewritten.
Yes. Jitsi Meet is released under the Apache 2.0 license, which lets you modify it, rebrand it and sell a service on top of it. Keep the license and notice files in your build.