PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
OmnistuSTUDIO / SERVICESStart a project

White-label

Messaging app, white-labelled for you

A customizable messaging platform under your branding. Original code, finished under your branding, scoped in writing before any build starts.

What it typically includes

How white-labelling works

Related reading

Scope areas for this kind of build

Overview

Calls That Never Meter by the Minute

  • Voice and video run straight between the two devices instead of through a paid calling vendor, so heavy use costs no more than light use. Group calls behave the same way.

Rebranding Is a Console Task, Not a Release

  • Name, logo, colours, languages, privacy policy and sign-in methods are all settings a non-technical operator changes. Launching a new brand takes an afternoon, not a release.
  • Ask for relevant work evidence and permission to verify any proposed client reference.
  • Open the platform yourself. Two working accounts are live, and that matters more for messaging than for any other product, because a messenger only proves itself with two people in the thread. Load one account in your browser and the other in a private window, then send a message across: it lands instantly, the ticks change as it is read, and the typing indicator shows as the other side answers.

Chats, Calls, Stories & Media

  • What members see. A chat list with the story tray on top, private and group conversations, voice and video calls, photos, video, voice notes, files, location and contact cards, polls, reactions, replies, forwarding, starring and pinning, plus wallpaper, avatar and language choices.
  • 2 Login with the first phone number below

The Receiving End of the Conversation

  • 1 Open a private window or second browser
  • 2 Login with the second phone number below
  • 3 Test: delivery, read receipts, typing, calls

Users, Moderation, Analytics & Brand Controls

  • Where the platform is actually run. Fifteen dashboard figures for signups, active users, groups and call volume, reported-user and reported-group queues, blocking, your report reasons, language management, branding and integration keys. We show this one live rather than leaving an operator login public.
  • 1 Message us with your scope
  • 2 We describe the console surfaces in writing
  • 3 Covers: Analytics, Moderation, Branding, Languages

The Native App on an Actual Phone

  • 3 Test: push, calls, camera, contacts, offline

Platform References - What the Build Actually Does

Voice and video calls connect directly between devices using WebRTC, with a relay server as fallback when a restrictive network blocks the direct route. No per-minute charge from a calling vendor sits between you and your users.

Reporting, blocking, per-conversation locks, an operator-managed list of report reasons and a moderation queue for both users and groups all arrive built, rather than being retrofitted after the first incident.

Modelled Reference - A Self-Hosted Community Messenger

An illustrative configuration showing how the platform would be set up for an organization that wants its community talking inside its own app rather than in an unmanaged group on another company s service. It describes no client engagement, and every figure is a property of the software rather than a reported result.

An organization whose members already talk every day in an unofficial group chat moves that conversation into its own app, because moderation, language and ownership now matter.

Why Organizations Move Their Messaging In-House

Most organizations let their community live inside a consumer messenger because it was free and everybody already had it. That holds until the day it does not: nobody can see who is active, nobody can properly remove a member, none of it carries your brand, someone else sets the group cap, and the relationship with your own members belongs to a company you never signed with.

Visibility Into Your Own Community

  • Weekly and monthly signups, who is active now and in the last half hour, groups created, audio and video call volume, where your users are, and whether they arrive on mobile or web.

Rules You Write Yourself

  • Report reasons you write, a moderation queue for people and groups, the power to block either, and a group size limit you choose instead of one imposed on you.

Members Who Stay Yours

  • Accounts, conversations and media sit in your database on your servers, so nobody else can change the terms, throttle your reach or shut your community down.

What Changes When You Own It

  • Ownership changes the shape of the problem. Members, data, rules and name are all yours. Nothing about the everyday experience gets worse for the people using it, since they still open an app, tap a name and talk, but your position as the organizer improves on every axis.
  • 01 Your brand on the app, the splash screen and the notifications
  • 02 Your languages, including right-to-left, added without a release
  • 03 Your moderation rules and your own report reasons

Platform Features - Encrypted Chat, Calling, Stories & Community Tools

Private Conversations

  • The reason people open the app. Messages move from delivered to read, the typing indicator shows when the other person is answering, and search reaches back through the history when something from last month is needed.
  • Private conversations with anyone on the platform
  • Delivered and read ticks with typing indicators
  • Online status and last seen

Groups and Public Communities

  • Start a group, name it, add a photo and invite members. Make trusted people admins, remove anyone who should not be there, and open a group publicly so new members can discover it.
  • Named groups with a photo and member list
  • Promote, remove, or leave as an admin
  • Public groups people can discover and join

Media of Every Kind

  • Photos, video, voice notes, documents, GIFs, a location pin and a contact card. Video is compressed and thumbnailed on the phone before upload, so sending stays quick on a weak connection.
  • Camera or gallery photos and video
  • Voice notes recorded in the app
  • Documents including PDFs

