Workspace-scoped CRM foundation

Customer intelligence that stays inside the workspace.

Create a protected workspace, manage customer and deal records, and keep the data boundary visible. PulseBoard starts empty by design—no fabricated revenue and no invented customer records.

Explore the security model

Live onboarding validated Real-data empty states

ACTIVE BOUNDARYYour secure workspace

RLS protected

CustomersReal account records

ContactsWorkspace relationships

PipelineDeals with context

Scoped queries only

DashboardWorkspace-only totals

Authenticated access

Supabase Auth PostgreSQL RLS Workspace CRM Manual integrations

Product workflow

Build context from real workspace records.

PulseBoard keeps its product claims small and verifiable: workspace data, CRM records, pipeline context, and calculated roll-ups.

Workspace by default

Workspace creation is bound to the authenticated caller. Row-level security scopes product data to the workspace.

Start with real records

Add customers, contacts, and deals when there is real information to manage. Empty workspaces stay visibly empty.

Pipeline with context

Keep a deal’s stage, value, probability, expected close, and customer link together in one workspace view.

Explicit data boundary

A public product page should not hide the security model.

PulseBoard’s browser client uses only public Supabase configuration. Workspace ownership and access rules remain in the database, while provider credentials stay server-side.

See current boundaries

Caller-bound onboardingThe database derives the workspace owner from the authenticated caller.

Workspace-scoped recordsCustomer, contact, and pipeline queries are filtered by the active workspace.

Server-only provider pathAI requests require a signed-in session and server-side configuration.

Honest product status

Useful foundations, deliberate limits.

AI stays unconfigured by default

The AI Analyst is behind a server-side boundary and remains unavailable until a provider is configured.

Integrations stay opt-in

GitHub and HubSpot connection paths are user-authorised and manual. No sync starts automatically.

No audit claim

These are source-backed product boundaries, not a claim of a third-party security audit.

Start with a protected workspace

Keep the customer context where it belongs.

Open a secure workspace to add your own records. PulseBoard will not fill the product with sample business data for you.