8 posts tagged with "security"

You've set up your video conferencing service, but now you want to make it smarter. What if you could automatically log the duration of every meeting for billing? Or get a Slack notification when a VIP joins a call? This is where webhooks come in.

This guide will walk you through building your very first automated workflow. We'll create a simple but powerful service that listens for a meeting to end and logs its duration to your console—a perfect starting point for a real-world billing or analytics system.

For more high-level ideas on what's possible, check out our companion post on 5 Powerful Workflows You Can Build with Webhooks.

In an age of heightened privacy concerns, offering End-to-End Encryption (E2EE) is one of the most powerful ways to build trust with your users. It provides a mathematical guarantee that conversations are confidential and that not even your server can access the media streams.

While the technology is complex, implementing it doesn't have to be. This guide will walk you through the two E2EE models available in Plug-N-Meet and show you how to enable them with a simple API call.

In an era where data breaches are daily news and "free" services monetize your conversations, privacy can no longer be an afterthought. It must be the foundation.

When we built Plug-N-Meet, we didn't just want to create another video conferencing tool. We wanted to build a platform that respects the user's right to privacy by default. This meant making hard architectural choices—prioritizing security over easy data harvesting, and giving control back to the user rather than hoarding it on the server.

If you are building a telehealth platform, a legal consultation app, or simply a secure meeting space for your team, you need more than just a "secure" sticker. You need an architecture designed for the Zero-Trust era.

Here is how Plug-N-Meet delivers on that promise.

Think about the last time a new application asked you to "download and install" something. A small wave of hesitation probably washed over you. Is this software safe? Will it slow down my computer? Do I have time for this? It's a moment of friction and uncertainty.

At plugNmeet, we believe that joining a video meeting should be as simple and frictionless as visiting a website. That's why we've built our entire platform around a core philosophy: No installation required.

This isn't just a convenience; it's a deliberate design choice that leads to a more secure, more private, and fundamentally better user experience for everyone.

The digital transformation of healthcare is accelerating, but for telehealth providers, the choice of communication technology is fraught with risk. Using off-the-shelf video conferencing tools can create a compliance nightmare. How do you ensure patient data is secure? How do you sign a Business Associate Agreement (BAA) with a public cloud vendor whose data practices are a black box? How do you create a seamless, trusted experience for your patients?

The answer is to own your stack.

Building a telehealth platform requires a foundation of absolute control over your data and infrastructure. This is why forward-thinking healthcare companies are turning to self-hosted, open-source platforms like plugNmeet to serve as the secure communication core for their applications. This article explains how.

We’ve all felt that moment of panic. You’re in an important online meeting, the chat is full of crucial links, and then you accidentally hit refresh. Everything is gone. To solve this, many applications store your entire session on their backend servers. This allows them to restore your session, but it comes at a huge cost: your sensitive data is now stored permanently on someone else's hard drive.

At plugNmeet, we believe this is the wrong trade-off. We've made a deliberate architectural choice to use your browser's own storage to provide a resilient experience without compromising your privacy.

Our philosophy is simple: if we don't need the data on our server to make the service work, we don't touch it.

In the world of secure communication, End-to-End Encryption (E2EE) is the gold standard. It ensures that only the participants in a conversation can decrypt and view the media streams, not even the server itself. At plugNmeet, we've implemented a robust E2EE model based on the WebRTC Insertable Streams API.

But "E2EE" isn't a single, one-size-fits-all solution. A critical question remains: where do the encryption keys come from, and who manages them?

plugNmeet offers two distinct models for managing E2EE keys, controlled by a simple setting: enabled_self_insert_encryption_key. Understanding the difference is key to choosing the right security posture for your application.

For educators and institutions using Moodle, the goal is to create a seamless, engaging, and secure learning environment. However, when it's time for a live virtual class, many are forced to send their students to an external, generic video conferencing link. This experience is often disjointed, and the tools provided are frequently limited to passive screen sharing.

What if your live classroom felt like a native part of Moodle? What if you could move beyond one-way screen sharing to a truly interactive and collaborative canvas, all while maintaining the highest levels of security and performance?

By integrating the plugNmeet activity module into Moodle, you can achieve exactly that. This post explores how to leverage plugNmeet's powerful, built-in collaborative tools—the interactive whiteboard and shared notepad—to build a superior e-learning platform.