ComplyOS

ComplyOS is a compliance operating system / compliance workflow tooling that helps operators and builders running compliance workflows structure compliance work with an OS-like tool surface.

TL;DR: ComplyOS — compliance operating system / compliance workflow tooling. Best for operators and builders running compliance workflows.

HR/L&D compliance operations and learning-evidence MCP/API/CLI toolkit

ComplyOS turns HRIS, LMS, and CSV learning records into tenant-scoped evidence, gap reports, DSR workflows, retention cleanup, and readiness packets for HR, People Ops, L&D, security, and campus teams. It is readiness/control-mapping software, not a certification badge or automated employment-decision system.

ComplyOS is also the live compliance/evidence module inside the working-title LearningOps Suite: a modular HR/L&D automation suite for intake, rosters, scheduling, regulatory awareness, instructional design, training specialist workflows, microlearning, evaluation, and manager briefs. The suite uses explicit maturity labels so live capability, contract interfaces, synthetic demos, and roadmap modules are not blended.

Regulatory awareness is defined as RegWatch v0: official source monitoring, source provenance, coverage-gap disclosure, and human-approved proposals before any rule, training, or notification changes state. The Source Intelligence spine now includes DB-backed schedules, job execution receipts, review UI, API/CLI export packets, and local fallbacks so external API procurement does not block hardening.

LearningOps demo packets are synthetic and explicitly labeled:

• Training from scratch

• Fix messy existing training operations

The landing/design direction is captured in DESIGN-SYSTEM.md.

Why ComplyOS?

Enterprise compliance tracking still runs on CSV exports, stale dashboards, screenshots, and "I thought they completed that" moments. ComplyOS treats learning compliance as an evidence problem:

• Evidence-backed audits — Reports cite tenant-scoped SHA256 evidence entries and action logs.

• Import governance — Preview/quarantine/promote CSV rows instead of letting bad exports mutate truth.

• Privacy workflows — Create DSR cases, require controller approval, block deletion on legal hold, and dry-run retention cleanup.

• Security and governance packets — Collect readiness-only SOC 2-style control evidence and AI/school/FCRA boundary packets for review.

• Source-intelligence review spine — Schedule local checks, store review proposals, decide them through RBAC, and export audit packets before any downstream rule or module changes.

• Notification outbox, email, and signed hooks — Queue email, Slack, Teams, or customer webhook deliveries with payload hashes, retry state, dry-run drain, channel/event kill switches, and HMAC headers instead of coupling jobs to network uptime.

• Authenticated web shell — Ten live modules (Overview, Gaps, Imports, Records, Evidence, Remediation, Source intelligence, Privacy & retention, Readiness, Administration) served at /shell from the same service layer. Signed-session cookie auth, WCAG 2.2 AA contrast enforced by tests. Not a mock: every module reads real service data.

• Proposal-only AI layer — AI can suggest field mappings, anomaly summaries, gap explanations, remediation-message drafts, and duplicate clusters, but cannot mark a learner compliant, promote imports, execute remediation, or change rules. PII is redacted before hashing. Every proposal has a reject + expiry lifecycle and full provenance hashes.

• Agent-native surfaces — Use the same service-backed workflows through CLI, API v1, MCP tools, or the web shell.

• Local-first — SQLite by default, PostgreSQL-ready URLs when deployment needs them.

Related MCP server: Enterprise Financial Compliance Audit Framework

Pricing

Published and flat per tenant — no quote-only gate: a paid pilot at $2,500–$7,500 (credited in full to a year-one license), then self-hosted annual tiers at Entry $6,000 / Core $12,000 / Enterprise from $24,000 per year. No auto-renewal, no per-learner metering — details in docs/pricing.md.

Architecture

