A seamless example of how Core + Apps + Components come to life.
You're building an audio library inside Webflow — for example, a collection of guided meditations or audio lessons.
You want:
Webflow doesn't support:
By combining Waveflow (audio player app) with all six Core modules, you get a fully modular, native Webflow audio system: ❤️
🎧 WAVEFLOW
A fully native audio player built from Webflow elements — no embeds, no code. Plays tracks, emits events, and responds to conditional logic. Completely free ❤️
📦 LIBFLOW
Handles hosting and streaming of all audio files (.mp3, .wav...). Fast, reliable delivery with no file size restrictions.
⚙️ IFLOW
Adds conditional visibility inside Webflow — e.g. show certain tracks only to users with specific tags, levels, or progress.
⚙️ UFLOW
Manages user accounts, login/signup, and user-specific data — like listening history, favorites, or custom access rules.
⚙️ DYNFLOW
Structures your content dynamically with Webflow CMS — organize tracks by level, category, or speaker, and connect them to user profiles or progress.
⚙️ DYNFLOW
Structures your content dynamically with Webflow CMS — organize tracks by level, category, or speaker, and connect them to user profiles or progress.
still have questions? Email us at hello@flowwwtin.com, we answer within 24 hours.
Core provides foundational logic and is the powerhouse of the Flowwwtin' ecosystem.
It consists of multiple modules that handle things like user accounts, file hosting, analytics, events, and conditional logic.
For example, let’s say you want to add an audio player to your website — you can do that completely free of charge. But since Webflow doesn’t support .mp3 hosting, you’d need a way to store your audio files. By connecting our free audio player app to our hosting module (Libflow), you’ll be able to host and play as many audio files as you need.
Apps are standalone tools like an audio player, PDF viewer, or multi-step form. They work without a subscription, but can connect to core — for example, if you're using the audio player and need a place to host your audio files, you can activate a Libflow subscription.
Components are free pre-built UI elements — like an upload button — that usually require a core app to function. For example, the upload button only works with an active Libflow subscription.
Yes — that’s the point. Core modules act as a shared layer. For example, Libflow (a core module providing hosting) can power an audio player, file upload button, file download button... — with one subscription.
Yes — all apps work independently for free. You only need to connect them to one or mode core modules if you want the functionality provided by a core module (hosting, gated content, analytics..)
No — most components need a core module to function. For example File Upload Button only works with an active Libflow subscription.
All apps and components are completely free to use, forever. Paid core modules do not include free trials or free tiers, but we offer a no-questions-asked full refund within 7 days of purchase if it’s not what you expected.
No — Flowwwtin' is fully modular. You only pay for the core modules you actually need. Everything else is free to mix, match, and layer on top.
Yes — you can upgrade, downgrade, or cancel anytime with no lock-in.
The features powered by that core module will stop working, but your site won’t break. Visual elements remain — only the interactive logic is disabled.
Yes — Flowwwtin' apps can be used across unlimited Webflow projects with one subscription within a single workspace. Each subscription is tied to a workspace, not an individual site. If you use one workspace for all your projects, core apps will work across all of them.
You can also create multiple workspaces — for example, one per client — and subscribe separately if needed.