About PubliScope

We build live broadcast infrastructure for organisations that operate more than one official Facebook Page.

The problem we solve

Large organisations rarely have one Facebook Page. A political party has a national Page and separate Pages for each state and district. A news network has Pages for each region and language. A retail chain has a Page per city. A religious or social organisation has a Page per chapter.

Each of those Pages has its own audience — people who chose to follow that particular Page because it is local to them, or in their language. That audience does not necessarily follow the national Page.

So when the organisation holds a live event — a rally, a press conference, a product launch, a festival — it faces a problem that has no good manual answer:

An event happens once, but the audience is spread across dozens of Pages.

Streaming only from the main Page means every regional audience misses it unless they go looking. Starting the stream by hand on 50 Pages means 50 people must be present, trained and awake at the same moment — and each broadcast still begins at a different time.

What we built

PubliScope takes a single live stream from the organisation's encoder and publishes it to every Facebook Page the organisation administers, at the same moment, from one button.

The operator streams once. Every connected Page carries the same live video. When the operator stops, every Page stops. Nobody at the district level has to do anything — they connect their Page once, and never touch it again.

How the broadcast reaches every Page

Encoder OBS or phone RTMP / SRT 1 stream PubliScope Normalises the stream Creates a live video on every Page National Page ● live State Page — Maharashtra ● live State Page — Punjab ● live District Page — Nashik ● live District Page — Jalna ● live

One encoder, one internet connection. Each Page receives its own live video created through the Facebook Live Video API, fed by the same source stream.

Why this matters to the organisations we serve

The audience sees it where they already are

Someone in Nashik follows the Nashik Page. They may never have followed the national Page. When the event appears in their feed from the Page they chose to follow, in their own region's context, they watch it. The same broadcast on a distant national Page would not have reached them at all.

Local teams stop being a bottleneck

Before, going live on 50 Pages meant 50 people with the credentials, the training and the availability to start a broadcast at exactly the right minute. In practice some started late, some missed it, some streamed the wrong thing. Now the district administrator connects their Page once and is never needed again.

The organisation knows what actually happened

Our console shows every Page in real time — which went live, which failed, and why. If one Page drops mid-event the operator can restore just that Page, or stop just that Page, without interrupting the rest. Without this, nobody discovers a Page missed the event until afterwards.

One event, not fifty separate ones

Because every Page starts within the same few seconds, the organisation's audience experiences a single shared moment rather than fifty broadcasts trickling out at different times.

Before and after

Doing it by hand 50 people must each be present at the right minute Each needs credentials and training Broadcasts start minutes apart Some Pages are simply missed Nobody knows which Pages actually went live Coverage: unpredictable With PubliScope One operator presses one button District admins connected their Page once, months ago Every Page live within about 20 seconds Failures are visible and can be retried instantly A single shared moment across the whole network Coverage: every connected Page, verified

How we think about access and consent

A tool that publishes to other people's Pages has to be careful about how it gets that access. Three rules are built into the product, not just written in a policy:

What we do not allow

PubliScope is for organisations broadcasting to their own official, openly affiliated Pages. It is not for making separately-branded or seemingly independent Pages carry identical content — that breaches Meta's Platform Terms and our own Terms of Service, and we suspend accounts that do it.

What we access, and what we never touch

We read or writeWe never access
Page name and category Posts, comments and reactions
Follower count (Facebook requires 100+ for live video) Follower lists or anything about individual followers
Creating and ending live videos on connected Pages Page inbox and messages
Whether each live video started successfully Personal profiles, friends, photos
Ads, ad accounts and payment information

The full detail is in our Privacy Policy, including how long each item is kept and how to delete it.

Who we are

PubliScope is built and operated by Grok Media Private Limited, a company registered in India, by a team that has run digital communications for large multi-region organisations. We built this because we needed it ourselves and no existing tool did the job: general multistreaming services publish to a handful of fixed destinations, not to hundreds of Facebook Pages each needing its own live video created at broadcast time.

Questions, or want to talk about your organisation's setup? Write to salman@publiscope.io.