/ For private equity
A repeatable technology foundation for portfolio companies with physical operations.
Surya gives supported locations a common approach to computers, site networks, and recovery. Begin with one portfolio company and a defined deployment, then evaluate where the same products fit across additional locations.
Operating partners, portfolio operations leaders and technology leaders supporting portfolio companies with physical operations.
/ Two business outcomes
Site resilience
Be ready when technology fails.
Prepare the devices, configurations, and recovery procedures your sites depend on, so a supported failure has a defined path back to work.
Security and compliance
Protect the operation. Show the controls.
Control equipment custody, user access, and network connections, with records that help demonstrate how the purchased scope is protected.
Where portfolio complexity shows up
/ 01
Acquisitions bring different technology setups
Equipment, configurations, providers, and responsibilities vary across acquired businesses and locations.
A common product standard does not resolve every acquisition integration requirement.
/ 02
Expansion repeats the same decisions
Each new site can require another round of configuration, purchasing, and recovery planning.
/ 03
Operating risk is difficult to compare
Different practices make it harder to understand which locations are prepared for supported technology failures.
What a common standard can give you
Repeatable deployment
Apply supported product profiles at additional locations after compatibility is confirmed.
Clear cost drivers
Understand the subscription, deployment, equipment, licensing, and other requirements for each proposed scope.
Defined responsibility
Know what Surya operates and what remains with the portfolio company and its vendors.
Inspectable evidence
Use agreed acceptance and operating evidence to evaluate the supported environment.
/ Products
The products behind the standard
The same products apply in every portfolio company. There is no separate private equity offering.
Surya Standby
Prepared replacement equipment at the site, bought on its own where that is the pressure.
Surya Standby in detail →Surya Endpoint
Standardized computers and prepared recovery, with prepared physical replacement where the product requires it.
Surya Endpoint in detail →Surya Fabric
Supported site networking, security boundaries and a defined recovery procedure.
Surya Fabric in detail →OT and CPS security
Applicable Claroty capabilities inside the Fabric scope where operational and cyber-physical systems are present.
OT and CPS security in detail →Surya Foundation operates Standby, Endpoint and Fabric as one system. There is no advisory retainer, consulting package or custom architecture offering.
/ First purchase
Start with one company
One portfolio company, one product, one defined scope.
/ 01
Select a portfolio company
Choose one with a concrete infrastructure or recovery problem.
/ 02
Choose the relevant product and an initial scope
The locations, users and devices in the first scope are named.
/ 03
Confirm compatibility, prerequisites, ownership, and commercial terms
Prerequisites and responsibilities are written down before installation.
/ 04
Deploy and verify the agreed operating behavior
Acceptance is against the product's own tests.
/ 05
Use the results to evaluate expansion
Extend to other suitable locations only where the evidence supports it.
A common product standard does not require portfolio companies to share a Microsoft tenant or pool business data. Access and information sharing require each company's authorization, and there is no automatic cross-company visibility or portfolio-wide access.
Where a material detail is unresolved, compatibility and scope are confirmed during qualification rather than assumed here.
Each product has its own prerequisites. Standby does not require Endpoint or Fabric, and buying Fabric does not automatically require Endpoint. Any dependencies that extend beyond the selected site are identified during qualification.
Where Surya fits in acquisition and expansion work
Surya's potential scope
- Supported endpoint configuration and lifecycle
- Prepared physical device recovery
- Supported site networking
- Defined security boundaries and applicable Claroty capabilities
The company and its specialists retain
- ERP, EHR, and other business-application integration
- Business-process and organizational integration
- Clinical systems and production-equipment functionality
- Transaction diligence, legal work, and integration strategy
Evidence before expansion
Documented operations and the trust material are published, and historical delivery evidence is kept separate from the results of any new product deployment. Cost reduction, faster expansion and improved consistency are outcomes to evaluate against an agreed baseline, not guaranteed results.