┌──────────────┐  ┌──────────────┐  ┌──────────────┐  ┌──────────────────┐
│  CLI (Typer) │  │  API v1      │  │  MCP         │  │  Web shell       │
│  complyos *  │  │  FastAPI     │  │  FastMCP     │  │  /shell (cookie) │
└──────┬───────┘  └──────┬───────┘  └──────┬───────┘  └────────┬─────────┘
       │                 │                 │                    │
       └─────────────────┴─────────────────┴────────────────────┘
                                   │
                    ┌──────────────▼──────────────────┐
                    │   Application SERVICE layer      │
                    │  ActorContext + require_perm(*)  │
                    │  (AuditService, EvidenceService, │
                    │   ImportService, PrivacySvc, …)  │
                    └──────┬──────────────┬────────────┘
                           │              │
              ┌────────────▼───┐   ┌──────▼───────────────────────┐
              │  Auditor /     │   │  LocalRepository (mixins)    │
              │  Rules engine  │   │  core | privacy | notif |    │
              └────────────────┘   │  source-intel | import | ORM │
                                   └──────────────┬───────────────┘
                                                  │
                    ┌─────────────────────────────┴──────────────────┐
                    │               Connectors                        │
                    │  CSV  │  Workday  │  SAP SuccessFactors  │ CSOD │
                    └────────────────────────────────────────────────┘

Tenant model

ComplyOS runs single-tenant at runtime with a tenant-aware data model: every persisted row carries a tenant_id so the schema is ready for a later migration without backfills. Multi-tenant / SaaS hosting is not built — see docs/multi-tenancy.md for the full posture, what is guaranteed today, and what must change before shared deployment is safe.

Source of truth

Forgejo is the source-of-truth remote for ComplyOS. Do not push ComplyOS changes to GitHub unless the repository owner explicitly asks for a mirror or legacy export.

Quick Start

Getting the source

ComplyOS is source-available, not public-clone. Source access is granted by PuenteWorks LLC — email simon@puenteworks.com and you will receive a private Forgejo remote. Evaluation and any other non-production use are free under BUSL-1.1; production use requires a commercial license — see the published rates in docs/pricing.md.

Installation

# Clone the private Forgejo remote you were granted (see "Getting the source")
git clone <your-granted-forgejo-remote> complyos
cd complyos

# Install with uv (recommended)
uv sync --all-extras --dev

# Or with pip
pip install -e ".[dev]"

CLI Usage

# Initialize profile-specific starter configs
complyos init --profile workforce
complyos init --profile campus --output campus.yaml

# Inspect profile-specific connector capability matrices
complyos connectors --profile workforce
complyos connectors --profile campus --json

# Run a compliance audit
complyos audit

# Filter by department
complyos audit --department Engineering

# Generate a structured report
complyos report --department Engineering --json

# Check a single user's status
complyos status u1

# What changed since the last audit? (new gaps, resolved gaps, trend)
complyos digest

# Generate a self-contained HTML dashboard (summary, trend, filterable table)
complyos dashboard --open

# Serve the live dashboard API and authenticated web shell locally
complyos serve-dashboard --host 127.0.0.1 --port 8000
# Then open http://127.0.0.1:8000/shell in your browser (login with your API token)

# Run configured scheduled audits once from cron/systemd/Forgejo Actions
complyos run-schedule --config complyos.yaml

# Queue and drain notification outbox events without inline network coupling
complyos notifications list --db complyos.db --json
complyos notifications preference-set --db complyos.db --channel email --event-type audit.completed --disabled --reason "quiet hours" --json
complyos notifications drain --db complyos.db --dry-run --json
complyos notifications drain --db complyos.db --send --json

# Check release-readiness artifacts
complyos release-check --json

# Collect readiness/control packets for review
complyos security evidence --period current --json
complyos governance packet --lane workforce --json

# Operate privacy/DSR and retention workflows through service gates
complyos privacy request <subject-id> --type access --json
complyos privacy approve <request-id> --note "controller approved" --json
complyos privacy export <request-id> --json
complyos privacy retention configure --raw-import-days 30 --evidence-days 2555 --action-log-days 2555 --ai-proposal-days 180 --privacy-request-days 365 --json
complyos privacy retention run --dry-run --json

# Export a self-contained HTML audit report
complyos export --output report.html

