/ Technology infrastructure for physical operations that cannot stop.
We own the result. You accept the standard.
You get a defined system, clear responsibilities, and a product support path. You do not get a private architecture, a named engineer, or an unlimited list of things for Surya to do.
These boundaries do not excuse product failures. Inside the accepted scope, Surya is responsible for restoring the product.
/ Four fit requirements
What acceptance of the standard means.
Supported configuration
For Surya Endpoint and Surya Fabric, the declared scope sits inside the released envelope for identity, endpoints, applications and network. For Surya Standby, the requirement is an operational one: the existing configurations to reproduce are agreed and reproducible, the issuance permissions and approvals are agreed, and the locker or secure room and cage placement is confirmed.
Required licenses and equipment
For Surya Standby and Surya Endpoint, you own the equipment, including the prepared replacements. For Surya Fabric, the network system equipment is supplied by Surya. The Microsoft licenses that the managed products require are in place on your paper; Standby does not automatically require the Microsoft licenses of Endpoint or Fabric; any licensing dependencies of the agreed replacement workflow and customer configuration are confirmed during qualification.
Authorized business and data owners
Named people decide access, data permissions and purchasing.
The product change process
Changes to the standard follow the product's change process rather than per-site improvisation.
/ The released envelope
What the standard supports.
Before an order is accepted, the selected product profile, supported scope and prerequisites are confirmed in writing.
| Dimension | Applies to | Supported rule |
|---|---|---|
| Tenant and identity | Surya Endpoint | A supported Microsoft commercial tenant with an approved identity model, starting with cloud-native Microsoft Entra join. Hybrid and domain-dependent environments complete a separately owned transition first unless a shared hybrid profile is released. This is an Endpoint prerequisite and does not automatically apply to Surya Fabric. |
| Identity for Surya Fabric | Surya Fabric | Fabric requires the administrative identities, access and approvals its selected network profile calls for, named during qualification. It does not inherit the Endpoint endpoint-join prerequisite, and no exception beyond the released profile is created for it. |
| Identity for Surya Standby | Surya Standby | Standby does not take over your tenant. Employees use their existing corporate identity to reach the agreed replacement workflow, and the identity integration, access permissions and approvals that workflow needs are agreed during qualification. |
| Endpoints | Surya Endpoint | Supported Windows hardware and currently supported Windows releases named in the release manifest. Other endpoint operating systems are outside the supported standard. |
| Applications | Surya Endpoint | A versioned catalogue of supported applications, integrations and peripherals. Supported administrative operations belong to the product; application development and vendor defects do not. |
| Network | Surya Fabric | Approved edge, switch, wireless, segmentation and connectivity profiles. Capacity variants follow tested need, not preference. |
| Sites and geography | Surya Standby, Surya Endpoint | Each Endpoint-enrolled site receives the physical recovery arrangement its released profile requires, including a branded Surya Smart Locker where one is specified. Where Surya Standby covers qualified network or site equipment instead, that equipment is held in an existing secure room or cage outfitted with Surya RFID, and a network-only Standby scope does not require a locker. Single-site organizations are not excluded. Installation, field response and replenishment coverage are confirmed for the proposed sites during qualification. |
| Capacity | All products | Released maxima for tenants, sites, users, endpoints, applications, network throughput and automation load are being qualified. An unvalidated limit blocks a standard quote rather than becoming an assumed range. |
| Microsoft licensing | Surya Endpoint, Surya Fabric | Each released profile has a license and control matrix. A capability your licenses do not include is named, not quietly dropped from the baseline. |
| Business ownership | All products | A decision-maker, data and access owners, purchasing authority and a site contact are required. A customer-employed infrastructure operator is not. |
| Existing equipment | Surya Standby, Surya Fabric | For Surya Standby, your existing laptop image or equipment configuration is captured per agreed role or equipment type, and replacements are prepared to that configuration; this is a physical process with agreed reproducible configurations, not a tenant takeover. For Surya Fabric, Surya provides the network system for the agreed sites: Surya supplies the equipment and its standard configuration, installs and tests it before operation, and maintains it, so existing network equipment is not adopted into the supported scope. Where Surya Endpoint is purchased, existing endpoints are reused only to the extent the released supported profile permits. |
| Excluded specialty systems | All products | Servers, arbitrary Azure workloads, industrial control systems, medical devices, custom voice systems and specialized peripherals are not implicitly covered. They require a separately released profile, not a custom statement of work. |
/ Reporting and evidence
Reporting configuration and evidence handoff.
The Vanta reporting configuration and evidence mapping for the purchased scope are defined, connected and checked as part of acceptance, and the evidence handoff to your compliance owner is recorded. Any requested auditor coordination is confirmed at the same time.
The evidence listed illustrates the product's contribution; the configured reporting scope determines which records are transmitted automatically. Vanta licensing, connection scope, reporting details and any third-party assessment fees are confirmed in the commercial scope.
/ Included, your decision, outside
Everyday situations, and who holds them.
| Situation | Included in the product | Your decision | Outside the product |
|---|---|---|---|
| A device or qualified site equipment fails | Under Surya Standby, a replacement prepared to the agreed configuration, the authorized and recorded issuance and custody, the return and certified erasure, and replenishment of the stock. | Who is authorized to collect a replacement, and the agreed configurations. | Ongoing administration of the production estate, which stays with your organization or its current provider unless Surya Endpoint or Surya Fabric is purchased. |
| A password or sign-in problem | Handled under the documented recovery path of the applicable purchased managed product (Surya Endpoint or Surya Fabric). Surya Standby alone does not include this. | You confirm the business authorization for a recovery. | - |
| A new hire or a leaver | The supported technical actions from the standard input and role catalogue, under Surya Endpoint. Surya Standby alone does not include joiner, mover and leaver handling. | The employment and access decisions. | A bespoke HR integration, unless a released profile covers it. |
| A Microsoft or carrier outage | Detection, the declared behaviour, and the escalation with a named owner, under the applicable purchased managed product. | Business communication to your own people. | Repair by the vendor or carrier. |
| A business-application error | The supported foundation beneath it, and evidence for the vendor, under the applicable purchased managed product. | Which vendor is engaged and how it is prioritized. | The application's own defects and development. |
Surya operates the supported technology foundation. The business, its applications, its AI workflows, access decisions and data authority stay with your organization.
/ Change management
What happens when the standard is changed.
- Supported changes follow the product's change process: proposed, validated against the release, and applied through the released method.
- When you or a consultant changes the standard, the affected scope is identified, its status is restored or resolved, and the record says which parts are back on the standard.
- A change to one setting does not void every obligation. The affected scope is what changes status.
- You can hire your own consultants at any time. Surya does not become their implementation staff, and they cannot create obligations for Surya.
/ Fit
Where the product fits, and where it does not.
Start with the product you need. Fit depends on its supported configuration, the owners and approvals it requires, and acceptance of its change process. We confirm dependencies and prerequisites in writing before accepting an order.
Surya Standby
We check the proposed sites, which equipment classes are written into scope for each site, the existing configurations Surya will capture and reproduce for each agreed role or equipment type, locker placement or secure room and cage readiness, the identity and approval arrangements the replacement workflow needs, field response and replenishment coverage.
Surya Endpoint
We check supported devices, approved applications and peripherals, identity and licensing dependencies, protected-data recovery, and the physical replacement arrangement required by the selected profile.
Surya Fabric
We check the declared sites and their supported network scope, the system Surya will supply and install, connectivity, site readiness and structured cabling, recovery procedures, and any identity or platform dependencies required by the selected profile.
Surya Foundation
We check the Standby, Endpoint and Fabric requirements together for the declared sites, plus the shared identity, licensing and site prerequisites that operating those products on one standard depends on.
A fit
- A supported configuration for the selected product
- Named business, access and data owners where required
- Acceptance of the product's operating standard and change process
- Confirmation of the prerequisites for the proposed scope
Not this release
- A requirement for a private architecture, a named engineer or a bespoke roadmap
- A requirement to keep unsupported equipment, integrations or identity models inside a purchased managed scope. Keeping your existing production setup outside a Standby replacement scope is not disqualifying
- Specialty systems as the core need: servers, industrial control systems, medical devices or custom voice
- Open-ended consulting, staffing or blocks of hours instead of a product
- Technology that cannot be standardized or qualified in this release
Start with Standby. Add Endpoint, Fabric, or both.
Start with Surya Standby on its own, or add Surya Endpoint, Surya Fabric or both on top of it, at the outset or later. Each product includes the capabilities required by its released profile, and Surya Control is included with Endpoint and Fabric. Surya Foundation is Standby, Endpoint and Fabric together.