Solutions · Networks
This category gathers products where people create, share or talk: feeds, chats, shared files, AI assistants and site builders. This hub compares how they handle content, audiences and running costs so you can pick the right model for your users.
Social, messaging, storage, AI and builder models
Audience, content and cost contrasts
Links to every networks product brief
Product models
Open the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerOpen the product brief
Open registerAsk who will see the thing a user makes. Public, followers, a group, one person, or only the user themselves. That answer puts you in one of these models and sets the privacy and safety work.
Storage, media streaming and AI inference grow with use, not with sign-ups. Estimate what an active user costs to serve in each model before setting prices or free tiers.
Products that skip this often find their most loyal users are their least profitable.
A public feed needs proactive screening and a review team, while a private chat leans on reporting and blocking. Match your safety tooling to exposure, and check the online safety rules in each country you serve.
Messaging, calling and file sharing can lean on open standards and established media servers, while AI products can call hosted models or run open-weight ones on your own infrastructure. Each choice trades speed to launch against control over cost, data location and future features.
Write down which parts must stay under your control, such as user data, moderation decisions and billing, and which can be rented. That list keeps the stack honest as the product grows and as vendor prices change.
FAQ
For private conversations it is now widely expected. It limits what the operator can see, so safety features have to work on the device or through user reports instead.
Each request uses model compute, and long conversations or large outputs cost more. Usage limits, caching and model choice keep costs in line with revenue.
Yes, even if the team is small. Reporting tools and a review process should exist on day one, and online safety duties apply in some markets regardless of size.
Many apps do, but each part has its own costs and safety needs. Launching the core use case first keeps the product focused and easier to moderate.
Sub-categories
Profiles, feeds and groups where reach and moderation are the hard parts.
Open registerReal-time chat, voice and video between chosen people, built for delivery speed and privacy.
Open registerUpload, sync and share files with permissions and versions, where storage and bandwidth set the economics.
Open registerAssistants, generators and workflow tools where every request has a model cost to manage.
Open registerEditors, templates and hosting that let customers publish sites under their own domains.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
UK regulator guidance for online services under the Online Safety Act.
Official project site for the open standard behind browser and app voice and video.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.
