Pubflow Schema Explorer

Understand the core structure behind Pubflow + Flowless

A friendly map of core tables, optional modules, and migration-ready SQL snippets so teams can move fast across engines.

Open PlaygroundRequest an Extension
How trust flows
Flowless handles identity, Flowfull handles your business logic.
Client App
Web, mobile, or desktop sends a session id.
session_id
Flowfull Backend
Validates sessions through bridge validation and applies your app rules.
bridge validation + trust token
Flowless Auth Core
Issues trust context, sessions, tokens, and secure identity state.

Core Tables and Extensions

Portable schema style: SQL-first, production-safe, and database-flexible.

Coreusers
Users
Identity, profile, verification, and account-level metadata.
  • id
  • email
  • password_hash
  • is_verified
  • two_factor
  • created_at
Coresessions
Sessions
Session lifecycle, security context, and 2FA verification status.
  • id
  • user_id
  • status
  • expires_at
  • two_factor_verified
  • created_at
Coreuser_accounts
User Accounts
OAuth and social providers linked to each user.
  • user_id
  • provider
  • provider_user_id
  • access_token
  • refresh_token
Coretokens
Tokens
Password reset, verification, and one-time action flows.
  • token
  • token_type
  • identifier_value
  • attempts_remaining
  • status
  • expires_at
Infrarate_limits
Rate Limits
Infrastructure safety bucket for anti-abuse controls.
  • key
  • points
  • expires
Moduletwo_factor
Two-Factor
Method-level state for OTP, email, SMS, and passkey extensions.
  • user_id
  • method
  • code
  • token_prefix
  • status
  • metadata
Moduleposts
Blog Posts
Modular content system with status, visibility, and publishing controls.
  • user_id
  • lang
  • title
  • slug
  • status
  • visibility
  • published_at
Interactive migration helper
Choose a table and database engine to get a starter SQL snippet aligned with the Pubflow style.

Default core-table bootstrap

CREATE_REQUIRED_TABLES is true by default. You can change it if needed. When enabled, Flowless creates all core tables internally with a secure bootstrap flow.

# default
CREATE_REQUIRED_TABLES=true

# optional override
CREATE_REQUIRED_TABLES=false

Pick table

Pick database

PostgreSQL dialect

-- PostgreSQL migration helper
-- Source style: pubflow flowless core (portable SQL-first)

CREATE TABLE IF NOT EXISTS users (
  id TEXT PRIMARY KEY,
  email TEXT NOT NULL UNIQUE,
  password_hash TEXT,
  is_verified BOOLEAN NOT NULL DEFAULT FALSE,
  two_factor BOOLEAN NOT NULL DEFAULT FALSE,
  metadata JSONB,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

-- Optional upsert example
INSERT INTO users (id, email) VALUES ('user_1', 'dev@pubflow.com')
ON CONFLICT (id) DO UPDATE SET updated_at = CURRENT_TIMESTAMP;
These snippets are migration starters. Keep your IDs, indexes, and constraints aligned with your production requirements.
Modular by design
Pubflow starts lean and grows with modules.

Blog Module

Blog module includes posts, categories, tags, and optional comments/reactions/bookmarks/stats extensions.

Two-Factor Module

Two-factor module adds dedicated method tracking and secure verification states.

This is just the beginning. We actively receive feature and module requests.

Try your flow now
Experiment in the playground or request a new module for your use case.
Go to playgroundSend feature request