Project · Progress

Progress

The roadmap and where the work stands, read automatically from the project’s source repository: each phase, each item’s status and the evidence behind it, the first-demo acceptance tests and the latest commits.

Project status Read from GitHub on the server, at most ten minutes after the repository changes: a page view that finds the copy older than that fetches a new one. Times are in UTC. Pre-alpha: nothing here is released or production ready.

Current phase
Phase 1 · Control server foundation and core platform proof
Stage
Pre-alpha (lab)
First-demo acceptance tests
22 of 24 passing in the lab
Latest release
None yet
Source
Roadmap in the repositoryRoadmap last changed Last read from GitHub

“Core platform components are integrated and tested in an isolated lab: own source build of Exchange-compatible groupware with single sign-on webmail, Keycloak SSO, file sync and browser document editing, backup/restore drills, chat and video meetings, and an infrastructure control server with monitoring, self-healing and a real Proxmox integration (VM lifecycle verified on a live cluster). Guided deployment wizards, provisioning automation and the credential vault are being integrated.” From the repository’s roadmap.

Roadmap

The phases in order, with each one’s status and how many of its items are integrated or tested in the lab. Select a phase for its items and evidence. More about the roadmap

Roadmap flow chart Product phases in order: Phase 0 Discovery (Tested in lab); Phase 1 Core platform proof (Current phase); Phase 2 Orchestration (In development); Phase 3 First user experience (In development); Phase 4 MSP and administration (Planned); Phase 5 Operational maturity (Planned); Phase 6 Collaboration (In development); Phase 7 Migration Center (In development); Phase 8 MSP pilot (Planned). PRODUCT PHASES PHASE 0DiscoveryTested in lab · 2/3 in labPhase 0: Discovery, Tested in lab, 2 of 3 items integrated or tested in the lab PHASE 1NOWCore platform proofCurrent phase · 10/11 in labPhase 1: Core platform proof, Current phase, 10 of 11 items integrated or tested in the lab PHASE 2OrchestrationIn development · 3/6 in labPhase 2: Orchestration, In development, 3 of 6 items integrated or tested in the lab PHASE 3First user experienceIn development · 2/3 in labPhase 3: First user experience, In development, 2 of 3 items integrated or tested in the lab PHASE 4MSP and administrationPlanned · 0/3 in labPhase 4: MSP and administration, Planned, 0 of 3 items integrated or tested in the lab PHASE 5Operational maturityPlanned · 1/3 in labPhase 5: Operational maturity, Planned, 1 of 3 items integrated or tested in the lab PHASE 6CollaborationIn development · 3/3 in labPhase 6: Collaboration, In development, 3 of 3 items integrated or tested in the lab PHASE 7Migration CenterIn development · 1/2 in labPhase 7: Migration Center, In development, 1 of 2 items integrated or tested in the lab PHASE 8MSP pilotPlanned · 0/1 in labPhase 8: MSP pilot, Planned, 0 of 1 items integrated or tested in the lab
Tested in lab or complete Current phase In development Planned Bar: share of items integrated or tested in the lab, amber in development Select a phase for its details.
  1. Phase 0

    Discovery and architecture

    Tested in lab

    Architecture decisions, and source-level licensing evaluation of every component before it is adopted, so the zero-cost, no-limits policy holds in what ships.

    2 of 3 items integrated or tested in the lab · 1 in development

    Items (3)
  2. Phase 1

    Control server foundation and core platform proof

    Current phase

    The control server first, then proof that the core services run together on one identity, from the project’s own builds where a vendor’s package is restricted. Lab work on isolated containers, each result recorded with evidence.

    10 of 11 items integrated or tested in the lab

    Items (11)
    • ICS: operator auth with MFA, encrypted vault, tamper-evident audit, approvals, durable jobs Evidence: security-review-ics-2026-11-15.md Tested in lab
    • ICS: service-level monitoring, incidents, alerts, signed node agents, bounded auto-remediation Evidence: ics-monitoring-results.md, security-review-ics-monitoring-2026-11-15.md Integrated in lab
    • Groupware: own source build of Gromox stack (MAPI/HTTP, EWS, ActiveSync, Autodiscover, IMAP/SMTP, CalDAV/CardDAV, webmail), no user cap Evidence: groupware-lab-results.md Integrated in lab
    • Single user directory: OpenLDAP authoritative for Keycloak SSO, files and groupware Evidence: identity-files-lab-results.md, groupware-ldap-results.md Integrated in lab
    • Files: OpenCloud with WebDAV, versions, desktop sync engine (offline, conflicts) Evidence: identity-files-lab-results.md Integrated in lab
    • Documents: browser editing via WOPI with verified save/reopen and restart persistence (Lab uses vendor CODE packages for functional tests only) Evidence: identity-files-lab-results.md Integrated in lab
    • Documents: own unlimited, rebranded Collabora Online source build (Own source build, rebranded, no connection/document caps: 30 concurrent documents and 60 sessions verified; edit/save via WOPI verified) Evidence: docengine-build-results.md Integrated in lab
    • User lifecycle: provision and deprovision across all services with measured revocation (Open gaps: OpenCloud app-token revocation, ActiveSync remote wipe, per-user IMAP session termination) Evidence: user-lifecycle-results.md Integrated in lab
    • Backup and restore drills to separate machines (files, identity, ICS controller) Evidence: restore-drill-results.md, ics-recovery.md Integrated in lab
    • Groupware restore to a separate machine and clean-room rebuild (Online logical backup; point-in-time consistency across mailboxes needs snapshots) Evidence: restore-drill-results.md Integrated in lab
    • Real Outlook, Thunderbird and mobile client compatibility matrix Evidence: MANUAL-CHECKLIST.md Planned
  3. Phase 2

    Infrastructure orchestration and repeatable deployment

    In development

    Repeatable deployment: a Proxmox VE provider, a deployment engine with sizing, plans and drift detection, signed images and the build and release pipeline for the project’s own distributions.

    3 of 6 items integrated or tested in the lab · 2 in development

    Items (6)
    • Provider adapter with Proxmox VE as first provider (discovery, metrics, scoped VM lifecycle) (Real PVE 9.2 cluster: scope refusals, clone, tag, configure, resize, start, snapshot, stop, destroy verified) Evidence: provider-proxmox-real.md, provider-proxmox.md Integrated in lab
    • Deployment engine: profiles, sizing, dependency graph, plans, desired vs actual state, drift Evidence: deployment-engine.md In development
    • Guest bootstrap: cloud-init, rootless Podman, signed digest-pinned images, agent enrollment (Tested in lab containers; real VM boot pending) Evidence: guest-bootstrap-results.md Integrated in lab
    • Setup, deployment and change wizards backed by approval-gated plans (Setup/deployment/change wizards deployed as the default first-run path; end-to-end deployment run in progress) Integrated in lab
    • Build and release pipeline for own distributions (signed packages/images, SBOM, staged channels) Evidence: 0008-build-release-pipeline.md Planned
    • Continuous integration (tests, secret scanning, license checks) Evidence: workflows In development
  4. Phase 3

    First working user experience

    In development

    The point at which it looks like one product: the redesigned infrastructure console, a unified user portal with single sign-on, and guided desktop and mobile onboarding.

    2 of 3 items integrated or tested in the lab

    Items (3)
    • Redesigned infrastructure console (dashboard, infrastructure views, operations, monitoring) (Redesigned console deployed; infrastructure views await Proxmox provider integration) Evidence: screenshots Integrated in lab
    • Unified user portal (mail, calendar, contacts, files, documents) with SSO (SSO launcher, recent files, new documents; webmail single sign-on proven on a lab node) Evidence: portal-results.md Integrated in lab
    • Guided desktop and mobile onboarding Planned
  5. Phase 4

    MSP and organization administration

    Planned

    Isolated customer stacks proven against each other, the organization admin center and MSP Control Center, and a versioned provisioning API.

    0 of 3 items integrated or tested in the lab

    Items (3)
    • Two isolated customer stacks with cross-customer access-denial tests Planned
    • Organization admin and MSP Control Center Planned
    • Versioned MSP provisioning API Planned
  6. Phase 5

    Operational maturity

    Planned

    Running it over time: patch rings, controlled upgrades and rollback, capacity analytics, and encrypted off-host backups with measured recovery points and times.

    1 of 3 items integrated or tested in the lab · 1 in development

    Items (3)
    • Patch rings, controlled upgrades and rollback (Signed pinned-package upgrade + rollback demonstrated on the lab mail server; merge pending) In development
    • Capacity analytics and scaling plans Planned
    • Encrypted off-host backups with measured RPO/RTO (Encrypted append-only backups as ICS jobs with verified restores (RTO 29-127 s in lab)) Evidence: backup-product-results.md Integrated in lab
  7. Phase 6

    Chat, meetings and telephony

    In development

    Chat, meetings and telephony joined to the same identity. A desk evaluation so far; nothing is installed.

    3 of 3 items integrated or tested in the lab

    Items (3)
    • Zero-cost collaboration stack evaluation (Matrix, Jitsi/LiveKit, Asterisk) Evidence: collaboration-eval.md Tested in lab
    • Chat (Synapse + MAS + Element) and meetings (Jitsi with SSO-issued tokens) Evidence: collaboration-lab-results.md Integrated in lab
    • Business telephony (Asterisk + browser softphone) (WebRTC + native SIP calls, voicemail to email, LDAP extensions, deprovisioning 0.6 s; no PSTN/E911 yet) Evidence: telephony-lab-results.md Integrated in lab
  8. Phase 7

    Migration Center (Microsoft 365, Google Workspace)

    In development

    A read-only readiness assessment of a Microsoft 365 or Google Workspace tenant before anything moves, then the engine that moves mail, calendars, contacts and files.

    1 of 2 items integrated or tested in the lab · 1 in development

    Items (2)
    • Read-only migration readiness assessment (Implemented and tested against API-shaped fixtures; awaiting a real tenant) Evidence: migration-assessment.md In development
    • Mail, calendar, contacts and file migration engine (IMAP to groupware mail migration verified in lab (incremental, resumable); merge pending) Integrated in lab
  9. Phase 8

    MSP pilot and production hardening

    Planned

    Hardening for real use with an MSP pilot: deliverability, performance and security testing, and support documentation.

    0 of 1 items integrated or tested in the lab

    Items (1)
    • Deliverability, performance, security testing and support documentation Planned

