Pubflow supports open source because standards should be shared.
Open by default
The core ideas behind Pubflow are designed to be portable: your language, your database, your backend, your rules.
Managed when useful
Pubflow can host Flowless, Bridge Payments, and other services, but the standard stays understandable and self-hostable.
Community shaped
New clients, starters, scanners, and utility tools can grow from real requests instead of closed roadmaps.
Open tools around the Pubflow Trust Layer.
Start with Flowfull, then use supporting projects for payments, fast state, and frontend security.
Flowfull
Flowfull is the custom backend side of the Pubflow standard. It trusts Flowless as the core authentication layer, uses Pubflow as the standard trust layer, and leaves your business logic, language, and database in your control.
- MIT-friendly foundation for backend services that trust Flowless sessions.
- Designed for custom backends, or several backends, under one portable trust model.
- Keeps auth separate from business logic so teams can build cleaner systems.
Native Payments
Native Payments is a modular, multi-provider payment system for SaaS, eCommerce, and digital stores. It gives teams a universal payment architecture instead of wiring each provider from scratch.
- Supports multiple providers and business models from one modular structure.
- Useful for subscriptions, checkout, digital stores, and provider migration paths.
- A practical open foundation for building payment systems with less lock-in.
Redge
Redge gives teams a Redis-compatible workflow for fast app state while persisting data into durable backends such as D1, Turso, LibSQL, Postgres, or MySQL.
- Use familiar Redis clients and commands without rewriting the app.
- Great for sessions, rate limits, flags, leaderboards, and hot reads.
- Pairs naturally with edge apps that still need durable storage.
FrontGuard
FrontGuard scans frontend apps for client-side vulnerability patterns, helping teams catch browser-exposed risks before they become production issues.
- Focuses on browser-facing security risks in frontend applications.
- Helps product teams understand what to fix and why.
- Fits the Pubflow philosophy: security should be easier to adopt early.
Want a new starter, scanner, client, or open-source utility?
Tell us what would help your team. Pubflow uses requests to prioritize new open-source projects, integrations, regions, SDKs, and utility tools.