/ Surya Standby

Protect revenue and customer commitments by keeping your sites working when critical equipment fails.

When equipment fails at a site, work stops until something working is in its place. Surya Standby prepares for that in advance, for the equipment classes written into your scope: workstations and peripherals, and qualified site equipment such as switches, firewalls, access points and edge appliances. It is complete on its own, and it works on the configurations you already run.

Prepared replacement coverage for the equipment written into your scope, whatever class it is. Surya captures your existing configuration for each agreed role or equipment type and prepares replacements to that agreed configuration through its supply chain. Where workstations are in scope they are held in a branded Surya Smart Locker at the site; qualified network and site equipment such as switches, firewalls, access points and edge appliances is held in an existing secure onsite room or cage outfitted with Surya RFID, staged on site or shipped from the Surya facility in Research Triangle Park, with authorized issuance, returns, readiness checks and replenishment, so a working replacement is ready before it is needed.

Check Fit →See the product

/ Two outcomes

Resilience outcome

Keep equipment failures from becoming prolonged business interruptions.

Security outcome

Keep covered equipment in authorized hands, with custody documented through issue, return, and disposition.

What Surya operates to deliver them.

Surya prepares replacements for qualified equipment, manages their availability, and operates the authorized issue-and-return process.

/ What can be tested or evidenced

Prepared replacement and readiness records.
Authorized issuance linked to the equipment identifier.
Return, custody, and applicable erasure records.

The security promise is custody and handling within Standby. Ongoing production endpoint protection and network administration belong to the purchased Endpoint or Fabric scope. Standby reporting does not imply that Surya Control or ongoing tenant administration is included.

Automated reporting to Vanta

Standby supports automated reporting to Vanta for its agreed equipment and handling scope.

Surya can arrange independent auditor relationships as part of your product scope when your requirements call for them.

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.

Explore Compliance with Vanta →Compliance reporting and auditor coordination →

/ Industry compliance support

Manufacturing and CMMC support →

Documented handling of covered equipment; applicability to FCI/CUI equipment is established within the qualified scope.

Healthcare and HIPAA support →

Device and media handling records for covered equipment, including return and disposition.

Each link explains this product's contribution. No single product independently covers every requirement.

/ What the element covers

Complete on its own.

Surya starts by learning your sites and your people. For workstations, Surya captures your existing laptop image and configuration for each employee persona or role and prepares replacements to that agreed configuration through its supply chain. The same principle applies to qualified switches, firewalls and other agreed critical equipment: the existing configuration is captured and ready replacements are prepared. Authorized issuance is recorded against the serial number, with returns and repair routing, certified erasure to NIST 800-88, readiness checks and replenishment.

Where the scope includes workstations, they are held in a branded Surya Smart Locker at the site, and employees use their existing corporate identity to reach the agreed replacement workflow. Qualified critical network equipment is held in an existing secure onsite room or cage outfitted with Surya RFID and retrieved by designated staff, and larger equipment can be staged on site or shipped from the Surya facility in Research Triangle Park. Which of these applies follows the equipment and sites in your agreed scope, so a network-only scope does not require a laptop locker. Equipment outside the locker is tracked in place with Surya's own RFID tags and labelling, including in locked server rooms, so the serial-level record matches what is on the shelf.

Preparing those replacements is Standby. Ongoing standardization and administration of your production endpoint and network estate is Surya Endpoint and Surya Fabric, which can be bought directly or added later, independently and in either order. Standby on its own does not include Surya Control and does not take over ongoing tenant, endpoint or network administration: your organization or its current provider keeps that responsibility. The identity integration, access permissions and approvals the replacement workflow needs are agreed during qualification.

Who owns what.

You purchase and own the equipment, including the prepared replacements, and you name the owners who authorize issuance. In managed Standby, where workstations are in scope, Surya provides, installs, owns and operates the locker it uses at the site; where the scope is network equipment, an existing secure room or cage of yours is outfitted with Surya RFID. Surya operates the inventory to the released standard. There is no mandatory period and no mandatory upgrade to a deeper product. A smart locker you buy and operate yourselves is a separate purchase, and it is yours.

/ Standby use cases

Keep a working device close to the work.

Shift changes, failed devices and missing spares can interrupt a physical operation. Explore how approved device access, prepared replacements and local inventory can fit your site through Surya Standby, which can be bought on its own.

Device models, equipment classes, shared-use workflows, access arrangements and readiness checks are confirmed during Check Fit against the supported product scope. Preparing replacements to the configurations you already run is part of Surya Standby; ongoing standardization and administration of the production estate is Surya Endpoint and Surya Fabric.

At the start of a shift

Give each shift a clear device handoff.

Teams that share equipment need to know which device they can take, where to return it and who last used it. A defined issue-and-return workflow can bring access and accountability into the place where work begins.

A distribution team starts its shift. Each authorized employee collects an assigned or pooled device through the approved process and returns it to the designated location when finished.

What to evaluate: Device availability at shift start and a traceable return process.

When a device fails

Put the replacement at the site.

Prepare recovery before a supported device fails. A replacement held at the site can be issued through the approved authorization process, with a defined path back to the working setup the person needs.

