Part of the Mediaflow ecosystem
Approved images, logos, press photos and other material are already in your Mediaflow account. That means a faster workflow in a crisis, when speed is essential.
When a crisis strikes, information needs to get out fast. With a crisis web in Mediaflow, you get a channel separate from your regular website – prepared in advance and always ready. You handle publishing yourselves in an environment you already know, with ready-made content blocks and direct access to approved material from your Mediaflow account. Fast, secure communication in a familiar and well-liked tool.
Approved images, logos, press photos and other material are already in your Mediaflow account. That means a faster workflow in a crisis, when speed is essential.
You publish the site and manage the content yourselves (without involving your IT department). The crisis web is built on the same platform that powers our Brand Portals and Play portals.
Pages are delivered as pre-built, cached pages and no information is fetched from a database, so your crisis web can handle the traffic spikes a crisis brings.
Your Mediaflow crisis web runs on our own servers in Sweden, in a GDPR-compliant environment.
With a crisis web in Mediaflow, you have an easily accessible channel that is prepared in advance and always ready. During the crisis, you update the content and publish continuously.
A site connected to your image bank, with ready-made content blocks, in an interface you already know.
Anton Gustafsson
Head of Security and Protective Security Officer, Kramfors Municipality
The crisis web is a dedicated website for crisis information. It is completely separate from your regular website and keeps working when your regular site is overloaded, under attack or down. You get a standby domain that is always active. If you want to use your regular web address to show the crisis information, you can add this as an option. You create the content for the crisis web yourselves in an admin interface in Mediaflow, using ready-made templates and blocks. You can then update the content and publish pages within 30–60 seconds.
The site is delivered as static HTML and runs in parallel on our own two servers in Sweden, in a GDPR-compliant environment. If one goes down, the other takes over automatically within seconds. DDoS protection scales up automatically, so the crisis web holds up even during an attack. The site is always encrypted, and visitor statistics are based on server logs – no cookies, tracking or consent banners.
A dedicated website for crisis information, technically separate from your regular website. You build and publish it yourselves in Mediaflow.
In a crisis, your regular website can become overloaded, be attacked or go down. A separate channel ensures that information gets out quickly even when everything else is down.
Mediaflow's own solution – the same platform that powers our brand portals and Play portals.
No. The crisis web is connected to your Mediaflow account. You build the site yourselves with ready-made blocks and publish within 30–60 seconds.
No. You control content and publishing yourselves. The exception is if you have chosen to use your regular domain for the crisis web – in that case, your IT department needs to repoint the regular domain.
Your own domain such as alt.example.com, preconfigured with a CNAME record pointing to the crisis web infrastructure. It is always active, so no activation is needed during a crisis.
Our crisis webs run in parallel in two different Swedish data centers. If one fails, the other automatically takes over within seconds, without you or your visitors noticing anything.
Yes. Proxy-based DDoS protection acts as an automatic fallback. The proxy handles the scaling, providing virtually unlimited capacity during an attack.
Level 1 has two Swedish edge nodes with approx. 1 Gbit/s burst capacity each, approx. 2 Gbit/s in total. Level 2 has four edge nodes, two per data center, which doubles the capacity per location.
Yes. The security certificate is renewed automatically, so the site is always encrypted and shown as secure in the browser.
No. You keep full control of your DNS, and we never touch it. That's why, during onboarding, we work with your IT department to create a clear emergency procedure, so the change can be made even when a crisis strikes.
Usually, but it depends on your DNS provider. Apex domains can rarely use regular CNAME records, so the solution is ALIAS/ANAME records with your provider or CNAME flattening at the proxy. We advise on a case-by-case basis.
Throughout the crisis. Once your regular domain points to us, all traffic to www.example.com passes through the proxy provider until you point it back.
Curious about Mediaflow but not sure where to start? Book a no-obligation chat. We’ll listen to your needs and help you explore the right next steps.
Already seen everything you need? Book a demo.