Flowless
The open-source trust core: identity, sessions, and authorization. Pubflow hosts it by default. You can also use only managed Flowless and keep building in Cursor or Claude Code.
Open FlowlessBuild the whole app.This is the system around it.
Idea to Blueprint to apps to trust to deploy. Flowless, Flowfull, the library, and schema are how that system stays real — not a backend-as-a-service catalog.
One path instead of ten services.
The enemy is fragmentation plus glue. Pubflow is a connected application, not a pile of vendors.
01
Idea
Describe the product in plain language. The composer on the homepage is the same door.
02
Blueprint
The shared plan: features, apps, data, APIs, UI, security, and build order.
03
Apps
Web, mobile, and backend generated from that plan — not a chat that disappears.
04
Trust
Identity and authorization move with the request. Flowless is the open trust core; Pubflow hosts it by default.
05
Deploy
A path to production with source you can export and host yourself.
The mechanism, not the catalog.
You do not wake up wanting Flowless plus Flowfull plus UltraLoad. You want the application. These pieces keep it coherent.
Flowfull
The logic layer for backends that share the Blueprint. Node and Python today. Portable when you take the source.
Open FlowfullLibrary
Starter kits and clients so the stack you already like can sit on the same system: React, Next.js, Expo, and more.
Open the librarySchema
The data shape the Blueprint, APIs, and apps agree on — so agents are not inventing tables in a vacuum.
See SchemaKits live with the system.
Frontend and backend starters are in the library, not a separate product aisle. Grab what matches your stack and keep the Blueprint.
Start with an idea.
Build the whole app. The ecosystem is how that app stays one system.