Ecosystem
From one product to one operating ecosystem.
MANPRA scales from one module to a connected operating model across modules, services, and partner delivery.
Ecosystem structure
One MANPRA ecosystem, multiple believable entry points
Public discovery, command-center operations, and managed delivery now follow one route map so the platform feels unified instead of stitched together.
Workforce
Standalone: Attendance, shifts, approvals, and payroll-ready workflows can run as a focused people-operations product.
Connected: When connected to MANPRA, workforce identity and presence feed the timeline, access trust, and command-center decisions.
Operator surface: Attendance desk, reports, and employee timelineAdmin surface: Billing, onboarding, module policy, export governanceSurveillance
Standalone: Camera operations, playback, health, and incident review can run as a dedicated monitoring product.
Connected: Inside MANPRA, surveillance events enrich identity, access review, and the unified command timeline.
Operator surface: Surveillance desk, devices, alerts, and playbackAdmin surface: Retention policy, deployment controls, device lifecycleAccess
Standalone: Doors, readers, badges, and policy zones can be deployed as a focused secure-entry product.
Connected: Inside MANPRA, access decisions share identity, camera context, and audit history with the same event layer.
Operator surface: Entry decisions, exception queue, access reviewAdmin surface: Policy zones, device ownership, role-aware governanceNetworkSearch
Standalone: Search, findings, and infrastructure risk context can run as a dedicated operational intelligence product.
Connected: Inside MANPRA, NetworkSearch correlates device, workforce, surveillance, and access signals into one remediation view.
Operator surface: Findings board, search console, remediation contextAdmin surface: Risk posture, export governance, escalation mappingPublic product site
CustomerThe public website explains each product both as a standalone module and as part of one MANPRA operating system.
DiscoveryCommand Center
OperatorThe authenticated app shell is the connected operating surface where events, devices, attendance, and actions come together.
OperationsBilling and workspace admin
AdminCommercial state, onboarding, plan scope, and module entitlement stay part of the same product story rather than a separate tool.
CommercialManaged operations
MSPMSP and client portfolio surfaces sit above the same module family so partners can manage many tenants without a second product line.
Managed ServicesStart with the product family
DiscoverPublic pages explain each module on its own while keeping the connected platform story visible from the first click.
Customer surfaceChoose the commercial path
ScopeTeams can buy a standalone module, a connected platform, or a managed delivery lane without changing the operating model.
Admin surfaceRun one command surface
OperateThe authenticated app keeps timeline, attendance, surveillance, access, and devices inside one command system.
Operator surfaceScale through managed operations
ExpandMSPs and partner-led deployments stay on the same module family, routes, and workspace logic instead of a second product line.
MSP surfaceStandalone module
Start with one module such as Workforce, Surveillance, Access, or NetworkSearch without losing the upgrade path into MANPRA.
Best for: Single-site or single-workflow adoptionConnected platform
Combine modules into one MANPRA command system with shared identity, timeline, device context, and admin controls.
Best for: Multi-module operations and multi-site teamsMSP / managed operations
Run many customers or sites through one managed delivery model with shared billing, client, and rollout structure.
Best for: Partners, SIs, and recurring service teamsBuild your stack
Core OS
- MANPRA command center shell
- Shared identity and policy context
- Cross-module operations timeline
Core modules
- MANPRA Workforce
- MANPRA Surveillance
- MANPRA Access
- MANPRA NetworkSearch
Add-on packs
- Advanced reporting
- Retention extensions
- Premium support lane
Services
- Migration readiness
- Deployment acceleration
- Executive review support
Partner tools
- MSP tenant controls
- Multi-client health board
- Partner delivery workflows
Future ecosystem direction
- Marketplace-ready connector surfaces
- Expanded automation paths
- Regional deployment expansion
Buyer journey lanes
SMB · Self-serve
Single-site teams starting with one module
Route: Signup → onboarding → first workflow in appPurchase motion: Monthly plan with optional add-onsMid-market · Guided rollout
Multi-site organizations with operations and security workflows
Route: Discovery review → migration plan → staged go-livePurchase motion: Growth or bundle plan with migration servicesEnterprise · Architecture review
Organizations requiring governance, auditability, and policy controls
Route: Trust review → deployment design → phased activationPurchase motion: Enterprise package with support and review lanesMSP / Partner-led
Service providers operating multiple client environments
Route: Partner onboarding → tenant rollout → managed operationsPurchase motion: Partner model with service and support stackRoute map from discovery to operations
Start with the product family
DiscoverPublic pages explain each module on its own while keeping the connected platform story visible from the first click.
CustomerChoose the commercial path
ScopeTeams can buy a standalone module, a connected platform, or a managed delivery lane without changing the operating model.
AdminRun one command surface
OperateThe authenticated app keeps timeline, attendance, surveillance, access, and devices inside one command system.
OperatorScale through managed operations
ExpandMSPs and partner-led deployments stay on the same module family, routes, and workspace logic instead of a second product line.
MSP