Private administrator previewManagement foundations are available. Windows imaging is in development.
Collective

Collective deployment operationsEarly development

One console.
Every deployment site.

Manage tenant content, fixed deployment profiles, and local appliances from one place. Keep the working files close to each site.

Explore the platform Administrator sign in

The management console is in private preview. Physical PXE, WinPE, and Windows imaging are not active yet.

Illustrative configurationapp.getcollective.cloud
Example tenant / DallasConfiguration
Dallas deployment profileReady to sync
01

Windows 11 ProManually supplied ISO

Selected
02

Driver packsSite-specific content

Selected
03

ApplicationsApproved packages

Selected
04

PowerShellTemporary deployment scripts

Selected
Site appliance onlineConfiguration current

Ubuntu site applianceConfig + verified content cache

Local
01

Tenant-aware from day oneIsolated private content and site scope.

02

Outbound site connectionNo inbound appliance management port.

03

Local operational memoryLast synchronized configuration and content cache.

01 / Platform

Control centrally.
Prepare locally.

Collective separates the coordination layer from the work that must stay close to each site. The console defines intent; the Ubuntu appliance keeps an authenticated local copy.

Available in preview

A consistent foundation for every site.

The current release manages the records, content, configuration, and site connection needed before physical imaging begins.

  1. 01

    Tenant and site structure

    Keep tenant records separate and organize each organization’s physical sites.

    Available
  2. 02

    Fixed deployment profiles

    Pin Windows 11 Pro media, drivers, applications, and scripts to a predictable stage order.

    Available
  3. 03

    Private and shared content

    Upload ISO, driver, application, and PowerShell artifacts with recorded size and SHA-256 integrity.

    Available
  4. 04

    Site-bound enrollment

    Issue short-lived, one-time keys that exchange for separate appliance credentials.

    Available
  5. 05

    Outbound appliance operations

    Synchronize configuration and cache, report events, and retrieve bounded redacted logs on request.

    Available

02 / Architecture

Cloud coordination.
Site resilience.

The appliance initiates the connection, verifies assigned artifacts, and retains the last complete synchronization. A SaaS interruption does not erase the local foundation.

Operational todayConsole, outbound agent, cache, events, and logs.

Planned nextPhysical endpoint execution through an isolated site network.

03 / Roadmap

Built in deliberate
operational layers.

Each stage earns the next. The roadmap separates what an administrator can use now from the endpoint work still under development.

Available nowFoundation

Control and site management

  • Tenant and site administration
  • Manual content upload and integrity metadata
  • Fixed Windows 11 Pro profiles
  • One-time site enrollment
  • Config/cache sync, events, and on-demand logs
NextExecution

Isolated imaging workflow

  • Physical PXE and custom WinPE bootstrap
  • Windows 11 Pro apply and reboot continuation
  • Application installation and quality checks
  • Secure Boot validation
LaterAutomation

Broader lifecycle tools

  • Vendor driver acquisition
  • Microsoft Entra SSO and Autopilot integration
  • Factory capture and restore
  • Expanded deployment automation

Roadmap items describe direction, not committed release dates.

04 / FAQ

Clear boundaries
by design.

Collective is in early development. These answers describe the preview as it operates today.

Can Collective deploy Windows to physical devices today?

Not yet. The administration, content, profile, appliance, caching, event, and log foundations are available. Physical PXE, WinPE execution, disk imaging, and reboot continuation are the next development milestone.

What continues working if the SaaS is unavailable?

The Ubuntu appliance retains its last completely synchronized configuration and verified artifact cache. It queues supported events locally for later delivery. Offline endpoint imaging will arrive with the future imaging executor.

How is tenant content isolated?

Private catalogs, profiles, sites, appliances, events, and logs are scoped to a tenant. Content becomes cross-tenant only when a platform administrator explicitly places it in a shared catalog.

Does Collective install a permanent agent on Windows endpoints?

No. The persistent management agent runs on the Ubuntu site appliance. Future Windows execution is designed around temporary WinPE and Windows PowerShell stages during deployment.

How do site appliances connect?

The administrator creates a short-lived, site-bound enrollment key. After one-time enrollment, the appliance uses its own credential and initiates outbound HTTPS requests.

Is there public signup or Microsoft sign-in?

No. The current release is a private administrator preview. Public signup is unavailable. Tenant-user access, Microsoft Entra SSO, and Autopilot integration are planned for later work.

Private administrator preview

The site foundation is ready.
The imaging layer comes next.

Administrator sign in