Mason

Name: Mason
Brand: Mason America

Mason is an end-to-end platform for building, deploying, and operating dedicated Android-based smart-device fleets, combining hardware procurement, a customized Android OS (Mason OS), and fleet management and observability tools accessible via Controller, REST APIs, and a CLI.

Est 2015|Valuation $69M|Raised $25.1M|16 Ref Customers

Website|FTEs 110

MarketsIoT Device Management

01Competitive Landscape

| Aspect | Mason (bymason.com) | Esper | Microsoft Intune | |--------|----------------------|-------|------------------| | Starting Price | Not public (custom quote likely) (public product review pages) | Published per-device pricing available from the vendor (Genesis tier) (official vendor pricing page) | Not public as “per device MDM” in the same way (bundled via Microsoft licensing; varies by plan/tenant) | | Best For | Purpose-built Android device fleets needing integrated hardware + OS control + remote debugging/observability | Dedicated Android/AOSP fleets where per-device SaaS pricing + compliance posture are key | Organizations already standardized on Microsoft ecosystem needing broad endpoint management across users/devices | | Key Strength | Deep device-level debugging via X-Ray (remote view/control + logs), integrated into CLI/APIs/Controller (official vendor documentation) | Transparent pricing tiers and published security/compliance claims (SOC 2 Type 2, ISO 27001, PCI DSS) (official vendor pricing and compliance pages) | Broad enterprise enrollment and Android kiosk/dedicated device management capabilities (official Microsoft documentation) | | Key Weakness | Limited public third-party reviews and unclear publicly posted security certifications | Hardware/OS integration may be less “single-vendor” end-to-end than Mason’s positioning | Community discussions frequently cite kiosk edge cases and complexity; Android “production appliance” needs can be tricky outside basic kiosk patterns (anecdotally) (community forum discussions) | - Direct competitors and their key differentiators - Esper - Positions strongly around modern device management for dedicated Android and provides public per-device pricing and a list of compliance certifications. (official vendor pricing and compliance pages) - Microsoft Intune - Strong choice for enterprises that want unified endpoint management tightly integrated with Entra ID / Microsoft security stack; supports Android Enterprise dedicated (kiosk) and AOSP enrollment paths. (official Microsoft documentation) - Workspace ONE / Omnissa and SOTI - Broad UEM feature sets and longstanding presence in rugged/frontline device management; may outperform on heterogeneous device OS support and advanced enterprise mobility workflows. - Feature comparison: where Mason appears to excel vs lag behind (based on public info) - Likely excels - Remote debugging/observability workflows purpose-built for Android fleets (X-Ray leveraging adb). (official vendor documentation) - Integrated approach to hardware + OS + device console (positioning as “end-to-end”). (official vendor documentation) - Likely lags / unknowns - Publicly documented compliance posture compared with competitors that publish SOC 2/ISO explicitly. - Public evidence of mature SSO/SAML/SCIM, audit logs, and enterprise IAM features (not found in accessible docs). - Pricing comparison: value proposition vs alternatives - Mason - Hard to benchmark due to opaque pricing. - May pencil out if it reduces device failure rates, field returns, or downtime for mission-critical workflows. - Esper - Easier initial ROI modeling due to published per-device pricing tiers and explicit plan packaging. (official vendor pricing page) - Market share and adoption trends (cite sources) - Not enough credible public data was found in accessible sources to quantify Mason market share. - When customers choose competitors instead (and why) - Intune / Workspace ONE - When the organization wants one UEM across laptops + mobile + identity/access policies and already owns the licensing. - Esper - When procurement requires visible compliance attestations and predictable per-device costs, and the fleet is primarily Android. - SOTI - When rugged/frontline device workflows (barcode enrollment, OEM tooling) and massive scale are central.

01Competitive Landscape

