Mass Deployment Events

When a corporate event moves ten thousand devices, it is quoted as one project.

An acquisition closes. A division carves out. A site opens. The fleet reaches end of life. A cloud migration or an Azure environment build lands on the calendar. Each one is a mass deployment event: a defined scope, a defined date, and one fixed price after a working session. Machines are set up the same way every time — the approved apps, settings, and security baseline every machine gets — deployed, and the outgoing fleet recovered, erased for good (certified to the NIST 800-88 standard), and retired, each one tracked by serial number. Executed from the RTP hub.

Ongoing operations are not an event. Support, security, the setup for every role, your Azure infrastructure run to the operating system line on its own published line, and the day-to-day device lifecycle run inside Your IT Department at $100 per person per month.

/ 01 The Boundary

Your people are covered. Your events are quoted.

Anything a person triggers — a new hire, a departure, a failed device, a role change — is inside the $100 per person per month, unlimited. Anything a corporate event triggers — an acquisition, a new site, a fleet-wide refresh, a cloud migration or Azure environment build — is a mass deployment event, scoped and quoted as a fixed project.

/ Inside Your IT Department

AI-driven end-user support with a human specialist behind it, every machine kept patched and locked down, with company systems reachable only by the person they belong to, on a healthy machine (Microsoft Intune and Entra), the setup for every role kept current, your Azure infrastructure run to the operating system line, and the physical lifecycle: RTP hub operations, on-site spare pools, same-day Standby, onboarding and offboarding, moves and changes. One number, no hourly meter.

See the price →

/ Quoted as a fixed project

A mass deployment event has a start, an end, and a volume that has nothing to do with headcount changing one person at a time. We scope it against your standard and your calendar and come back with one number and a date. Ownership does not change inside an event: we own the machine end to end — the hardware, its setup, keeping it secure, and the person's support. You own your Microsoft accounts and the back ends of your own business applications.

/ 02 Event Types

Different triggers. The same physical work.

Every one of these arrives looking like a different problem, owned by a different executive, on a different clock. Underneath it is the same work: devices set up, moved, recovered, and accounted for by serial number.

/ 01

Acquisition waves

Acquired-company devices rebuilt to your managed standard and reconciled against the acquired inventory, against a close-date deadline rather than a comfortable one.

/ 02

Carve-outs and separations

The same play in reverse: the divested population rebuilt to a new standard, and the parent's devices recovered and reconciled before the transition service agreement expires.

/ 03

Collections at scale

When a population leaves at once, recovery is the event. Return kits with a label on your carrier account, guided workflows, and escalation on non-returns. Every recovered device reconciled by serial number — back to stock or disposition.

/ 04

New-site standups

A plant, clinic, or office comes online with devices pre-staged and set up on a date you can plan against, and an on-site spare pool positioned before the first shift.

/ 05

Fleet-wide refresh

Thousands of devices cohorted by role and site, deployed in waves, with the outgoing fleet recovered on the same schedule, erased for good (certified to NIST 800-88), and disposed of with a certificate per serial number.

/ 06

Cleaning up your hardware records

Physical inventory reconciled against your system of record. Devices that exist only on paper are found or written off with evidence, and lifecycle states are corrected against the serial ledger.

See how an event is executed →

/ 03 How An Event Runs

Scoped in waves, executed from one floor.

Waves are matched to hub capacity and your business calendar — by division, site, or business unit — and every step is a record against a serial number.

  1. / 01

    Working session and scope.

    Volume, sites, dates, your managed standard, and the constraints that actually govern the calendar. Out of it comes a written scope and one fixed price. No hourly rates.

  2. / 02

    Intake and staging at the RTP hub.

    Devices received, serialized, and asset-tagged before they enter our racks. Freight runs on your carrier account throughout.

  3. / 03

    Set up the same way, every time.

    One build per role — the approved apps, settings, security baseline, and hardware settings — with peripherals kitted and serialized to your spec.

  4. / 04

    Deployment in waves.

    Direct-to-employee shipping for distributed staff; at sites, swaps are performed by your own staff to a guided workflow with a Surya specialist on the line, or by a partner we coordinate — cohorted so no single wave outruns capacity.

  5. / 05

    Recovery and disposition.

    Return kits with a label on your carrier account and guided workflows, erased for good (certified to NIST 800-88), refurbished for redeployment or destroyed with certification, with a disposition certificate and complete record filed against every serial number.

  6. / 06

    Handoff into Your IT Department.

    When the event closes, the population it touched is already inside Your IT Department at $100 per person per month. There is no second onboarding.

4,000 devices

Operated at scale for a private equity-backed national accounting and advisory firm.

0.66 movements / device / yr

Measured across the fleets we operate over a 16-month window. A movement is any physical event: a shipment, a swap, a return, a repair.

/ 04 Who This Is For

An event with a date on it.

/ Scale

Populations in the hundreds to tens of thousands.

Multi-site or multi-region footprints, procurement-led sourcing under master agreements.

/ Shape

A defined scope with a defined end.

An acquisition wave, a carve-out, a collection, a site standup, a refresh — scoped, quoted as one fixed project, and delivered against a date.

/ Standards

Vendor risk assessment as a default gate.

NIST 800-171-aligned handling, every device tracked by serial number, audit-grade reporting. SOC 2 Type II in progress — report available on completion.

/ Assurance

Documented and ready for your risk team.

SOC 2 Type 2 — audit in progress
HIPAA-aligned operations with BAA capability
NIST 800-171-aligned facility
Erased for good, with a certificate (NIST 800-88)

Security questionnaires, control evidence, and policy review under NDA are a standard motion.

/ 05 Next Step

Bring us the event. Leave with a scope.

One working session. We map the event against your standard and your calendar and come back with a fixed-scope quote your procurement team can act on — and Your IT Department price for everything that follows it.

Price My Fleet →Have a conversation →

/ Contact

Start a conversation with our RTP team.

One working session. Fleet, sites, what breaks today, what you want us to own. No slides.

Facility

Surya Technologies
Research Triangle Park, NC 27703

Verticals

Healthcare · Manufacturing