LeaderOS

How LeaderOS fits together

Execution System → Executive Intelligence → AI-native leadership OS. The same problem—less administrative load on leaders—with layers added over time.

Conceptual evolution

Execution management — commitments, people, calendars, compliance.
Leadership analytics — OHS, EPS, delegation and team signals.
Executive intelligence — narrative briefs, command center, learning insights.
AI-native direction — provider-agnostic AI, agent APIs, emerging Executive Memory.

Platform architecture

                    LEADEROS CORE
                         │
        ┌────────────────┼────────────────┐
        │                │                │
       CES            STRATEGY         MEETINGS
        │                │                │
    DELEGATION       DECISIONS         LEARNING
        │                │                │
        └────────────────┼────────────────┘
                         │
               EXECUTIVE INTELLIGENCE
                         │
                AI / AGENTS / MEMORY

Strategy to measurement

Strategy
Initiatives
Commitments
Execution
Measurement
Executive intelligence

Public site vs authenticated product

This marketing surface is static and crawlable. The product runs behind authentication at routes such as /dashboard, /director, and /board. A future app.leaderos.com.mx split is possible but not required for the current deployment.

Technical stack (verified)

Next.js App Router · TypeScript
PostgreSQL · Drizzle ORM
NextAuth (credentials + Google)
Per-user Google Calendar OAuth
Scheduled jobs (cron / GitHub Actions)
Agent HTTP APIs with tenant isolation