Aspect	Mason (bymason.com)	Esper	Microsoft Intune
Starting Price	Not public (custom quote likely) (public product review pages)	Published per-device pricing available from the vendor (Genesis tier) (official vendor pricing page)	Not public as “per device MDM” in the same way (bundled via Microsoft licensing; varies by plan/tenant)
Best For	Purpose-built Android device fleets needing integrated hardware + OS control + remote debugging/observability	Dedicated Android/AOSP fleets where per-device SaaS pricing + compliance posture are key	Organizations already standardized on Microsoft ecosystem needing broad endpoint management across users/devices
Key Strength	Deep device-level debugging via X-Ray (remote view/control + logs), integrated into CLI/APIs/Controller (official vendor documentation)	Transparent pricing tiers and published security/compliance claims (SOC 2 Type 2, ISO 27001, PCI DSS) (official vendor pricing and compliance pages)	Broad enterprise enrollment and Android kiosk/dedicated device management capabilities (official Microsoft documentation)
Key Weakness	Limited public third-party reviews and unclear publicly posted security certifications	Hardware/OS integration may be less “single-vendor” end-to-end than Mason’s positioning	Community discussions frequently cite kiosk edge cases and complexity; Android “production appliance” needs can be tricky outside basic kiosk patterns (anecdotally) (community forum discussions)

Direct competitors and their key differentiators
- Esper
  - Positions strongly around modern device management for dedicated Android and provides public per-device pricing and a list of compliance certifications. (official vendor pricing and compliance pages)
- Microsoft Intune
  - Strong choice for enterprises that want unified endpoint management tightly integrated with Entra ID / Microsoft security stack; supports Android Enterprise dedicated (kiosk) and AOSP enrollment paths. (official Microsoft documentation)
- Workspace ONE / Omnissa and SOTI
  - Broad UEM feature sets and longstanding presence in rugged/frontline device management; may outperform on heterogeneous device OS support and advanced enterprise mobility workflows.
Feature comparison: where Mason appears to excel vs lag behind (based on public info)
- Likely excels
  - Remote debugging/observability workflows purpose-built for Android fleets (X-Ray leveraging adb). (official vendor documentation)
  - Integrated approach to hardware + OS + device console (positioning as “end-to-end”). (official vendor documentation)
- Likely lags / unknowns
  - Publicly documented compliance posture compared with competitors that publish SOC 2/ISO explicitly.
  - Public evidence of mature SSO/SAML/SCIM, audit logs, and enterprise IAM features (not found in accessible docs).
Pricing comparison: value proposition vs alternatives
- Mason
  - Hard to benchmark due to opaque pricing.
  - May pencil out if it reduces device failure rates, field returns, or downtime for mission-critical workflows.
- Esper
  - Easier initial ROI modeling due to published per-device pricing tiers and explicit plan packaging. (official vendor pricing page)
Market share and adoption trends (cite sources)
- Not enough credible public data was found in accessible sources to quantify Mason market share.
When customers choose competitors instead (and why)
- Intune / Workspace ONE
  - When the organization wants one UEM across laptops + mobile + identity/access policies and already owns the licensing.
- Esper
  - When procurement requires visible compliance attestations and predictable per-device costs, and the fleet is primarily Android.
- SOTI
  - When rugged/frontline device workflows (barcode enrollment, OEM tooling) and massive scale are central.

Aspect

Mason (bymason.com)

Esper

Microsoft Intune

Starting Price

Not public (custom quote likely) (public product review pages)

Published per-device pricing available from the vendor (Genesis tier) (official vendor pricing page)

Not public as “per device MDM” in the same way (bundled via Microsoft licensing; varies by plan/tenant)

Best For

Purpose-built Android device fleets needing integrated hardware + OS control + remote debugging/observability

Dedicated Android/AOSP fleets where per-device SaaS pricing + compliance posture are key

Organizations already standardized on Microsoft ecosystem needing broad endpoint management across users/devices

Key Strength

Deep device-level debugging via X-Ray (remote view/control + logs), integrated into CLI/APIs/Controller (official vendor documentation)

Transparent pricing tiers and published security/compliance claims (SOC 2 Type 2, ISO 27001, PCI DSS) (official vendor pricing and compliance pages)

Broad enterprise enrollment and Android kiosk/dedicated device management capabilities (official Microsoft documentation)

Key Weakness

Limited public third-party reviews and unclear publicly posted security certifications

Hardware/OS integration may be less “single-vendor” end-to-end than Mason’s positioning

Community discussions frequently cite kiosk edge cases and complexity; Android “production appliance” needs can be tricky outside basic kiosk patterns (anecdotally) (community forum discussions)