# Sync LMS data to local SQLite
complyos sync

# Validate an assignment rule before deploying
complyos validate-rule rule.json

# Preview who would be affected by a rule
complyos preview-rule rule.json

# Check connector health
complyos health

# Send reminders / manager notifications for current gaps
complyos remediate --dry-run

Notification and Hook Operations

ComplyOS now treats notifications and hooks as durable infrastructure, not inline side effects. Audit, privacy, retention, and source-intelligence workflows enqueue tenant-scoped notification_events; a separate worker drains email, slack, teams, or generic webhook deliveries.

Provider-neutral controls that are implemented now:

• durable outbox tables for events and deliveries;

• retry, skip, sent, and dead-letter delivery states;

• SMTP-backed email delivery via COMPLYOS_SMTP_* and COMPLYOS_NOTIFICATION_EMAIL_TO;

• Slack, Teams, and generic webhook delivery via COMPLYOS_SLACK_WEBHOOK_URL, COMPLYOS_TEAMS_WEBHOOK_URL, and COMPLYOS_WEBHOOK_URL;

• optional outbound HMAC signing via COMPLYOS_WEBHOOK_SECRET;

• channel/event preferences and tenant kill switches through complyos notifications preference-set and /api/v1/notifications/preferences;

• generic inbound hook receipts through POST /api/v1/hooks/inbound/{source};

• optional inbound HMAC validation via COMPLYOS_INBOUND_WEBHOOK_SECRET;

• systemd, cron, and Forgejo Action worker templates under deploy/.

Still intentionally deferred: real customer webhook URLs, real SMTP credentials, paid regulatory APIs, and provider-specific LMS/HRIS parsers.

MCP Server

# Start the MCP server
complyos mcp

Then configure your MCP client (Claude Code, Cursor, etc.) to point to the server.

Connectors

CSV Configuration

No API access needed — point ComplyOS at a directory containing your LMS export as users.csv, courses.csv, and enrollments.csv:

export COMPLYOS_CSV_DIR=./examples/csv   # try it with the bundled sample data
complyos audit

# Try profile-specific sample exports
COMPLYOS_CSV_DIR=examples/csv-workforce complyos audit
COMPLYOS_CSV_DIR=examples/csv-campus complyos audit

Common column-name variants are recognized automatically (User ID, Email Address, Learner ID, Completion Status, Deadline, ...), so exports from Canvas, Cornerstone, Moodle, Docebo, and similar systems work without reformatting. The CSV source is read-only: audits and reports work fully, but reminder remediation requires an API-backed connector.

Workday Configuration

Set environment variables:

export WORKDAY_BASE_URL="https://your-workday-instance.com"
export WORKDAY_USERNAME="your-user"
export WORKDAY_PASSWORD="your-pass"

Development

# Run tests
uv run --extra dev pytest -q

# Run with coverage
uv run --extra dev pytest --cov=complyos --cov-report=term-missing

# Lint
uv run --extra dev ruff check .

# Type check
uv run --extra dev mypy complyos

Domain Model

ComplyOS normalizes Workforce and Campus source data into one shared audit model. The cross-LMS connector contract normalizes transcripts, enrollments, assignments, submissions, completions, exemptions, and recertifications into LearningRecord. The existing Enrollment model remains for compatibility with the current audit engine.

LearningRecord(
    id="lr1",
    user_id="u1",
    course_id="c1",
    source_system="cornerstone",
    source_record_id="csod-transcript-1",
    status="completed",
    expires_at="2026-01-20",
)

ComplianceGap(
    user=User(id="u1", department="Engineering", ...),
    missing_courses=[Course(code="SEC-101", mandatory=True)],
    severity="high",  # critical | high | medium | low
    days_overdue=14,
    rule_name="Mandatory Compliance Training",
)

Every audit produces a tenant-scoped EvidenceLedgerEntry with SHA256 hashes for auditor/counsel review. Action logs record who did what without turning readiness software into a legal-status claim.

Roadmap

