Which self-hosted video conferencing platform fits your team
Choose Jitsi Meet when you need general meetings that can be embedded in your own websites and internal tools, BigBlueButton when the job is a virtual classroom with teaching features, and Nextcloud Talk when calls and chat should sit inside a Nextcloud file platform your users already use. None of the three is the right answer for every team, and the choice usually follows where your users already work and what the room is for. Jitsi Meet is built from separate parts (a web app, Prosody for signalling, Jicofo for conference focus and Jitsi Videobridge for media), so you can scale the bridges horizontally as load grows. BigBlueButton is a heavier, single-purpose system that asks for a dedicated server with 16 GB of memory and 8 CPU cores in its 4.0 install documentation. Nextcloud Talk adds the least new infrastructure if you already run Nextcloud, but its default mesh design limits calls, so plan for the High Performance Backend if you expect larger rooms.
Element Call and LiveKit-based apps such as La Suite Meet are named here for completeness but are not profiled in this comparison. Confirm each project's license, server sizing, scaling and recording support directly with the project before you put it on a shortlist, because those details are outside the facts this page relies on. Whichever platform you test, run a pilot with your real room sizes, your identity provider and your firewall rules, since TURN, UDP port ranges and HTTPS certificates decide whether calls work for remote staff. Ask any implementation partner to confirm those prerequisites in writing as part of a fixed scope.
Which video platform suits which scenario
This table maps common video scenarios to the platform that fits best and the condition that makes the fit hold. Read each row against your user count, recording needs and whether your files already sit in Nextcloud, because those conditions usually decide the choice more than feature lists do.
| Scenario | Best fit | Why, and the condition it depends on |
|---|---|---|
| General team meetings | Jitsi Meet | Lightweight browser-based calls with a small server footprint. Holds when meetings are ad hoc, participant counts stay modest and you do not need a file platform in the same login flow. |
| Online classes and courses | BigBlueButton | Built as a virtual classroom with slides, annotations, polling, whiteboard and breakout rooms. Holds when you can dedicate a 16 GB, 8-core server and plan for 500 GB of disk if recordings are kept. |
| Webinars with many passive viewers | BigBlueButton or Nextcloud Talk with the High Performance Backend | BigBlueButton suits lecture-style sessions on its own server. Talk with the High Performance Backend is documented for hundreds of passive participants, but that backend is a Nextcloud partner product obtained through Nextcloud sales, so confirm terms and sizing with them. |
| Calls inside an existing Nextcloud deployment | Nextcloud Talk | Chat, calls and file sharing sit in one login and share the same permissions. Holds when files already live in Nextcloud; without the High Performance Backend, calls usually scale to about 5 to 20 users. |
| SIP dial-in or a hosted option | Jitsi Meet (Jigasi for SIP, or 8x8's JaaS for hosting) | Jigasi provides SIP dial-in within a self-hosted Jitsi deployment, and 8x8 offers JaaS as a hosted service. Holds when you need telephone access without running a separate PBX; confirm SIP trunk and hosting terms with the vendor, and check Talk's optional SIP dial-in if you already run Nextcloud. |
How Jitsi Meet, BigBlueButton and Nextcloud Talk differ at a glance
These five options split into two groups: standalone meeting platforms and meeting apps that live inside a file platform. Each card names the license, the main use and the trade-off that decides whether it fits your team, so you can narrow the shortlist before comparing server sizing, scaling and recording in detail.
Jitsi Meet
Apache-2.0 browser-based meetings built from the Jitsi Videobridge media router, Jicofo, Prosody and optional Jibri and Jigasi components. It suits general meetings and guest access when you can run several services and keep HTTPS with a proper domain certificate working for every client. Check the authentication model you need (internal accounts, JWT tokens, LDAP or Matrix verification) and plan for horizontal videobridge scaling. The trademark belongs to 8x8, Inc., which also offers a hosted service called JaaS.
BigBlueButton
LGPL-3.0 virtual classroom with slides, annotations, polling, breakout rooms, shared notes and recording. It is built for teaching and training, and it is embedded in many learning management systems. The trade-off is hardware: the 4.0 install docs call for 16 GB of memory, 8 CPU cores and 500 GB of disk for recordings, with UDP ports 16384 to 32768 open. Upgrades directly from 2.6, 2.7 or 3.0 are not supported, so plan a clean server for 4.0.
Nextcloud Talk
AGPL-3.0 chat and calls inside Nextcloud, sharing accounts, files and sharing permissions with the file platform. It fits teams that already run Nextcloud and want meetings next to documents. Without the High Performance Backend, each participant sends a stream to every other, so calls usually stay within about 5 to 20 users. Larger calls need the High Performance Backend, a Nextcloud partner product obtained through Nextcloud sales. Confirm TURN server and HTTPS requirements before rollout.
Element Call
Element-based group calls built on the LiveKit stack, positioned for teams already using Matrix and Element. It matters if your chat strategy is Matrix, because calls then sit beside the messaging platform. Confirm the license, server sizing, scaling model and recording support with the project before shortlisting, since these depend on the release and deployment you choose. Do not assume feature parity with Jitsi or BigBlueButton.
La Suite Meet
LiveKit-based meeting app from the La Suite numérique program, designed for public-sector and sovereign deployments. It is worth a look if you want a self-hosted video app that fits a broader European open-source workplace stack. Confirm its license, server sizing, scaling behavior and recording options with the project before shortlisting, because this page does not state them. Ask for a written list of supported components and the update policy.
Capabilities, licensing and hosting needs side by side
This table compares Jitsi Meet, BigBlueButton and Nextcloud Talk on license, release, deployment, identity, recording, dial-in, scaling, server sizing, ports and paid routes, with Element Call and La Suite Meet marked for confirmation. Where a supplied fact is missing for an option, the cell tells you what to confirm with the vendor. Read each row against your own meeting volume, class sizes and hosting constraints.
| Capability | Jitsi Meet | BigBlueButton | Nextcloud Talk | Element Call | La Suite Meet |
|---|---|---|---|---|---|
| License | Apache-2.0 | LGPL-3.0 | AGPL-3.0 (Talk app for Nextcloud) | Confirm with Element before deployment | Confirm license with the project |
| Latest supplied release | stable/jitsi-meet_11248, September 14, 2026 | v4.0.0, October 14, 2026 (3.0.39 on October 2, 2026) | v25.0.6, October 15, 2026 | Confirm current release with the project | Confirm current release with the project |
| Deployment method | Debian/Ubuntu packages or Docker containers | Install script on a clean Ubuntu 24.04 server | Installed as an app inside a Nextcloud server | Confirm supported deployment options | Confirm supported deployment options |
| Identity options | Internal XMPP accounts, JWT, LDAP, Matrix verification via Docker .env | OpenID Connect in Greenlight v3, with Keycloak suggested for more login methods | Inherits Nextcloud user accounts and sign-in | Confirm supported identity options | Confirm supported identity options |
| Recording | Optional Jibri component for recording or streaming | Built in, requires 500 GB disk for recordings | Confirm recording capability with the Talk docs | Confirm recording capability | Confirm recording capability |
| SIP dial-in | Optional Jigasi component | Confirm with BigBlueButton documentation | Optional SIP dial-in via High Performance Backend | Confirm SIP support | Confirm SIP support |
| Scaling approach | Add more videobridges horizontally | Single server or load-balanced deployments (Scalelite) | Mesh by default, scales further with High Performance Backend | Confirm scaling model | Confirm scaling model |
| Minimum server guidance | Central server 4 CPU and 8 GB; each videobridge 4 or 8 CPU and 8 GB | 8 CPU cores, 16 GB RAM with swap, 500 GB disk (50 GB without recording), 250 Mbit/s symmetric | Confirm sizing with your user counts and TURN load | Confirm sizing with the project | Confirm sizing with the project |
| Required ports and TURN | 80 and 443 TCP, 10000 UDP; 5349 TCP and 3478 UDP optional | TCP 80 and 443, UDP 16384 to 32768; TURN recommended behind firewalls | HTTPS required; TURN on port 443 or 80 in almost all cases | Confirm port and TURN requirements | Confirm port and TURN requirements |
| Federation or embedding | Embeds in other web apps via token-based access | Embeds in Canvas, Moodle, Sakai, D2L and other LMS platforms | Federated chats with other Nextcloud servers | Confirm federation with Matrix deployment | Confirm embedding options |
| Paid or hosted route | 8x8 JaaS hosted service; free meet.jit.si instance | BigBlueButton Inc. hosting and commercial support | Nextcloud Enterprise subscription; High Performance Backend via Nextcloud sales | Confirm hosted options with the project | Confirm hosted options with the project |
How server sizing and scaling change the choice
The three platforms scale in different shapes, so sizing is the first place they diverge. Jitsi separates the work across components: the central server (Prosody for signalling, Jicofo for conference focus) is one machine, and the Jitsi Videobridge media routers are added horizontally as load grows. The scalable setup guide suggests a 4 CPU, 8 GB machine for the central server and 4 or 8 CPU with 8 GB RAM for each videobridge, and notes that the default install is already configured for horizontal scaling. Adding bridges is a routine capacity step, but the central server remains a single point you must size and watch. Jitsi is adequate for small-to-medium meetings when you can add bridges as demand grows. Measure concurrent participants, bridge CPU and bandwidth at peak, and whether your bridges sit in the same network as your users.
BigBlueButton treats one server as the unit of capacity. The BigBlueButton 4.0 install documentation sets minimums of 16 GB of memory with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth. Those figures describe a single server, not a cluster. Load balancing across several BigBlueButton servers is a separate step that the project handles through its own tooling, so the reader should plan it as additional design and operations work rather than a default setting. A single well-specified server is adequate for a school, department or class size where concurrent sessions stay within what one machine can carry. Before committing, measure concurrent sessions, recording storage growth and the symmetrical bandwidth available at the site, and confirm the load balancing approach with the project documentation.
Nextcloud Talk uses a mesh model by default. Without the High Performance Backend, each participant sends a stream to every other participant, roughly 1 Mbit/s times participants minus one, and Talk usually scales to about 5 to 20 users in a call. That makes uplink bandwidth and client CPU the constraints well before the server is. The High Performance Backend, a selective forwarding unit that is a Nextcloud partner product obtained through Nextcloud sales, typically supports 30 to 50 or more active participants and hundreds of passive participants for webinars. Small team calls inside a file platform may be adequate on the built-in mode, while larger calls, webinars or SIP dial-in need the HPB and a sales conversation. Ask for the HPB sizing guidance in writing and test a realistic call with your own participant count and network paths.
How identity, recording and classroom features differ by platform
Jitsi Meet offers several authentication routes, and the choice shapes how rooms are created and who can join. The Docker setup reads these options from the .env file, so the identity design is set at deployment time rather than in a separate product module. Internal XMPP accounts are the simplest option. JWT token authentication is the route the Jitsi handbook recommends for new installations, with a separate anonymous domain for guests. LDAP, Matrix user verification and a hybrid Matrix plus JWT mode are also listed in the Docker guide.
- Deprecated secure domain: The username and password room creation method is marked deprecated for new installations, so plan for JWT instead.
- Recording with Jibri: Recording and streaming run in a separate Jibri container. Confirm the storage location, retention and access controls for recording files in your own environment.
- SIP dial-in: Jigasi is the optional SIP gateway for dial-in. Confirm that it is needed before adding it to the deployment.
- Classroom features: Jitsi Meet is a meeting tool first. Confirm whether breakout rooms, polling or shared notes meet your teaching needs before you commit.
- Hardened containers: Since stable-11146 the containers run rootless with read-only filesystems, which affects how you mount recording storage.
Before committing, confirm how your identity provider maps to JWT claims and whether your recording retention rules can be met with the Jibri storage you plan to use.
BigBlueButton is built as a virtual classroom, so its feature set and identity options are aimed at teaching. Greenlight v3 is the front end that manages rooms and users, and it supports external authentication through OpenID Connect, configured with environment variables. The BigBlueButton documentation suggests Keycloak as a broker for Google, Microsoft, SAML and other login methods. This means your identity design usually runs through Keycloak rather than through BigBlueButton directly.
- Greenlight v3 OpenID Connect: Configure the OIDC settings with environment variables, then test sign-in for every role, including instructors and guests.
- Keycloak as a broker: Use Keycloak to add SAML or Microsoft sign-in, and confirm the claim mapping for roles.
- Recordings: Recording requires a larger disk. The install documentation lists 500 GB for recordings and 50 GB without recording for a 4.0 server.
- Breakout rooms and polling: Breakout rooms, polling, a multi-user whiteboard and shared notes are part of the core feature set. Test them with your class sizes.
- API checksums: API calls use a shared secret with SHA-256 by default, so the secret must stay on the server side and never appear in a web page.
Confirm your recording retention period, who can view recordings and whether the server disk meets the recording estimate for your expected session volume.
Nextcloud Talk is part of the Nextcloud file platform, so its sign-in is tied to the Nextcloud account system. Users who already sign in to Nextcloud can join Talk rooms with the same account, which makes the identity design simpler than a separate meeting stack. Whether this extends to every external login method, such as SAML, LDAP or OpenID Connect, depends on the Nextcloud user backend you deploy. Confirm that configuration in your own environment before treating it as single sign-on for Talk.
- Account reuse: Talk rooms use Nextcloud accounts, so user lifecycle changes in Nextcloud apply to meetings as well.
- Calls and sharing: Talk supports private, group, public and password-protected calls, screen sharing and chat with file sharing and mentions.
- Recording and classes: The Talk README and system requirements do not describe a recording pipeline or classroom features comparable to BigBlueButton. Confirm whether recording and class tools meet your needs.
- Scale depends on the backend: Without the High Performance Backend, Talk usually scales to about 5 to 20 users in a call. The High Performance Backend is a Nextcloud partner product obtained through Nextcloud sales.
- TURN and HTTPS: Talk needs HTTPS for WebRTC calls and a TURN server on port 443 or 80 in almost all scenarios.
Confirm which login methods your Nextcloud deployment supports, whether recording is available for your edition, and whether the High Performance Backend is needed for your call sizes.
What it costs to move meetings and users between platforms
Video platforms hold little persistent data compared with file or mail systems, so the cost of moving between Jitsi Meet, BigBlueButton and Nextcloud Talk is mostly rebuilding the links, identities and room configuration around the meetings, plus retraining users. Recordings are the main data you may need to keep. Before you commit, inventory every place a meeting URL appears: calendar invitations, LMS course pages, intranet links, bookmarks, SIP dial-in numbers and any host application that creates rooms. Record which identity source each platform authenticates against, the room or class settings people rely on, and where recordings are stored and who must be able to find them after cutover. Those lists, not the software license, will drive most of the work.
BigBlueButton 4.0 needs a clean server installation because direct upgrades from 2.6, 2.7 or 3.0 are not supported, so an existing BigBlueButton estate cannot be moved forward in place. Plan for a new host meeting the published requirements, a parallel run, and an export or archive path for recordings that you have tested. Confirm with BigBlueButton Inc. or your own test environment how any existing recordings and LMS integrations will be carried across. For Jitsi Meet, the JWT setup means that your host application, not Jitsi, must issue the tokens that grant room access, so moving to or from JWT changes code in that application. Nextcloud Talk calls depend on the Nextcloud deployment itself, including its HTTPS certificate, TURN server and user accounts, so a Talk move can also be a file platform move. Ask for a written list of every dependency before scheduling the cutover.
Treat the cutover as a pilot first. Choose one team or course, run it on the new platform for a defined period, and log the failures users actually hit, such as browser permissions, firewall blocks on UDP ports, or certificate warnings. Confirm the scope of any migration assistance, data export tooling and retraining in a written statement of work before work starts, since DeployOpen scopes these engagements as fixed deliverables. Where the platforms do not share identity or room models, budget for mapping work and for running old and new links side by side until the old ones are retired.
How to choose and pilot a self-hosted video platform
This sequence turns a shortlist of Jitsi Meet, BigBlueButton, Nextcloud Talk and other LiveKit-based or Matrix-based options into a documented pilot decision that your team can defend with measured load, identity and support evidence.
Define the video use cases first
Start by naming the primary use: internal meetings, classes, webinars or calls with outside parties. Each use shapes the platform choice. Nextcloud Talk suits chat and calls inside a file platform, while BigBlueButton is built as a virtual classroom with polling, shared notes and breakout rooms. Jitsi Meet fits general meetings with a separate media router design. Ask the business owner of each use to sign off the list in writing. Done means each use case has a named owner and a rough audience type, not a platform name.
Set participant limits and recording rules
For each use case, record the largest expected concurrent participant count and the number of passive viewers. Talk's documentation says calls without its High Performance Backend usually scale to about 5 to 20 users, and that the High Performance Backend typically reaches 30 to 50 or more active participants, so the answer decides whether that add-on is in scope. Write down who may record, where recordings are stored, how long they are kept and who approves access. BigBlueButton's install guide asks for 500 GB of disk when recording is enabled, so storage is part of this decision. Confirm with each vendor how recording and retention are configured for your edition.
Confirm domain, certificate and port readiness
Have your network team confirm a valid domain name, a trusted certificate and the ports each candidate needs. Jitsi's handbook says HTTPS with a proper domain certificate is necessary for working audio and video, and self-signed certificates cause problems on mobile clients. BigBlueButton needs TCP 80 and 443 and UDP 16384 to 32768, and Nextcloud Talk needs HTTPS and a TURN server on port 443 or 80 in almost all cases. Ask whether your firewalls and load balancers allow these paths and whether a TURN server is required for users behind restrictive networks. Done means a signed checklist of ports, hostnames and certificates for each candidate.
Measure bandwidth and TURN needs
Estimate the upload and download your meetings will need at peak. Talk without the High Performance Backend sends each participant's stream to every other participant, roughly 1 Mbit/s times participants minus one, so bandwidth grows quickly with group size. BigBlueButton 4.0 lists 250 Mbit/s symmetrical bandwidth for its server. Identify which users connect from restrictive networks and test them specifically, since a TURN relay may be required. Done means a bandwidth figure per meeting size and a list of users who need relay testing.
Choose the identity method before the pilot
Pick how users sign in before building anything. Jitsi's Docker guide lists internal XMPP accounts, JWT tokens, LDAP, Matrix verification and a hybrid mode, and its handbook recommends JWT token authentication over the deprecated secure domain method, with a separate anonymous domain for guests. Greenlight v3 for BigBlueButton supports OpenID Connect, and its docs suggest Keycloak for additional login methods. Nextcloud Talk inherits the sign-in set up on the file platform. Confirm with your identity team which methods your directory supports and who owns the token signing keys or client secrets.
Run a pilot on a server at the vendor minimum
Build a pilot on a server that meets or exceeds each vendor's published minimum, then test at your target load. BigBlueButton 4.0 requires 16 GB of memory with swap and 8 CPU cores with high single-thread performance. Jitsi's scalable guide suggests a 4 CPU, 8 GB central server and 4 or 8 CPU videobridges with 8 GB RAM each. Use a clean install, since direct upgrades from earlier BigBlueButton versions are not supported. Record CPU, memory, bandwidth, packet loss and recording storage during scripted meetings at your peak size. Done means a measured load report that compares observed numbers with the vendor minimums. Confirm the minimums with each vendor before you size production hardware.
Decide the support route and document the result
Compare the community route with paid support for each candidate. Jitsi's own team offers JaaS as a hosted option, BigBlueButton Inc. offers hosting and commercial support, and Nextcloud GmbH sells Enterprise subscriptions. Ask each vendor for support terms in writing, including response expectations and what covers upgrades. A partner such as DeployOpen can plan, implement, harden and support the chosen platform inside your infrastructure under a fixed-scope agreement, and ongoing support is available as a retainer. Close the pilot with a decision record that lists the chosen platform, measured load, identity method, ports, recording policy and the named support owner.
What do buyers ask before choosing self-hosted video conferencing?
What drives the cost of self-hosting video conferencing?
Cost depends on how many servers you run, how much recording storage you keep, how much identity work you need, and how many staff hours the rollout and operation consume. Infrastructure is recurring: cloud or data center capacity, bandwidth and storage. Labor is partly one-time (design, installation, identity and certificate setup) and partly recurring (upgrades, monitoring, user support). The BigBlueButton 4.0 install documentation lists a minimum server of 16 GB of RAM with swap, 8 CPU cores, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth, so recording alone changes the disk figure by an order of magnitude. Ask any provider for a written quote that itemizes servers, storage, bandwidth, TURN, certificates, identity integration, hours and support terms.
How long does a self-hosted video conferencing setup take?
The timeline depends on sizing decisions, the identity integration, network approvals and how many environments you need, so no single duration applies. A single-server Jitsi Meet or Nextcloud Talk test can be running quickly on a prepared host, but production work adds certificates, firewall changes, load tests and sign-off. BigBlueButton 4.0 cannot be upgraded directly from 2.6, 2.7 or 3.0, so a clean install is the recommended path, which can add migration planning if you already run an older version. Ask the vendor or partner to state the phases, the dependencies they assume from your side, and the acceptance tests that close each phase.
What do we need to provide before a provider starts work?
You need to provide network access, a firewall change window, the public hostnames you want to use, identity sources and the people who approve them, and a sizing sign-off for expected concurrent users and meeting size. Jitsi needs ports 80/TCP, 443/TCP and 10000/UDP open, with 5349/TCP and 3478/UDP optional, and the Jitsi handbook says HTTPS with a proper domain certificate is necessary for working audio and video. BigBlueButton requires TCP 80 and 443 and UDP 16384 to 32768. Write these requirements, the owner for each and the date you need them into the scope before work begins.
Can our own team run this without outside help?
A team with Linux, reverse proxy, TLS and database experience can often run a small Jitsi Meet or Nextcloud Talk deployment in-house, but the hard parts are scaling, TURN for users behind restrictive firewalls, recording storage and identity integration. Jitsi scales by adding Videobridges, and its scalable guide suggests 4 CPU and 8 GB for the central server and 4 or 8 CPU with 8 GB RAM per bridge. Nextcloud Talk without the High Performance Backend usually scales to about 5 to 20 users per call. Decide who will carry upgrades, incident response and on-call duties, because those recur for the life of the system.
What does open-source licensing change compared with a paid or hosted route?
Open-source licenses give you the right to run and modify the code, but they do not include vendor support, service levels or hosted operations. Jitsi Meet is Apache-2.0, BigBlueButton is LGPL-3.0 and Nextcloud Talk is AGPL-3.0, so each has different obligations if you modify and distribute the code. Jitsi states that Jitsi is a trademark of 8x8, Inc., and 8x8 offers JaaS as a hosted service. The hosted route replaces infrastructure and operations cost with a subscription, while self-hosting keeps data in your environment at the price of staff time. Confirm license obligations with your legal team and confirm support terms with each vendor in writing.
How is the Nextcloud Talk High Performance Backend obtained?
The Nextcloud Talk High Performance Backend is a Nextcloud partner product that enterprises obtain through Nextcloud sales, according to the Talk scalability documentation. It is a selective forwarding unit that Talk typically scales with to about 30 to 50 or more active participants and hundreds of passive participants for webinars, and it provides optional SIP dial-in. Because it is not part of the open-source Talk app, ask Nextcloud sales for its licensing terms, price basis, support scope and deployment requirements before you design around it. Ask for these in a written quote alongside your Nextcloud Enterprise subscription options.
Which identity and certificate tasks add the most effort?
Identity integration and TLS certificates are the two tasks that most often stall a rollout. Jitsi's Docker guide lists internal XMPP accounts, JWT tokens, LDAP, Matrix verification and a hybrid mode, and its handbook recommends JWT token authentication over the deprecated secure domain method. Greenlight v3 for BigBlueButton supports OpenID Connect through environment variables, and the docs suggest Keycloak for other login methods. Nextcloud Talk needs HTTPS for WebRTC calls and a TURN server on port 443 or 80 in almost all scenarios. Self-signed certificates cause problems, especially on mobile clients, so plan for a domain certificate process and renewal from the start.
How DeployOpen scopes and delivers a video conferencing rollout
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For video conferencing, that means agreeing in writing which platform fits your meetings, classes or calls, and then delivering it under a fixed scope with clear handover material.
How we scope
- Written scope covers the platform choice, user groups, identity method, and whether recording or SIP dial-in is needed.
- We confirm server sizing against the vendor's published requirements for your expected concurrent participants.
- Fixed-scope engagements list deliverables and timelines in writing before any work starts, so quotes follow directly from that document.
How we build
- We deploy the chosen stack in your environment, including HTTPS certificates, TURN relay where firewalls require it, and open ports.
- We integrate authentication with your existing identity provider, such as JWT tokens, OpenID Connect or LDAP where the platform supports them.
- We test call quality, scaling behavior and recording storage against the scope, and document the results for your review.
How we hand over
- You receive configuration documentation, runbooks for restarts, certificate renewal and upgrades, and the list of open ports and dependencies.
- Handover covers the recording storage plan, backup approach and the access model for administrators and moderators.
- We walk your platform and security teams through the setup so they can run changes without relying on the original build.
How we support
- Ongoing support, version upgrades and continuous testing are available as retainers, scoped separately from the build.
- Upgrade planning follows the vendor's release and migration notes, with each change tested in your environment first.
- Your team should confirm support windows and paid edition terms directly with each vendor, since those decide how long a version stays patched.