A workstation stops working during an evening shift. The site follows its approved replacement procedure, records the issue and returns the failed device for the next step in its lifecycle.

What to evaluate: A replacement prepared to the agreed configuration, issued through an authorized and recorded handoff. Restoring declared protected data is part of purchased Surya Endpoint, not of Standby on its own.

Across multiple locations

Keep the next replacement ready.

Define which spares each site needs and what happens when one is used. A complete replacement process includes custody records, failed-device return and replenishment of the opened inventory position.

One clinic uses its prepared spare. The failed unit enters the return process, and replenishment restores the site's agreed reserve for the next interruption.

What to evaluate: Available spare positions and completion of the replenishment cycle.

Before the next device is issued

Define what ready means.

Availability starts with a device that is fit for its next approved use. Define the required configuration, application access and readiness checks, along with the return conditions that must be met before reissue.

A shared device comes back at the end of a shift. The supported workflow defines the checks and handling needed before another person can use it; a device needing attention stays out of the ready pool.

What to evaluate: Whether issued devices reach their defined usable state.

From issue to return to the next ready device.

The approved scope defines the configuration the replacement is prepared to, who may authorize access, how the working setup is restored and how returned equipment is handled. The process also covers the replacement position and its replenishment. Whether the equipment sits in a Surya Smart Locker or in an existing secure room or cage outfitted with Surya RFID follows the equipment classes in scope.

Check Fit →See how a first deployment works →

Want to run your own locker?

Surya also supplies and sets up LocknCharge smart lockers that your team owns and operates, with no Surya service subscription required.

Smart lockers with LocknCharge →

/ Related guides

Laptop locker →

/ Deployment

Your first deployment.

Deployment starts with a defined scope - one component, one site or one group of equipment - rather than the whole estate. Components such as a conference room or a smart locker are deployed and handed over on their own. Within the full workstation and site-network products, Standby provides the prepared physical recovery layer. Endpoint or Fabric is deployed to the released profile when that deeper scope is purchased, at the outset or later. Where Surya Fabric is purchased, Surya provides the network system itself: the equipment, its standard configuration, installation and testing.

Starting Surya Standby does not change how your estate is managed. Surya captures the configurations you already run for each agreed role or equipment type, prepares replacements to them, and installs the physical arrangement the scope calls for, with the identity and approval arrangements agreed during qualification. If Surya Endpoint or Surya Fabric is added later, replacement preparation then follows that managed product's agreed baseline instead of the captured configuration.

/ 01
Choose the scope
The products, the equipment classes, one site or one device group. The scope is written down before anything is installed.
/ 02
Compatibility review
For Standby, the configurations Surya will capture and reproduce, the physical placement and the approvals the replacement workflow needs. For Endpoint, your environment is checked against the released profile, including identity and platform dependencies. For Fabric, the sites, connectivity, cabling and site readiness the Surya-supplied network system needs are checked.
/ 03
Written prerequisites
Anything that must change first is stated in writing, together with the approvals your organization needs to give.
/ 04
Installation
Surya installs the agreed physical arrangement and the prepared replacements, deploys and tests the Surya-supplied network system where Fabric is purchased, and configures any purchased Endpoint scope to the released standard.
/ 05
Acceptance tests
Each product is accepted against its own tests, so the result is inspectable rather than asserted.
/ 06
Ongoing operation
Surya operates the accepted scope, and faults inside it are Surya's to resolve.

What changes in your environment

Surya Standby reproduces the configurations you already run; it does not require your estate to be rebuilt first, and keeping your existing production setup is not a barrier to it.
Standby prepares replacements for your existing supported equipment and configurations. Endpoint can retain devices where its released profile permits. Fabric supplies, installs and tests the network system for the agreed sites.
Where Endpoint is purchased, configurations inside that purchased scope are brought to the released profile, which can change how some settings are managed today, and replacement preparation then follows that baseline. Where Fabric is purchased, the supported site network runs on the Surya-supplied system and its standard configuration. Equipment and identity models outside the purchased scope are unaffected.
Approvals from an accountable owner are required for consequential changes.
Providers responsible for adjacent systems, applications or machinery remain responsible for them, and Standby on its own leaves ongoing tenant, endpoint and network administration where it is today.

An illustrative first scope: one site, the declared equipment classes, the prepared replacement positions for each of them, the named owners who authorize issuance, and the acceptance test for a recorded swap. Quantities, timing and commercial terms come from the proposal for your environment.

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.

What it depends on

The customer purchases and owns the devices, including the prepared replacements. Where workstations are in scope, Surya provides, installs, owns and operates the locker; where the scope is network equipment, an existing secure onsite room or cage is outfitted with Surya RFID. The agreed configurations to reproduce, the identity integration, access permissions and approvals the replacement workflow needs, and installation, field response and replenishment coverage are confirmed for the proposed sites during qualification.

What it excludes

Supported equipment 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. Standby prepares, stocks, swaps and tracks the replacement equipment. Ongoing standardization and administration of your production endpoint and network estate is Surya Endpoint and Surya Fabric, and Surya Control is not included with Standby on its own.

How it is accepted

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.