Infrastructure operations track

First-demo acceptance tests

What the first working demonstration has to show, test by test. A test counts here only when the repository records it as integrated or tested in the lab.

22 of 24 passing in the lab

  1. A1ICS deploys the required components into approved lab infrastructure (ICS deployed a VM + signed container on real Proxmox end to end (lab-only bootstrap; production no-SSH bootstrap pending owner storage prerequisite))Integrated in lab
  2. A2Services reachable through correctly configured TLS endpoints (Lab CA)Integrated in lab
  3. A3Keycloak login and user provisioningIntegrated in lab
  4. A4User can enter the Office Unbound portal (Portal with Keycloak SSO in lab)Integrated in lab
  5. A5User can access mailIntegrated in lab
  6. A6Send and receive real test messages (Within the lab; external deliverability not yet tested)Integrated in lab
  7. A7Calendar events created and synchronizedIntegrated in lab
  8. A8Contacts created and synchronizedIntegrated in lab
  9. A9Create a documentIntegrated in lab
  10. A10Edit and save a documentIntegrated in lab
  11. A11Content correct after close and reopenIntegrated in lab
  12. A12Content survives service restartIntegrated in lab
  13. A13Desktop sync upload/download and offline work (Sync engine tested headless; GUI client not yet)Integrated in lab
  14. A14Groupware protocol tests report actual client compatibility (Protocol level done; real clients pending)In development
  15. A15ICS detects a simulated service failureIntegrated in lab
  16. A16Approved recovery action succeedsIntegrated in lab
  17. A17Backup restored to a separate test machine (Files, identity, groupware and ICS controller tiers restored to separate machines)Integrated in lab
  18. A18Tests identify unsupported functionality instead of concealing itIntegrated in lab
  19. A19User deprovisioning removes effective access (App tokens, IMAP sessions, ActiveSync wipe, Matrix and phone access all revoked in lab)Integrated in lab
  20. A20Two isolated customer deployments pass access-denial tests (Two independent customer stacks: 153/155 isolation checks; per-customer network isolation needs VLAN/SDN in production; backup key boundary being re-tested)Integrated in lab
  21. A21Pinned upgrades and recovery demonstrated (Pinned signed-package upgrade and rollback demonstrated (merge pending))Integrated in lab
  22. A22Installer can repeat the installation (All lab tiers install in one pass on fresh machines and re-run idempotently; ICS installer on Ubuntu 24.04 and Debian 12)Integrated in lab
  23. A23Monitoring and audit history survive restarts (Audit chain verified after controller restore)Integrated in lab
  24. A24Administrator documentation describes real proceduresIn development

