Industries. Five sectors, one platform.
How banking, fintech, insurance, marketplace and food and beverage teams use ContentFlow to change in-app content without waiting for a release.
Each page sets out the pressures that sector works under, four things a team could build, and which ContentFlow products do the work. The examples are illustrative: they describe what the platform supports, not a named customer.
One control plane, five sectors.
The same eight products, pointed at five different sets of pressure. Each page sets out what that sector is up against and what a team could build for it.
One place all five sectors work in.
Where the pressure lands.
Banking
Govern approved banking guidance across fast-changing in-app customer journeys.
Approved content, in context.
Fintech
Coordinate wallet education, reactivation and status content from one control plane.
Guidance at product speed.
Insurance
Control policy, claim and renewal guidance across changing customer states.
Content that follows status.
Marketplace
Coordinate seller guidance, buyer notices and bilingual marketplace content.
Buyers and sellers, one plane.
Food and beverage
Control menu, daypart and branch content across every ordering screen.
Menus that move with the day.
Residency, certification and integration.
Data residency. Today ContentFlow runs as a single deployment on infrastructure located in Riyadh, Saudi Arabia, so production content and end-user data are processed in the Kingdom; that is a property of how we are currently deployed rather than a control the product enforces, encrypted backups and some third-party processors are handled outside the Kingdom, and an in-Kingdom-only arrangement is something we agree in writing on an Enterprise plan rather than something this page can promise.
Certifications. Our controls are built around the requirements of the Saudi PDPL. Backups are encrypted with AES-256 and restore-tested. HTTPS is enforced across the site. SOC 2 Type II and ISO 27001 are planned.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.
One engineering integration up front. After that your team publishes content changes without a new app build and without a new app store submission.
Integrate once.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.