Beta

Data isolation, identity, state, and approved integrations.

This page is the technical map for how FoundComp separates user identity, company data, UI state, AI orchestration, and MCP-connected business tools.

Identity, company scope, and state boundaries.

This view shows how the app proves who the user is, resolves the active company, and separates UI state from company truth.

  • Sign in

    IAM

    User authenticates before private workspace access. Public marketing and resources remain indexable.

  • Resolve membership

    company membership

    The app checks which companies the user can open and what plan/access level applies.

  • Open active company

    active-company guard

    All workspace routes resolve against one active company ID so cross-company data is not mixed.

  • Company truth

    Logic API

    Company, goals, documents, decisions, health, approvals, and memory belong behind the Logic API rather than in the browser.

  • Company-scoped workspace

    tenant boundary

    Every view is loaded for the active company. Company switching clears the previous context before rendering the next workspace.

Operating stack

The model is last — not first.

  1. You — the founder

    Ask · Visual / Classic

  2. FoundComp

    App · weekly loop · memory

  3. Identity & access

    IAM

  4. Company control plane

    Logic

  5. Intelligence

    AI Service · Orchestrator · skills · agents

  6. Guardrails

    Policies · GDPR posture

  7. Connected tools

    Only after Approve

    Books, inbox, files — your accounts

Need product positioning instead?

Product overview and target user personas live on the overview page. Homepage value propositions live on the homepage.