Two ways to run it

Run Media Verdict on your own servers, or as one client of the shared system. It is the same build either way.

1. Your own installation: every service and store runs for your organisation alone, in a database no other client uses.

2. The shared system: services and detection models are shared, and each client’s watch lists, results, budget and users are kept apart.

Media Verdict console
1 2
Illustration

Your own installation or the shared system

Your own installationThe shared system
Where it runsYour own servers in India, or a database of your ownServers in India, shared between clients
Who operates itWe install it; who runs it day to day is agreed with youWe run it; a few named people on our side can switch between clients, and every switch is logged
SeparationNothing is shared with any other clientEach client sees only its own data. One client’s labels, rules and budget never change another’s results
UpdatesThe regression set runs on every release; maintenance is announced 48 hours aheadThe same: the regression set runs on every release; maintenance is announced 48 hours ahead
Sign-inYour identity provider, by single sign-onSingle sign-on; each user belongs to one client and sees only that client

India region

All data, logs and reports are stored in India: collected posts and media, the records built from them, evidence packs, reports and the audit trail.

Some analysis uses services that run outside India, for example the language model that writes the headline paragraph of a report. What they return is stored in India with everything else.

On your own installation the servers are yours, in India. In the shared system every client’s data is stored in India.

Sign-in

  1. Single sign-on

    Users sign in through your organisation’s identity provider. Roles come from its groups, and the product stores no passwords.

  2. Two factors for approvers and admins

    Required for the approver and admin roles.

  3. Every change has a name

    Every write records who made it, and each user has an audit trail of their own.

Support and service levels

  1. 01

    Uptime

    Measured monthly for the console and alerts against the target in your service agreement. Your team can read status on the health screen.

  2. 02

    Incident communication

    Within 30 minutes of a serious incident, on the channel you choose.

  3. 03

    On call in busy periods

    During periods you declare, such as election phases, someone is on call and acknowledges within 15 minutes. Outside them, by the next business hour.

  4. 04

    Maintenance

    Announced 48 hours ahead.

Getting started

  1. Week 1

    Access

    The installation is set up in India. You connect your official accounts, identity provider and alert channels, set budgets, and submit the review that Instagram and Facebook replies need.

  2. Days 5 to 10

    What to watch

    A workshop turns your topics, keywords in each language, hashtags and accounts into a watch list, imported with its projected cost. Rules are tried on the first day of data before any is switched on.

  3. Weeks 2 to 5

    Baseline

    Three weeks of collection before anything is trusted. Calibration needs this history; until it has run, probabilities are labelled uncalibrated. Your analysts label items in the same weeks.

  4. Weeks 2 to 5

    People

    Analysts, an approver and a policy owner are named and trained, and an on-call rota is set for busy periods.

  5. Week 6

    Go-live

    The first external report is approved and delivered, replies are switched on platform by platform, and a weekly review begins.

Questions

Can we run it on our own servers?

Yes. The same build runs as your own installation, with a database no other client uses.

Where is our data stored?

In India, in both forms of deployment. Some analysis uses services outside India, and the Data residency page describes them by kind.

How long before the first report?

A first internal report is possible in about a week. A report you can rely on outside your organisation takes five to six weeks, because calibration needs three weeks of your data.

What do we need to bring?

Named people for the analyst, approver and policy owner roles, your identity provider, your official accounts, keyword lists in each language and budget figures.

Decide which form of deployment fits your organisation’s rules, with the people who run it.

Request a demo