Component status

From the repository’s status record. Each status moves only with recorded evidence: test output, the commit and the environment it ran in. “In lab” means an isolated test environment, not a deployment anyone uses.

Component status, with the evidence for each
ComponentStatusEvidence
ICS backend (auth/TOTP, vault, HMAC hash-chained audit, typed actions, 2-approver plans, jobs, PVE read-only client) Testedunit/integration; 329 tests on main as of 2026-11-15 19:05 UTC security-review-ics-2026-11-15.md incl. remediation; service ics on 127.0.0.1:8088
ICS console (Vue, redesigned shell/dashboard/users) Integrated in lab— deployed 2026-11-15 vitest 32/32, typecheck, build; screenshots docs/screenshots/
ICS monitoring, alerts, node agent, remediation Integrated in lab ics-monitoring-results.md; review fixes H1, H2, M1–M4, Lows merged
ICS identity lifecycle (create / update_groups / disable+VERIFY / enable / delete / reconcile) Integrated in lab user-lifecycle-results.md: acceptance script PASS (all paths refused <= 7 s), pytest suite; open gaps: OpenCloud app tokens resurrect on enable, ActiveSync wipe, Gromox open-session kill is a quarantine workaround
Proxmox pve06 (real) Read-only probe verified; provider broker + mutations implemented vs simulator, integration in progress provider-proxmox-real.md, provider-proxmox.md
Groupware: own source build of gromox 3.13 + sync/dav/web Integrated in lab groupware-lab-results.md — 57 automated checks pass (lead re-run): MAPI/HTTP Connect, EWS, ActiveSync, Autodiscover, IMAP/SMTP, CalDAV/CardDAV, shared mailbox, restart, export/import restore; 7 users (no cap)
Groupware ↔ OpenLDAP single user store Implementing groupware-ldap-results.md (pending)
Identity: OpenLDAP + Keycloak 26.8.2 Integrated in lab identity-files-lab-results.md (T01 36/0)
Files: OpenCloud 9.1.0 Integrated in lab T02 11/0 incl. restart, T05 versions 9/0
Documents: Collabora via WOPI Integrated in labwith vendor CODE (lab-only) T03 28/0 standalone, T04 13/0 (real edit → PutFile → content verified). KI-1 below
Collabora own source build (unlimited, rebranded) Implementing docengine-build-results.md (pending)
Desktop sync engine (opencloudcmd 4.0): upload/download/offline/conflict/delete Integrated in lab T07 11/0
Backup → restore to separate machine: files tier Tested in lab restore-drill-results.md: 18 s restore, content + version history byte-identical
Backup → restore to separate machine: identity tier Tested in lab online backup; 79 s restore; logins via restored KC+LDAP, DB-only canary, identical realm keys + entryUUIDs
GUI desktop client, mobile, real Outlook clients Plannedmanual blueprints/lab/tests/MANUAL-CHECKLIST.md
Build/release pipeline Implementingdesign ADR-0008; first recipe = Collabora None recorded yet
MSP center, migration, chat/meetings Planned None recorded yet