24-Hour Stories

  • Photos and videos that disappear after a day, each with its own caption. The poster sees exactly who viewed, and any reply lands straight in a private chat.
  • Stories that expire after a day
  • Several photos or clips per story
  • A caption on each item

Replies, Reactions and Polls

  • Reply to one message in a thread
  • Forward to another chat

Star, Pin, Archive and Lock

  • Star what you will need later, pin something important for a day or permanently, move a quiet chat into the archive, and put a private conversation behind its own password.
  • Star messages to find them later
  • Pin for a day, a week, a month or for good
  • Archive quiet conversations

Deletion, Done Properly

  • Delete a message only for yourself, withdraw it for everyone, clear a whole conversation, or close the account entirely, each as a separate deliberate step.
  • Delete for yourself
  • Delete for everyone
  • Clear a conversation

Contact Sync and Discovery

  • Sync the phone book, see which contacts are already on your platform, give someone your own label, and search for people who are not saved yet.
  • Your own label for a contact
  • See which contacts are already here
  • Search by name or number

Notifications With Context

  • Alerts name the sender and say what arrived, whether a photo, a video or a document, instead of a blank ping, and incoming calls ring properly even with the app closed.
  • Push alerts that name the sender
  • Different wording per media type
  • Answer calls from the lock screen

Four Surfaces - iPhone, Android, Web & the Operator Console

The browser version is not a reduced copy either. Someone at a desk gets the same conversations, calls, stories and settings as someone on a phone, and can stay signed in on both with messages landing on each.

Operator Console - Analytics, Moderation, Branding & Languages

The console is where the platform is actually run, and it is built for an operations team rather than engineers. How the app looks, which languages it speaks, who is allowed in and what happens after a report are all forms in a browser rather than change requests.

Operator Console Sections

  • 01 The Dashboard Fifteen live figures: total users and the week-on-week change, groups and their trend, audio and video call counts, newest users and groups, signup curves by week, month and year, and where your traffic comes from.
  • 02 Who Is Online Now Who is active right now and in the last half hour, the mobile and web split, and which sign-in method people actually chose, so you know whether SMS is worth paying for.
  • 03 Reported Users Each incoming report with who filed it, who it concerns, the reason picked and the conversation it came from. Review it, mark it seen and block the account where needed.
  • 04 Reported Groups An equivalent queue for groups, holding every report against a group in one place, with the option to block the whole group instead of chasing members one by one.

Branding & Appearance

  • App and site name, primary and secondary colours, light and dark logos, favicon, banner, copyright text and store links, all editable by someone who has never opened a terminal.
  • App name, logo and brand colours
  • Light and dark logos, favicon and banner
  • Privacy policy and terms links

Languages & Translation

  • Add a language, translate it key by key or in bulk, switch it on or off, and choose which one new members see first.
  • Add and translate a language in place
  • Enable, disable and set the default
  • Right-to-left per language

What an engagement can include

One fixed price with everything below included and no conditions on what you do with it afterwards. Unlike a hosted chat service billed per user, nothing here stops working when a subscription lapses.

Full Source Code

  • The Node.js API, the Flutter mobile app, the browser client and the operator console, all yours to change, rebrand, redeploy and resell with no licence strings.
  • The full source, yours to keep
  • Change, rebrand or resell it
  • No licence fee or revenue share

Two Mobile Apps

  • iPhone and Android from a single Flutter codebase, so features land on both together, published under your own Apple and Google accounts with your name on them.
  • Two mobile apps, one Flutter codebase
  • Your own developer accounts
  • Feature parity on iPhone and Android

The Browser App

  • A complete web client for desk users with the same conversations, calls, stories and settings as the phone, served from your domain with nothing to install.
  • A browser app for desk users
  • Messaging, calling and stories
  • No install, nothing to update

The Operator Console

  • The dashboard, moderation queues, user and group management, branding, language tools and integration keys in a single browser interface.
  • An operator console
  • Fifteen live dashboard figures
  • User and group moderation queues

Deployment & Handover

  • Deployed on your infrastructure
  • Database and media storage configured
  • Your SMS, push, maps and email keys connected
  • A handover with your team

The Documentation Set

  • Requirements, data model, API reference, a developer and security handbook and a VAPT compliance document, written for your engineers to work from.
  • Product, schema and API docs
  • Developer and security handbook
  • VAPT and compliance reference

What White Label Actually Means Here

The phrase gets used loosely, and most white label messaging software is rented by the month. Here is exactly where the line falls on this platform.

The iPhone and Android app names, icons, splash screens and store listings, the browser client on your own domain, and the logos, colours, favicon, banner, legal links and sign-in methods set in the console. The interface speaks whichever of the sixteen languages you switch on, so a new brand is an afternoon of settings rather than a release.

Who Is This White Label Messaging App Built For?

It suits any organization whose people already talk to each other constantly and would rather that conversation happened somewhere it controls than in a group on a consumer app.

