Technology infrastructure for physical operations that cannot stop.
Technology infrastructure for physicaloperations that cannot stop.
Surya standardizes and operates the network, the endpoint environment, physical recovery, the OT security foundation and the AI operating layer behind mission-critical physical environments. Your IT team focuses on the business. Surya keeps the supported foundation operating.
Surya is built for organizations whose operations depend on physical sites: plants, hospitals and clinics, smart buildings, logistics and distribution, life sciences, energy and other environments where a technology failure stops real work.
/ Why physical operations are different
In a physical environment, a technology failure stops real work.
In an office, a failure is an inconvenience. In a plant, a hospital, a distribution center or a laboratory, the same failure stops a line, delays a patient, holds a shipment or invalidates a run.
Environments like these hold equipment that cannot be replaced on demand, networks that reach places people do not, endpoints that live on carts and forklifts and benches, and operational technology that was never designed for a modern security model.
That is why Surya is built as a product with defined behaviour, prepared recovery and standardized operation, rather than an engagement that improvises each time something breaks.
Surya operates the technology foundation. Surya does not run production machinery, clinical care or the business process itself.
/ The five elements
Five elements, delivered as one product.
/ 01
Surya Fabric
The network, built to the standard.
Approved edge, switching, Wi-Fi, segmentation, connectivity and recovery, operated to one released profile with a tested recovery procedure.
Boundary
Unsupported network configurations must change before enrollment. A single connection is not sold as redundant. Surya does not control carrier repair, building power or production machinery.
/ 02
Surya Endpoint
A reproducible endpoint and workplace environment.
Supported identity, endpoint provisioning, Intune configuration, controls, approved applications and protected-data recovery. Autopilot, Intune and Graph are Microsoft functionality; the product is the engineered combination and its verified operation.
Boundary
A defined Microsoft foundation, not every application or every Microsoft feature. No line-of-business software engineering, business-process redesign or unlimited training. A replacement device is not a backup, and local-only data outside the protected locations is not promised to reappear.
/ 03
Surya Standby
Working replacements and the supply chain behind them.
Lockers, prepared inventory, authorized issuance, returns, readiness checks and replenishment, so a replacement is prepared before it is needed.
Boundary
Supported devices and published logistics terms, not unlimited procurement. A prepared replacement covers device failure, not an application outage, an identity outage, a power loss or every network fault.
/ 04
Surya Control
The system that maintains the system.
Customer-dedicated operations compute in Surya's Research Triangle Park facility, with tested automated actions, continuous configuration verification and an explicit exception path.
Boundary
No arbitrary privileged AI agent and no custom automation built per customer. Dedicated compute does not mean a dedicated facility, power, staff, logging infrastructure or downstream cloud service. Continuous monitoring is not the same as staffed 24/7 incident response.
/ 05
Surya AI Foundation
The controlled foundation for your AI work.
Approved Microsoft Copilot and Cowork capabilities, identities, connectors, data boundaries, auditability and consumption controls. Licensing, access, model selection and consumption are separate requirements, not one statement that Copilot is included.
Boundary
Your organization builds and owns its business workflows. No AI strategy retainers, departmental discovery, custom workflow development, model training or output-accuracy guarantees. The employee-facing AI foundation is separate from the local model used by Surya Control.
One platform, five operating elements. Not five practices to assemble into a custom engagement.
/ Start with one domain
Adopt the element your operation needs first.
Most organizations start with the element under the most pressure and add the others as the standard proves itself. Every element is operated to the same released standard whether it arrives first or last.
Surya Endpoint
The endpoint and workplace environment: identity, provisioning, configuration, protection and protected-data recovery.
See the detailSurya Fabric
The site network: approved edge, switching, wireless, segmentation, connectivity and tested recovery.
See the detailSurya Standby
Physical recovery: on-site lockers, prepared inventory, authorized issuance, returns and replenishment.
See the detailSurya AI Foundation
The governed foundation for AI work: approved models, connectors, access groups, data boundaries and audit.
See the detailOT and CPS security
Visibility and security for operational and cyber-physical systems, delivered with Claroty inside a defined boundary.
See the detail/ What Surya is not
A product company, not a services firm.
Not an MSP
You are not buying general IT support, ticket coverage or a co-managed arrangement. You are buying a defined product with a supported standard.
Not a consultancy
There is no discovery phase that produces a bespoke architecture. The standard exists before you arrive.
Not a staffing company
Surya does not sell engineer hours, named resources or blocks of access to people.
Not a custom build
Released profiles define what is supported. Anything outside them is stated plainly rather than customized around.
Product support is included. Open-ended consulting is not.
/ Where Surya operates
Environments where stopping is expensive.
Manufacturing plants
Production networks, plant endpoints, OT segmentation and prepared replacement at the line.
Hospitals and clinics
Clinical endpoints, identity, protected data recovery and a working replacement inside the building.
Logistics and distribution
Scanners, carts, wireless coverage and endpoints that move all day inside a large footprint.
Life sciences
Instrument-adjacent endpoints, controlled configuration, protected data sets and audit-ready operation.
Smart buildings and energy
Distributed sites, building systems on the network, segmentation and tested recovery.
Multi-site operations
Organizations opening, refreshing or acquiring sites that must run to one standard, not local habit.
Excluded unless a released profile exists: arbitrary Azure workloads, industrial control system programming, medical devices, custom voice systems and specialized peripherals.
/ Your internal IT team
Surya is the foundation your team stops maintaining.
Surya does not replace your IT organization and does not take authority away from it. Access decisions, business applications, AI workflows and priorities stay where they belong.
What changes is the routine work: provisioning, configuration drift, network firefighting, replacement logistics and the standing coordination behind them run as a product instead of as your team's week.
If ordinary operation of the accepted system still requires a services firm alongside it, the product has not met its design objective.
/ Standardized on purpose
The standard is the product.
Every customer runs released profiles. That is what makes behaviour predictable, recovery testable and improvements deliverable to everyone at once.
Qualification checks whether your environment fits those profiles. Where it does not, the gap is named and either resolved before installation or stated as out of scope.
Where Surya is not the right product.
- Fully remote organizations with no physical operation to protect.
- Environments that require a bespoke architecture rather than a released standard.
- Buyers looking for general IT support hours or a co-managed services arrangement.
- Requirements that depend on unsupported configurations no released profile covers.
/ Clean ownership
You own the assets. Surya owns the product.
You own
- Microsoft and other software licensing, on your paper
- Endpoints, network equipment and spare inventory
- AI, cloud and backup consumption accounts
- Internet circuits and carrier relationships
- Your data, your tenant and every access decision
Surya owns
- The product software, standards and released profiles
- The automation and operating logic behind them
- Deployment artifacts, releases and orchestration
- The locker hardware it installs and operates
- The methodology that keeps every customer on one standard
Because the assets and licensing are yours, leaving is a transition rather than a rebuild. Exit treatment comes from the approved agreement.
/ Product accountability
What the product is accountable for.
- The supported network operates to the approved configuration and can be restored to it.
- A supported endpoint can be provisioned, protected and restored to the defined working state.
- A working replacement is prepared at the site before it is needed.
- The supported operating state is continuously evaluated, with prohibited actions stopped and raised.
- AI access behaves as policy says it should, with usage visible and audited.
/ Deployment
A 30-day installation target. A defined finish line.
The target covers a declared, qualified installation after site, equipment, access, licensing, and compatibility requirements are met. Completion means the acceptance tests pass across all five elements.
The clock depends on readiness: site and cabling, equipment on site, administrative access, licensing, and compatibility resolved. Unmet prerequisites move the start, not the finish line. The target applies to a declared, qualified scope, not to transforming an organization.
/ 01
Qualify
The declared scope is compared against the released standard, and prerequisites are named and owned.
/ 02
Install
The five elements are installed to the released profile for the declared scope.
/ 03
Test
The acceptance tests for each element are run and their evidence recorded.
/ 04
Accept
Acceptance is the point where every required test has passed for the declared scope.
/ Evidence
Show that it works.
These are the acceptance requirements evidenced for the declared scope. Every deployment is accepted against them, and the results are recorded.
- A working replacement reaches the person and restores the defined working state.
- Network recovery returns the approved configuration.
- Identity recovery works, and an unauthorized recovery attempt is denied.
- A data restore returns protected data to the defined state.
- AI access is denied where the policy says it should be.
- A permitted automated correction is applied and verified.
- A prohibited action is stopped and raised through the exception path.
- The operations appliance is replaced and rebuilds its working state.
Surya's documented work covers multi-site device logistics, preparation, delivery, recovery and custody. It is the operational history behind Surya Standby, reported at its own scope rather than as a claim about the whole product.
/ Commercial transparency
Know the whole commitment before you sign.
Installation
The one-time installation of the declared scope, quoted from the released standard and its published options.
Recurring product
The subscription that covers operation of all five elements for the accepted scope.
Equipment and spares
Customer-owned. You purchase and own the endpoints and the replacements held in the locker.
Software licenses
Microsoft and other vendor licensing stays on your paper and your agreements.
AI, cloud and backup consumption
Usage-based charges for AI, cloud and backup services are separate from Surya's charges.
Logistics and site options
Shipping, field response and released site options follow the published territory and terms.
The released standard, the quantities and the published options determine the quote. There is no bespoke solution to price.
If a covered site loses a business day to technology we operate, that site's month is free.
/ Straight answers
Straight answers.
/ Technology infrastructure for physical operations that cannot stop.
See whether your organization fits the product.
Bring your tenant, site, device, and application requirements. Qualification checks compatibility with an existing standard. It does not begin a consulting engagement.