Skip to main content
All CollectionsSecurity & Compliance
Flowbox system architecture and security
Flowbox system architecture and security

A summary of the Flowbox platform, system architecture and security

Updated over a week ago

Flowbox's platform and solutions have been developed by an in-house development team, all based in Stockholm, Sweden.

From the first iteration, the platform has been built to scale and continuous investment in talent has meant we have been able to develop new innovative features and deliver ongoing quality control and upgrades.

The Flowbox platform

The Flowbox platform is divided up into three areas.

1. Client portal

Users can log in to the main Flowbox platform with their unique login and password. In the Flowbox platform, admin users can manage the collection, moderation, optimization, and distribution of content. Admin users can also invite and manage their team members' access to Flowbox.

Some areas of the client portal functionality can also be accessed through the iOS app (Publish function) and the Chrome Extension (sending Rights Requests). Users must log in to the app and Chrome Extension with their unique Flowbox login and password.

2. External interface

Flowbox Flows are shared externally on client websites through our embed script, which feeds data back to Flowbox for insights and analytics.

For the Commerce product, Flowbox check-out script is embedded onsite as well, and these are linked back to the Flowbox platform for insights and analytics.

Flowbox Flows can also be embedded in email via an HTML embed code.

Flowbox also connects to other external third-party services in order to pull and push data, including our technology partners like Trustpilot for example, social media companies, Google Shopping Feed, and more.

3. Admin portal

This is our back-office access into the Flowbox platform, where Customer Success Managers can log in to support client activities and the Support Team can carry out troubleshooting activities.

Real-time capability

To cope with and serve the high load of platform requests, Flowbox invests in robust serving infrastructures, caching and monitoring. Flowbox also uses a content delivery network (CDN) to serve media content.

To improve load times, images in Flowbox are lazy loaded and in the modern webP format. That means that they are optimized to serve the best size for your customers' device type, screen size and resolution.


Flowbox uses CDN and Redis cache to eliminate system stress and bottlenecks, as well as to optimize delivery performance and response times.

Flowbox databases are housed through Amazon Web Services (AWS) ensuring compliance with all industry best practices.

Flowbox utilizes Amazon Athena to perform data aggregations for our Insights tool and for our AI algorithm Flowscore.

System security


Flowbox connects to the AWS VPC (virtual private cloud) service for a secure, encrypted environment.


All Flowbox databases are located on the private subnet in the AWS VPC, without public access.


We perform daily backups of our databases, with AWS RDS snapshot capabilities.


Clients' accounts can be accessed from our back-end Admin portal, which is available to Support, Customer Success Managers and Moderators (if the client has requested this). All user logins are secured with two-factor authentication (2FA).


Did this answer your question?