/ For IT leadership
Give your team a reliable foundation to build on.
Surya operates standardized endpoint and site-network products. Your team retains business applications, access decisions, integrations and the workflows that move the organization forward.
CIOs, IT directors, IT managers, infrastructure owners and internal IT teams.
/ 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.
What the foundation covers.
/ 01
Endpoint
Supported identity and endpoint configuration, provisioning, protection, defined data recovery and the required physical replacement capability.
/ 02
Fabric
The complete site-network system provided by Surya - supplied equipment and standard configuration, segmentation and tested configuration recovery, with Claroty capabilities where the OT and CPS scope applies.
/ Products
The products.
Standby is where the relationship starts and is complete on its own: Surya captures your existing configurations per role and prepares replacements to them, while ongoing administration stays with your team or its current provider. Endpoint and Fabric are added on top of it, independently and in either order, and each includes Surya Control and the operating elements its released profile requires.
Surya Standby
Prepared replacement equipment at the site, with authorized issuance, returns, certified erasure and replenishment.
Surya Standby in detail →Surya Endpoint
Identity and endpoint configuration, provisioning, protection, protected-data recovery and the required physical replacement capability.
Surya Endpoint in detail →Surya Fabric
Site networking, segmentation and tested configuration recovery.
Surya Fabric in detail →OT and CPS security
Claroty capabilities inside the Fabric scope where operational and cyber-physical systems are present.
OT and CPS security in detail →Each product has its own business reason to buy, subject to its actual prerequisites. Standby does not require Endpoint or Fabric, and buying Fabric does not automatically require Endpoint. Standby on its own does not include Surya Control.
/ First purchase
Start with a supported scope.
Adoption follows the same sequence for every product.
/ 01
The selected product
One product and one declared scope, chosen against the problem you want solved first.
/ 02
Actual prerequisites
Identity, tenant, network and application prerequisites are reviewed against the released profile. Some products carry tenant-wide dependencies; those are stated during qualification rather than discovered later.
/ 03
Systems and providers that remain
Existing applications, vendors, providers and internal systems that stay outside the Surya scope are named.
/ 04
Required approvals
Your named owner authorizes the consequential changes the deployment requires.
/ 05
Acceptance tests
The product is accepted against the acceptance criteria of its released profile.
/ 06
The ongoing support path
Faults inside the accepted scope follow the product support path.
Where a material detail is unresolved, compatibility and scope are confirmed during qualification rather than assumed here.
Surya operates. Internal IT retains.
Surya operates
- The released scope of each purchased product
- Endpoint and network configuration inside that scope
- The defined protection and recovery behaviour
- Product faults and supported vendor escalation
- Release improvements delivered to every customer at once
Internal IT retains
- Business applications and their vendors
- AI workflows, process design and adoption
- Access and business decisions
- Integration with business systems
- The results the business wants
What is outside the product.
- Not included: Bespoke architecture, staffing or named engineers
- Not included: Unrestricted IT support or open project menus
- Not included: Application development and business process redesign
- Not included: Configurations outside the released profile
/ Deployment
Your first deployment.
Deployment starts with a defined scope, a single site or a single group of equipment, rather than the whole estate. The relationship starts with Surya Standby, and 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.
/ 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 agreed equipment classes, the existing configurations captured per role, the prepared replacement positions for them, and the acceptance tests for that scope. 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 you can inspect.
The released standard, the deployment model, documented operations and the security documentation request path are all published. Acceptance criteria are product-specific and confirmed during qualification.