Sign In

We're the bridge between marketing ambition and financial wisdom. Born from the frustration of seeing e-commerce companies chase growth at any cost, we built a platform that turns complex customer data into simple profit signals.

Ready to turn your marketing budget into pure rocket fuel? 🚀

Drop us a line at hello@headw.ai and let's explore how we can boost your ROI. (We promise the demo will be worth your time!)

© Copyright 2026 Headwai. All Rights Reserved.

    Legal
    • Privacy Policy

    Database Overview

    Understanding the database schema and table structure in your application.

    Note: This is mock/placeholder content for demonstration purposes.

    The database schema is designed with a multi-tenant architecture that supports both personal and team accounts.

    Core Tables

    Users Table

    The users table stores user authentication data and is managed by Supabase Auth:

    • id - Unique user identifier
    • email - User's email address
    • created_at - Account creation timestamp

    Accounts Table

    The accounts table represents both personal and team accounts:

    • id - Unique account identifier
    • name - Account display name
    • slug - URL-friendly identifier
    • is_personal_account - Boolean flag for personal vs team accounts

    Projects Table

    Store your application's project data:

    • id - Unique project identifier
    • account_id - Foreign key to accounts table
    • name - Project name
    • description - Project description
    • created_at - Creation timestamp

    Relationships

    All data in the application is tied to accounts through foreign key relationships. This ensures proper data isolation and access control through Row Level Security (RLS).

    Next Steps

    • Learn about migrations
    • Understand RLS policies