SureCentric Platform Roadmap
This roadmap reflects the desired direction as of April 2026. Timelines are estimates. Priorities may shift as engineering work progresses.
Current State (April 2026)
The SureCentric Platform currently runs as four separate Docker Compose stacks with five PostgreSQL databases:
nuxeo-webui-2025-local surenet surecentric sc (legacy)
───────────────────────── ────────────── ─────────────── ──────────────────
nuxeo-sc-2025:local network-service superset_app nuxeo-application
nuxeo-webui-apisix-local network-database superset_db nuxeo-database
nuxeo-web-ui:3.1.29-local network-es superset_cache
nuxeo-webui-db-2025 (PG 16) ← ← PG 15 ← ← PG 17 ← ← PG (legacy) ←
nuxeo-webui-logto card-api
nuxeo-webui-logto-postgres duckdb
nuxeo-webui-cloudflared
The SureCentric Client (SureNetwork Global UI, Angular 16) rides across all four stacks as the unified browser / Electron shell.
Goal State
SureCentric Platform (single Docker Compose)
────────────────────────────────── ──────────
nuxeo-app (Nuxeo 2025 + SC extensions)
network-service (SureNetwork)
nuxeo-web-ui
apisix
logto
superset
card-api
duckdb
elasticsearch
Databases: 2 PostgreSQL instances
├── platform-db (Nuxeo 2025 + SC data)
└── network-db OR merged into platform-db
Roadmap 1: SC Nuxeo 5.6 → Nuxeo LTS 2025
This is the primary engineering migration. The SC legacy Nuxeo 5.6 stack is retired in favor of Nuxeo LTS 2025.
Phase 0 — Current (parallel stacks)
scstack (Nuxeo 5.6) is the production-equivalent local environmentnuxeo-webui-2025-localstack (Nuxeo 2025) is the development target- Both stacks have separate databases; this is intentional during the migration
- SureDrive (AngularJS) connects to Nuxeo 5.6; Nuxeo 2025 runs without SC extensions
Phase 1 — Port Tier 1 SC extensions
Port these modules from Nuxeo 5.6 APIs to Nuxeo 2025:
| Module | Role |
|---|---|
suredms-nuxeo-mobile-api | Automation API surface (491 operations) |
suredms-nuxeo-doctypes | SC document types and SureNetwork repositories |
suredms-nuxeo-security | Authentication, permissions |
suredms-nuxeo-management | Runtime admin and property behavior |
suredms-nuxeo-project | Project and study logic |
suredms-nuxeo-database | DB schema and persistence |
suredms-nuxeo-deployment-profile | Runtime deployment patching |
Go/no-go gate: Can the minimum login-related modules compile and package against Nuxeo 2025?
Phase 2 — SureDrive wired to Nuxeo 2025
- SureDrive (AngularJS) iframe connects to the Nuxeo 2025 backend instead of the 5.6 stack
- Minimum Automation operations validated:
Mobile.GetSystemSnapshot,Mobile.GetServerProperties,Mobile.GetStudies,Mobile.GetDocuments - SureDrive iframe still served; no UI changes to the AngularJS app
Go/no-go gate: Can a user log into SureDrive on localhost against Nuxeo 2025 and browse a study?
Phase 3 — Full navigator path on Nuxeo 2025
- Complete read-only document navigator path validated
- All 13 minimum read-oriented operations working
- Old SureDMS AngularJS document navigator fully usable against Nuxeo 2025
- Seed data / license initialization working repeatably
Go/no-go gate: Can a developer start from scratch, run the stack, and have a fully navigable study on Nuxeo 2025?
Phase 4 — SC legacy retired
scstack (Nuxeo 5.6) is shut down permanently- Nuxeo 2025 is the only Nuxeo
- SC legacy database absorbed into the Nuxeo 2025 database
- Tier 2 extension modules ported as needed for broader product parity
Go/no-go gate: Is there zero production dependency on any Nuxeo 5.6 component?
Phase 5 — SureArchive replaces SureDrive
- SureArchive (Angular 16 inside SureNetwork Global UI) has reached feature parity with SureDrive
- SureDrive iframe card on Project Desktop is retired
- All document navigation runs natively in Angular 16 — no AngularJS dependency remains
Roadmap 2: SureDrive → SureArchive (AngularJS → Angular 16)
This roadmap tracks the progressive replacement of the legacy SureDMS AngularJS navigator with the modern Angular 16 SureArchive module.
| Milestone | Deliverable |
|---|---|
| M1 | SureArchive module scaffolded in SureNetwork Global UI; empty route on Project Desktop |
| M2 | Basic study list ported from AngularJS to Angular 16 |
| M3 | Folder browser ported |
| M4 | Document viewer ported (read-only) |
| M5 | Document details, history, attachments ported |
| M6 | Write operations ported (upload, check in/out, lock) |
| M7 | SureDrive card removed; SureArchive is the sole document navigator |
Until M7, both SureDrive and SureArchive cards coexist on Project Desktop.
Roadmap 3: Database Consolidation
Current state: 5 PostgreSQL databases
| Database | Stack | Engine |
|---|---|---|
| Nuxeo 2025 DB | nuxeo-webui-2025-local | PostgreSQL 16 |
| Logto DB | nuxeo-webui-2025-local | PostgreSQL 17-alpine |
| SureNetwork DB | surenet | PostgreSQL 15-alpine |
| Superset DB | surecentric | PostgreSQL 17 |
| SC Legacy DB | sc | PostgreSQL (internal) |
Target state: ≤ 2 PostgreSQL databases
| Phase | Action | Result |
|---|---|---|
| Phase A | SC legacy DB absorbed into Nuxeo 2025 DB (after Phase 4 of Roadmap 1) | 4 databases |
| Phase B | Logto DB externalized to managed identity service or consolidated | 3 databases |
| Phase C | Superset DB merged into shared platform DB or replaced by embedded metadata | 2 databases |
| Phase D | SureNetwork DB consolidated or merged into platform DB | 1–2 databases |
The SureNetwork DB may remain separate if its schema and access patterns are sufficiently different. The architectural goal is no more than 2 PostgreSQL instances running in a standard platform deployment.
Roadmap 4: Docker Unification
Current state: 4 separate Docker Compose stacks
Target state: 1 unified SureCentric Platform Docker Compose
# surecentric-platform/docker-compose.yml (target)
services:
nuxeo-app: { image: nuxeo-sc-2025:latest }
nuxeo-db: { image: postgres:16 }
apisix: { image: apache/apisix:3.11.0-debian }
logto: { image: svhd/logto:latest }
logto-db: { image: postgres:17-alpine }
nuxeo-web-ui: { image: nuxeo-web-ui:3.1.29 }
network-service: { image: sn-nuxeo-lts:latest }
network-db: { image: postgres:15-alpine }
network-es: { image: elasticsearch/elasticsearch:... }
superset: { image: apache/superset:4.0.0 }
superset-db: { image: postgres:17 }
superset-cache: { image: redis:7 }
card-api: { image: node:20-alpine }
duckdb: { image: datacatering/duckdb:v1.2.1 }
Sequencing: Docker unification should happen after SC legacy stack retirement (Roadmap 1, Phase 4). Combining stacks while the legacy stack is still needed adds compose complexity with no benefit.
Developer benefit: After unification, a single docker compose up starts the entire SureCentric Platform for local development.
Roadmap Summary
| Roadmap | Goal | Key Gate |
|---|---|---|
| 1: Nuxeo 5.6 → 2025 | Retire SC legacy Nuxeo | SureDrive works against Nuxeo 2025 |
| 2: SureDrive → SureArchive | Retire AngularJS navigator | Angular 16 doc navigator reaches feature parity |
| 3: DB Consolidation | ≤ 2 PostgreSQL databases | SC legacy DB absorbed after Roadmap 1 Phase 4 |
| 4: Docker Unification | 1 platform compose | After SC legacy stack retired |
These roadmaps are sequential in their dependencies but can progress in parallel where independent. Roadmap 2 (SureArchive) can proceed independently of Roadmap 1 — the Angular 16 porting work does not require the Nuxeo 5.6 migration to complete first.