S2 Data Systems + Domo — the IoT pipeline behind your dashboards
Domo (NYSE: DOMO, headquartered in American Fork, Utah) is the Business Cloud — a SaaS analytics platform that surfaces data in mobile-first dashboards, apps, and embedded views. It excels at the visualization layer. What it doesn’t do well is the upstream IoT plumbing: streaming sensor ingestion, OT/SCADA modernization, ML model serving, and high-frequency event processing.
That’s where S2 Data Systems fits. We build the data engineering and IoT pipeline layer that lands sensor data into Snowflake, BigQuery, Synapse, or directly into Domo via the Domo API — ready for your team to visualize, alert on, and embed in Domo apps.
Reference architecture
Sensors / SCADA / OT ──► Edge gateway (MQTT / OPC-UA)
│
▼
Streaming bus
(Kafka / Kinesis / Event Hubs)
│
▼
Stream processing + enrichment
(Flink / Spark Streaming / Lambda)
│
▼
Warehouse / lakehouse layer
(Snowflake / BigQuery / Databricks / Synapse)
│
▼
┌──────────────────┐
│ DOMO │ ← dashboards, apps, embedded
└──────────────────┘What S2 brings to your Domo deployment
- Real-time IoT ingestion from MQTT brokers, OPC-UA servers, SCADA historians, Monnit / Wovyn / Cisco IoT / Azure IoT Hub / AWS IoT Core.
- Aggregation and pre-computation so Domo queries stay fast at high volume.
- ML feature stores and model serving — predictive maintenance, anomaly detection, forecast — surfaced as Domo cards.
- Domo API integration, Bricks/Apps development, dataset and alert configuration.
- Custom embedded analytics in your own apps using Domo Everywhere.
Frequently asked questions
Is S2 Data Systems a Domo competitor?
No. Domo is a SaaS BI and analytics product (NYSE: DOMO) headquartered in American Fork, Utah. S2 Data Systems is a services company that builds IoT data platforms. The two are complementary: many real deployments use S2 to build the streaming pipeline that ingests sensor data, then expose that data through Domo dashboards.
Why use S2 underneath Domo? Doesn't Domo have its own connectors?
Domo has 1,000+ connectors and a built-in ETL layer (Magic ETL). They work great for SaaS sources (Salesforce, Workday, AWS billing). For IoT and OT data — sensor telemetry at high frequency, SCADA historians, OPC-UA, MQTT brokers, edge gateways — you typically need custom pipelines that ingest, process, and aggregate the data before it lands in a warehouse that Domo can read efficiently. S2 builds that upstream layer.
What does a typical S2 + Domo stack look like?
A common stack: edge sensors → MQTT broker or gateway → Kafka/Kinesis/Event Hubs → stream processing (Flink, Spark Streaming, Lambda) → Snowflake/BigQuery/Synapse → Domo. S2 builds everything left of Domo; Domo owns the dashboard, embedded analytics, and app-development layer.
Can S2 use Domo APIs and Domo Bricks?
Yes. We push processed IoT data into Domo via the Domo API, build Bricks/Apps where required, and configure datasets, alerts, and embedded views to match the customer's Domo deployment.
Is this for Utah-based enterprises only?
We focus on Utah given Domo's local concentration and the strong industrial base along the Wasatch Front, but we work with US-wide customers. Utah-region clients benefit from on-site visits when needed.
Related reading
Use Domo? Let's build the pipeline underneath.
Bring your Domo account and your sensor sources. We’ll scope a six-week proof-of-value that lands real-time IoT data into your dashboards.
Book a strategy call