Schools, colleges and training providers who need class groups, announcements and staff-to-student contact inside a moderated environment with a record, instead of on personal phone numbers.

Use Cases - Community, Enterprise, Education, Resale & Sovereign Hosting

The case the platform was designed around. An organization with an active membership brings its conversation in-house under its own app, name, rules, group limit and moderation queue. Members keep the experience they know, and you gain a directory, a dashboard and the ability to remove someone properly rather than from a single group.

Internal communication the business actually owns. Messages stay on your servers, operators open and close accounts, the group limit is yours, and no consumer platform sits in the middle with terms that can change. Email sign-in suits an internal rollout where SMS costs money and everyone already has a work address.

Industries We Serve

The platform suits any operator whose audience already talks among itself. Membership organizations use everything from groups to moderation, enterprises lean on private hosting and account control, schools use class groups and public discovery, regional operators use the language engine, agencies redeploy per client, and public bodies self-host it entirely for data residency. For the wider sector view, see our technology and SaaS platform development page. For custom work beyond this product, see our social media app development service.

A sector missing here rarely means a poor fit. It usually means the conversation in that industry is happening somewhere nobody has yet thought to bring in-house.

How the Platform Works - Sign Up, Message, Call & Moderate

From outside a messenger looks like a list of names; underneath it is a tightly sequenced pipeline of identity, delivery, presence and moderation. This is the path from a phone number to a running, moderated community.

User Journey - From Phone Number to Moderated Community

  • 1 Signing Up Someone installs the app and proves they are reachable, before they can do anything else. They enter a phone number with its country code, or an email address if you prefer that route
  • A one-time code is sent by SMS or email and checked on the server
  • A session token is issued and stored, and the device is registered so notifications can reach it
  • They choose a name, an avatar and a language, and accept your privacy policy and terms

Technology options we may propose

Deliberately ordinary and easy to hire for: Node.js and Express on MySQL with Socket.IO for live delivery, one Flutter codebase for both phones, a browser client and a React console, chosen so the operating knowledge is common rather than rare.

Nothing here is unusual, and that is deliberate. Any capable Node and Flutter team can pick it up, so you are not tied to us or to a niche framework after handover.

How we would design for scale

Nothing exotic in the topology: a Node.js application behind a web server, MySQL as the system of record, file storage for media and a scheduled cleanup job. None of it needs a specialist, and nothing unusual has to exist before your first thousand users.

Messages and Media Grow Fastest

  • On a messenger the fastest-growing thing is not the user table but the message table and the media folder beside it. Every conversation keeps writing rows and every photo, clip and voice note lands on disk. The two levers that matter are indexes on the columns messages are fetched by and a plan to move media to object storage before disk becomes the limit, both cheap early and expensive late.
  • Live connections come second. One server holds a great many sockets comfortably, and because connection state is written to the database rather than memory, growing to several servers means an adapter and a load balancer, not a redesign.
  • As with any application of this shape, the database is the natural limit. Pooling is already in place, and growth brings the usual steps: secondary indexes on lookup columns, read replicas for heavier dashboard queries, and a retention policy for media you no longer need.
  • Calling is designed not to grow your bill. Voice and video run device to device, so call volume uses almost no server bandwidth, and the relay only carries the minority of calls where a restrictive network blocks the direct route.

Real-Time Connections

  • Persistent sockets instead of polling, with connection state in the database so several application servers can share load behind a balancer when needed.

Message Table Growth

  • The conversation tables grow fastest, and secondary indexes on the columns messages are fetched by are the highest-value tuning step, cheap when done early.

Media on Object Storage

  • Relative media paths turn a move to S3-compatible storage into a configuration change instead of a migration that rewrites every row.

Calls Off the Critical Path

  • Voice and video flow between devices rather than through your servers, so a heavy calling day costs bandwidth you never paid for.

Scheduled Cleanup

  • Story and pin expiry run on an hourly schedule, pinned to one instance in a multi-server deployment so the same cleanup never runs twice.

Process Management

  • PM2 manages restarts, clustering across cores and logs, the baseline reliability layer before any extra infrastructure.
  • None of it is needed on day one. One modest server runs the whole platform for a launch community, and each step above is taken when a real number calls for it, not in advance.
  • We size the first deployment with you at handover and write down which measurement should trigger which step, so the scaling plan belongs to your team rather than living in our heads.

Security and privacy requirements we can design for

A messenger holds identities, conversations and media, so its security posture is documented rather than asserted. Messages are end-to-end encrypted, WebRTC encrypts call media as standard, and a developer and security handbook plus a VAPT compliance reference both state plainly what the code does and what is your deployment work.

We would rather state plainly where the line falls than let your penetration test find it. The cards describe what the platform contains; what follows separates what we deliver from what belongs to your infrastructure team.

Describe your Messaging app

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com

More pages on this build

4 pages describing this proposed build.