/ Technology infrastructure for physical operations that cannot stop.
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 every required element of the purchased product has passed its acceptance test.
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.
/ Four stages
Qualify, install, test, accept.
/ 01
Qualify
The declared scope is compared against the released standard, and prerequisites are named and owned.
/ 02
Install
The operating elements required by the purchased Surya product 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.
/ Readiness
What has to be true before the clock starts.
Readiness is checked for the products and equipment in your agreed scope. Prepared replacement positions apply wherever Standby is in scope, and their physical form follows the equipment: a Surya Smart Locker where workstations are in scope, an existing secure room or cage outfitted with Surya RFID for network equipment. A network-only Standby scope does not require a laptop locker. Tenant, identity and platform prerequisites apply to Endpoint, Fabric and Foundation, and are identified explicitly.
Site
Space, power, cabling and network ports for the declared scope. Where Surya Standby covers workstations, the branded Surya Smart Locker location is agreed. Where Surya Standby covers qualified network or site equipment, an existing secure onsite room or cage for Surya RFID is confirmed ready. (Standby, Endpoint, Fabric)
Equipment
The supported equipment for the products in scope, purchased and on site. Standby's prepared-replacement stock is agreed for the equipment classes written into scope. Endpoint spares apply where the selected Endpoint profile requires them. For Surya Fabric, the network system is supplied by Surya, so what you provide is site readiness, structured cabling and power. (Standby, Endpoint, Fabric)
Access
For Surya Standby, the identity integration, access permissions and approvals the replacement workflow needs are agreed during qualification - not a tenant takeover. For Surya Endpoint and Surya Fabric, administrative access and the consented application identities in your tenant are required for the scope being deployed. (Standby, Endpoint, Fabric)
Licensing
The Microsoft licenses the selected Endpoint or Fabric profiles require, active on your agreement. Surya Standby on its own does not require these licenses. (Endpoint, Fabric)
Compatibility
Applications, peripherals, network configurations and identity model confirmed against the released catalogue for the products in scope. (Endpoint, Fabric)
Owners
A decision-maker, data and access owners, purchasing authority and a site contact, named. (All products)
/ Acceptance
Completion means every required element of the purchased product passed its test.
Complete Foundation deployment.
A complete Surya Foundation deployment covers Standby, Endpoint and Fabric, together with the acceptance tests for the capabilities inside them, including Surya Control. A single-layer deployment runs only the acceptance tests that layer requires.
Surya Standby
A person at the site obtains a working replacement, prepared to the agreed configuration, through the runbook and returns to the defined working state, with the swap recorded.
Surya Endpoint
Provision a new supported device; restore an authorized user to the defined working state on a replacement; test account recovery and the denial of an unauthorized recovery attempt; verify approved controls; execute a safe data restore; validate joiner and leaver handling; run a controlled containment exercise.
Surya Fabric
Inventory matches the installation; required business paths succeed; prohibited cross-segment access is denied; the approved configuration can be restored; losing each included path produces the declared result.
Surya Control
A permitted automated correction is applied and verified; a prohibited action is stopped and raised; the operations appliance is replaced and its working state rebuilt from your tenant.
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.
Acceptance is a test result at a point in time. Reliability over months is measured separately and reported separately. Failure of a Surya acceptance test is Surya's responsibility to resolve.
Any published deployment example states both the contract-to-operational time and the installation clock. A prerequisite project is never hidden outside the clock.
There is no free pilot, free hardware offer or paid assessment. The product is bought and installed to the standard. Payment and remedy wording comes from the approved commercial terms.
/ What delays a deployment
The honest list.
- Prerequisites that are still open at the start of the clock
- Equipment, licensing or carrier delivery outside Surya's control
- Administrative access or approvals not yet in place
- An unsupported configuration discovered inside the declared scope
- A change to the declared scope during installation
Start with qualification.
Tell us what your physical operation does and what stops when technology fails. Qualification names the prerequisites and their owners before any date is discussed.