Skip to content
AI-powered decisions, with human authority always. · Your systems stay authoritative
LeadershipOSDaffodil operating system

Service status

What is running, and what is enabled per deployment.

This page exists so nobody has to guess. It says which parts of LeadershipOS are running here, which are turned on during a deployment, and which are deliberately off until somebody approves them.

  • Public site

    Running

    Published content, edited by named web administrators

  • Workspace

    Running

    18 modules, API-backed, gated at every surface

  • Governed API

    Running

    Access ladder enforced server-side

  • Source connectors

    Per deployment

    Built against your systems during onboarding, one boundary at a time

  • Write-back to source systems

    Off by default

    Enabled only for a scope your team has approved

  • Sign-in and sessions

    Running

    Real credential check; access level derived from the assignment

  • Organisation SSO

    Running

    Odoo is the identity provider and assignment authority

  • MFA / recovery

    Not built

    A tenant's own identity provider would enforce these

  • Lead routing / CRM

    Not connected

    Forms validate and stop

  • TLS on the demo host

    Not configured

    Plain HTTP on an IP; needs a domain

Gate status is unchanged by anything on this page: no live source integrations, no real tenant data, write-back disabled. Treat it as a working demonstration of governed patterns.

Controlled next step

Discuss what would have to be true before a pilot.

Approvals, named owners, source access, restore proof and rollback criteria come before any expansion of scope. That order does not change under a deadline.