Known limitations

  • New Outlook for Windows and Outlook mobile cannot use MAPI/EWS against non-Microsoft servers (Microsoft limitation); IMAP/SMTP only
  • Lab currently runs in isolated containers on a single host; production topology is full VMs on Proxmox
  • No production releases exist yet

Known issues

  • KI-1 (diagnosed): ~5 s window after OpenCloud restart before the editor app re-registers; tests now wait on /app/list; ICS check must use it. No data loss.
  • KI-2: LDAP lock alone does not end Keycloak SSO/offline refresh tokens (>420 s). Deprovisioning must revoke in Keycloak (<1 s measured).
  • KI-3: Collabora CODE in nspawn runs without chroot jails (unshare fails in unprivileged container) — lab-only acceptable; production VM must have jails.
  • Lab install scripts were fixed incrementally; clean-room re-runs pending.

Next tasks

  • Integrate monitoring/remediation demo (acceptance 15–16), Collabora own build, Gromox↔LDAP.
  • ~~ICS provisioning action: one user lifecycle~~ done (user-lifecycle-results.md); next: OpenCloud app-token revoke path, ActiveSync wipe, mailbox purge/export action, clean-room re-run.
  • Restore drill for groupware tier to separate machine; clean-room reinstall (22).
  • Fix monitoring security review findings (security-review-ics-monitoring-2026-11-15.md: H1 agent idle-connection DoS, H2 approval mode ineffective, M1–M5) once user-lifecycle work lands.
  • Rebranding patch queues + package recipes for gromox stack (ADR-0008).

How progress is tracked

So the numbers mean the same thing every time.

Roadmap and items
Read from docs/progress.json in the repository, the same file its ROADMAP.md is generated from. A status there moves forward only with evidence in the repository, and this page follows within minutes.
Current phase
The first phase not yet finished. It moves on by itself when the repository marks a phase done, here and in the site header.
Component status
Read from docs/status/STATUS.md, the developers’ status record, with the evidence for each entry.
Statuses
The repository’s scale: Planned, Researching, Implementing, Integrated in lab, Tested, Alpha, Beta, Production supported, and Blocked. “Integrated in lab” means demonstrated in an isolated lab; nothing is Alpha or later until there is a release.

Counts measure items and tests, not effort or quality, and say nothing about dates. Decisions and the reasons for them are written up in project updates.

Share