/ Compare

Surya vs a traditional MSP.

Both run your IT. The difference is what the price includes, who touches the hardware, and whether the number is published before you sign.

/ Dimension by dimension

Dimension

Surya

Traditional MSP

Scope

Your IT Department: support, endpoint management and security, one standard setup per role, Standby readiness, and the physical device operation. Sites, deployment events, Surya Critical devices and Azure infrastructure are quoted or published separately.

Scope is written per agreement. Support and endpoint management are typical; device logistics, security operations and projects are commonly separate line items or statements of work.

Pricing model

$100 per person per month, with a $5,000 monthly floor covering up to 50 people. Device movements bill per event at published rates. The rates are on the site before you sign.

Per-user, per-device, hourly, or blocks of time, depending on the agreement. Rates vary by agreement and are set in negotiation.

Staffing model

Remote delivery from the RTP hub. AI-driven support with human specialists behind it. No engineers sold by the hour.

A named team or a shared pool, depending on the agreement. Recurring on-site field technicians and after-hours coverage are usually priced as additions.

Physical device layer

Part of the operation, not an add-on. Devices are received, staged, stored and shipped from the RTP hub, tracked by serial number at every movement.

Often subcontracted to a logistics or reseller partner, or handled by a field technician on a visit.

Security operations

Endpoint management and security run inside your Microsoft 365 tenant: one hardened standard setup per role, access mapped per person, enforcement on the Microsoft security stack.

Baseline patching and antivirus are common in the base agreement. Hardening, access mapping and compliance work are typically scoped as projects.

Onboarding

One working session. The session is the discovery, and a fixed deployment quote comes out of it.

An assessment or discovery phase, then an onboarding project, usually billed separately from the recurring agreement.

What stays your responsibility

Microsoft licensing, and hands at the site. Site work is done by your own staff on guided runbooks, or by a partner we coordinate. Applications and strategy stay with you.

Licensing, and whatever the agreement leaves out — commonly applications, vendor management, and anything outside the named scope.

Scope

Surya

Traditional MSP

Scope is written per agreement. Support and endpoint management are typical; device logistics, security operations and projects are commonly separate line items or statements of work.

Pricing model

Surya

$100 per person per month, with a $5,000 monthly floor covering up to 50 people. Device movements bill per event at published rates. The rates are on the site before you sign.

Traditional MSP

Per-user, per-device, hourly, or blocks of time, depending on the agreement. Rates vary by agreement and are set in negotiation.

Staffing model

Surya

Remote delivery from the RTP hub. AI-driven support with human specialists behind it. No engineers sold by the hour.

Traditional MSP

A named team or a shared pool, depending on the agreement. Recurring on-site field technicians and after-hours coverage are usually priced as additions.

Physical device layer

Surya

Part of the operation, not an add-on. Devices are received, staged, stored and shipped from the RTP hub, tracked by serial number at every movement.

Traditional MSP

Often subcontracted to a logistics or reseller partner, or handled by a field technician on a visit.

Security operations

Surya

Endpoint management and security run inside your Microsoft 365 tenant: one hardened standard setup per role, access mapped per person, enforcement on the Microsoft security stack.

Traditional MSP

Baseline patching and antivirus are common in the base agreement. Hardening, access mapping and compliance work are typically scoped as projects.

Onboarding

Surya

One working session. The session is the discovery, and a fixed deployment quote comes out of it.

Traditional MSP

An assessment or discovery phase, then an onboarding project, usually billed separately from the recurring agreement.

What stays your responsibility

Surya

Microsoft licensing, and hands at the site. Site work is done by your own staff on guided runbooks, or by a partner we coordinate. Applications and strategy stay with you.

Traditional MSP

Licensing, and whatever the agreement leaves out — commonly applications, vendor management, and anything outside the named scope.

/ The honest cases

When a traditional MSP is the better fit

Three cases where an MSP agreement fits your situation and ours does not.

You want recurring on-site field technicians — a person in the building on a schedule. We deliver remotely from the hub and rely on your staff or a coordinated partner for hands at the site.
You are not on Microsoft 365. Our endpoint management, access policies and standard setups run inside a Microsoft 365 tenant. Without one, the operation does not apply.
You want time-and-materials flexibility — buy hours, direct them where you choose, change scope month to month. Our price is fixed per person and the scope is fixed with it.

Put your own numbers in.

The calculator gives you a monthly figure and an estimate of movement spend. The working session turns it into a fixed quote.

Price My Fleet →Have a conversation →