social.plusvs Stream

Both are infrastructure you build into your own app. Stream offers chat, video and audio, activity feeds and moderation as separate products, each with its own SDK and pricing. social.plus brings social engagement features together in one integrated layer: feeds, groups and forums, stories, clips, live streaming, chat and moderation, with SDKs, UIKit components and APIs across all of them. social.plus also includes operational tools that sit above the SDK layer: the Console for moderation and content management, and the Dashboard for engagement analytics.

social.plus includes a commerce layer built into the engagement experience: a product catalogue with product tagging across posts, comments and live streams, and sponsored content placement that lets your team run native ads in feeds and stories. social.plus UIKit gives your team fully customizable, white-label UI components across iOS, Android, Web (React), React Native and Flutter, covering feeds, chat, groups and forums, and more, so you can match the look and feel of your product without building from scratch. social.plus also includes comprehensive real-time analytics and insights with sentiment analysis and natural-language querying through Agentry.

Stream offers video calling and audio rooms, chat SDKs for game engines, message translation, typing indicators, and feed features like bookmarks, reposts and comment voting. Stream also has an open-source framework for building voice and video AI agents. social.plus does not offer these today. The closest social.plus features are live streaming with co-hosts, video and audio messages in chat, online presence indicators, and read and delivery receipts.

You can use the parts you need. social.plus is modular: you can start with chat alone, add feeds or groups and forums later, and expand into monetization or analytics when your product is ready. You can use the UIKit components or build your own interface on the SDKs and APIs. Stream also sells its products separately, each with its own pricing.

social.plus has client SDKs for iOS (Swift), Android (Kotlin and Java), TypeScript/JavaScript and Flutter. React Native has its own package built on the TypeScript SDK, and the TypeScript SDK works with React, Next.js (client-side), Vue, Angular and Svelte. UIKit is available for iOS, Android, Web (React), React Native and Flutter, and server-to-server APIs cover administration, moderation and automation. Stream covers a similar range of platforms for chat, video and feeds, with additional support for game engines. Stream also offers server SDKs for Node.js, Python, Go, Java, Ruby, PHP and .NET.

You own the data your app generates through social.plus. Your app identifies each user with its own user ID, so user profiles attach to accounts that already exist in your product. Each social.plus application runs in the US, EU or Singapore region, chosen when you create it. A data export API delivers reports of recent data, and webhooks (in private beta) send events to your server. Stream also lets you choose a region for your app, stores data in that region, and supports data exports and webhooks across its products.

social.plus includes user reports, a moderation feed in the Console for reviewing flagged content, blocklists and allowlists, PII detection, bans, mutes and custom roles. AI moderation covers images for pre-moderation and text, images and video for post-moderation, and live streams can be checked by AI while they run. Stream covers text, image, video and audio moderation. Text can be checked before posting, and other media types are checked after upload. Live calls can be moderated in real time, and moderators review flagged content through the Stream Dashboard.

Stream supports data exports for chat channels, users and feeds. On social.plus, the server-to-server APIs handle data import and administration. Because your app supplies the user ID, user profiles attach to accounts your users already have, so there is no separate account migration step. Talk to our team to plan a migration path.