• Phase 1 — Core auditor, MCP server, CLI, Workday connector, tests

• Phase 2 — SQLite persistence, assignment rules engine, sync command

• Phase 3 — Remediation workflows, CSV connector, compliance digest, HTML dashboard

• Phase 4 — Operator-ready release: scheduled audit runs, notification outbox, release packaging, and documentation/security polish

• Phase 5 — Scale-out: PostgreSQL backend, live web dashboard, SAP SuccessFactors connector, Cornerstone connector

• Enterprise readiness foundation — tenant-scoped evidence, API/MCP/CLI parity for privacy workflows, retention cleanup, security evidence packet, and governance packet

• Source Intelligence hardening — DB-backed runs/proposals/schedules/job executions, review UI, export packets, migration ledger, deployment check, and external APIs kept list-only

• Notification outbox hooks — DB-backed events/deliveries/preferences, source-intel/audit/privacy event enqueue, email/webhook drain, signed outbound and inbound hook payloads, worker templates, and no-secret logs

• Enterprise control-plane — service boundary with ActorContext + 37-permission catalog + require_permission choke-point across all services; API v1 (FastAPI) with bearer-token auth, structured errors, rate limiting, admin/roles routes, and OpenAPI snapshot test; CLI/MCP/API v1 surface parity enforced by adversarial tests (BOLA/IDOR, secrets audit, cross-surface denial, export formula/XSS neutralization); authenticated web shell at /shell with ten live modules (Overview, Gaps, Imports, Records, Evidence, Remediation, Source intelligence, Privacy & retention, Readiness, Administration) and WCAG 2.2 AA enforcement; proposal-only AI layer with PII redaction, reject/expiry lifecycle, and provenance hashes.

Remaining work is mostly outside application code: real webhook URLs/SMTP credentials, paid regulatory APIs, provider-specific LMS/HRIS event parsers, counsel-approved terms, customer-specific retention schedules, production security receipts, backup/restore evidence, access-review evidence, accessibility audit/VPAT where needed, and auditor review.

License

ComplyOS uses Business Source License 1.1, SPDX identifier BUSL-1.1. Avoid the shorthand "BSL" here: BSL-1.0 usually means the unrelated Boost Software License.

This is a source-available license. The source code is visible and may be copied, modified, redistributed, and used for non-production purposes. Production use requires a commercial license unless a future Additional Use Grant says otherwise.

On 2030-06-11, or the fourth anniversary of the first public distribution of a specific version under this license, whichever comes first, that version converts to Apache License 2.0.

The licensor is PuenteWorks LLC (California). Production use is licensed under the Commercial License Agreement (draft, pending counsel review) at the published rates in docs/pricing.md. Licensing contact: simon@puenteworks.com.

What is ComplyOS?

ComplyOS is a compliance operating system / compliance workflow tooling that helps operators and builders running compliance workflows structure compliance work with an OS-like tool surface.

Who it's for

• Primary: operators and builders running compliance workflows

• Use when you need to structure compliance work with an OS-like tool surface

• Skip if you need a certification body

FAQ

What is ComplyOS?

ComplyOS is a compliance operating system / compliance workflow tooling. It helps operators and builders running compliance workflows structure compliance work with an OS-like tool surface.

Who should use ComplyOS?

operators and builders running compliance workflows.

How is ComplyOS different?

Tooling to operate compliance work — not a certifier.

Is ComplyOS production software?

Treat the README status and release tags as source of truth for maturity. Validate against your own requirements before production use.

Status

• Maintained as of 2026 on the default branch

• Prefer release tags when pinning dependencies

• Report issues on the canonical remote listed above

Agent surface

• Coding agents: read this README first, then repo docs/AGENTS.md if present

• Prefer machine-readable briefs (llms.txt) when the repo ships one

• MCP or skill entrypoints are documented in-repo when applicable

Contributing

Issues and PRs welcome on the canonical remote. Keep public docs free of secrets and machine-local paths.

License

See LICENSE in this repository (or package metadata if license is package-only).