NOBA is live in beta. Core migration flows have been validated across two real remote locations over WAN/ISP links using four Proxmox hosts, four AD environments, and an Azure dev tenant; the next phase is broader customer-scale validation.
The best fit is a team willing to evaluate NOBA against larger real operational workflows, not just a polished demo dataset.
Hybrid AD / Entra, Samba or LDAP edge cases, M&A domain merges, cross-domain reconciliation, LAPS/BitLocker coverage, and compliance-evidence expectations.
Remote agents, service control, endpoint monitoring, self-healing trust levels, approval gates, maintenance windows, and incident-response workflows.
SAML/OIDC, SCIM, WebAuthn, RBAC, audit trails, retention, SIEM/OTel export, vault controls, backups, updater posture, and procurement questions.
The command center, enterprise identity surfaces, agents, audit/evidence flows, AD project workflows, downloads/updater path, and interactive demos are exposed for technical evaluation.
Larger scale, messy directory topology, real firewall/DNS constraints, migration edge cases, operator workflows, compliance-evidence expectations, and go-live expectations. See what has already been exercised in the validation topology.
Start with the mock-data demo, then reproduce the flow in your own lab, then use dry-run workflows and explicit rollback plans before any production cutover.
AD integration has been exercised against real Samba AD, Windows Server 2025 AD, and Azure AD / Entra ID surfaces across a 2-site, 4-Proxmox-host topology. Current evidence supports workflow path coverage; larger-volume validation depends on customer or design-partner infrastructure.
LDAP-to-LDAP, Azure-to-LDAP, LDAP-to-Azure, sync, migration, acquisition, reconciliation, pre-flight, and authentication verification paths have evidence in the AD PoC.
Server 2025 LDAPS, Windows LAPS, PSOs, nested groups, tombstones, AdminCount/AdminSDHolder, service-account SPNs, and Azure eventual consistency were exercised or explicitly bounded.
This is real-system validation at small load, including 100-user throughput runs on the SQLite-backed beta profile while the 4-host lab also carried cross-site AD testing. PostgreSQL and Redis-backed caching are available for heavier deployments, but multi-thousand-user evidence still needs customer-scale infrastructure.
The latest enterprise changelog entries show two things happening in parallel: the remaining honesty gaps are being closed explicitly, and the integration surface is being wired through to real implementations and live-test coverage instead of placeholder success states.
The latest releases closed concrete honesty gaps: Trust Center and health scoring now treat missing or failed evidence as unknown instead of green, workflow runs return a real run_id, SIEM forwarding re-enqueues failed batches with durability counters, backup metadata reports real PostgreSQL/MySQL values, and WebAuthn plus SAML validation paths were hardened.
The integration surface is no longer mostly aspirational wiring. The changelog now records a live test harness for real instances, execute-op retrofits for older modules, and full implementations replacing the last placeholder modules across security, surveillance, file-sync, NAS, hypervisor, and identity categories. Live testing is now actively finding and fixing real bugs that mocks did not catch.
The changelog still calls out bounded gaps where evidence is not there yet: some platforms remain explicitly UNVERIFIED or unsupported, and the public beta copy stays limited to what the current app, live tests, and documented evidence can actually support.
Walk the cross-domain flow with mock data before connecting real directories.
Review deployment boundaries, agent data flow, security model, and release infrastructure.
Understand the real remote lab coverage before planning your own customer-scale validation.
Install the beta build in a controlled environment and compare it against your own topology and constraints.
You're on the list.