Ingest from PLCs, sensors, SCADA, and energy meters. Transform at the edge. Push to SAP, cloud, historian, warehouse, or observability stack. A scalable platform architecture — resilient, efficient, DMZ-native. Your network policy, your data.
Connectors — ingest from shop floor
Egress — push to enterprise / cloud
Built on open standards — ISA-95 UNS event bus, MQTT, OPC-UA. Audit + correlation via fasten (GitHub), our open-source audit SDK — every state change is auditable and immutable: who did what, when, where, why, and how. New blocks ship on demand — not a platform rewrite. No proprietary protocols, no vendor lock-in.
Data queues locally at the edge, encrypted. Syncs automatically on recovery — nothing lost, no manual intervention, no data gaps in your reports.
Processing happens at the source. Only refined, approved data leaves your network — your sensors never talk to the cloud directly. You control what moves and when.
Rules, aggregations, FFT, and alerts all run on the edge node. Cloud gets answers, not noise. Less bandwidth, faster response, lower cost.
The engineers building EdgeBits have spent 7+ years shipping industrial IoT software — contributing to open-source projects, building OT protocol integrations, and deploying systems in real factory environments. Deep familiarity with what actually breaks on the shop floor.
Bridges Modbus, OPC-UA, EtherNet/IP, S7, Sparkplug B on the OT side to SAP RFC/OData, REST, MQTT, and warehouses on the IT side. Works with ABB, Schneider Electric, Siemens, and Allen-Bradley equipment out of the box — no custom integration projects.
Outbound HTTPS only. No inbound ports, no VPN concentrators, no firewall exceptions per site. Edge-local buffer survives internet drops, syncs on recovery. The architecture plant IT approves without a review cycle.
Each can be deployed and sold independently. Start with Edge Node, add Manager and Analytics as you scale.
On-premise data processing engine. Ingests from PLCs, runs pipelines, evaluates rules, fires actions, egresses to cloud or ERP. Works standalone or managed.
Factory Floor · Per-Node LicenseThe control plane. Register nodes, build ISA-95 topology, deploy pipeline templates to your entire fleet in one click, monitor health across every site. No VPN. SaaS or self-hosted.
Cloud or On-Prem · SaaSThe data plane. OEE per line, tag explorer, data quality monitor — plus SAP S/4HANA correlation: cross-reference your machine data with production orders, cost centers, and quality specs. For most manufacturers, no separate historian needed.
Cloud or On-Prem · Add-OnEdgeBits runs entirely behind your DMZ. Every node polls Edge Manager outbound over HTTPS. One dashboard, every site, no VPN concentrators, no firewall exceptions.
EdgeBits publishes every reading to a Unified Namespace — an MQTT topic hierarchy shaped by ISA-95. The hierarchy is the routing: site, area, line, device, tag. Self-describing, wildcard-subscribable, consumer-agnostic.
uns/gurugram/area-a/line-1/plc-01/temperature
Any service — pipeline, event engine, egress, historian — subscribes by topic pattern. Add a consumer without changing any producer.
From shop floor data capture to boardroom dashboards — one platform.
OEE tracking, cycle analysis, downtime classification — read directly from PLCs and CNC machines. Real-time visibility into every production line.
PLC → Edge → DashboardMonitor energy meters via Modbus, build per-line and per-shift consumption dashboards, and close the loop back to controls. Sustainable automation with BEE/PAT compliance reporting out of the box.
Meters → Aggregate → ReportContinuous monitoring of temperature, humidity, pressure for GMP environments. Immutable audit trails for pharma, food, and auto industries.
Sensors → Validate → AuditPush production counts, material consumption, and quality data to SAP, Oracle, or Tally. Automate the shop-floor-to-ERP bridge in real time.
Edge → SAP RFC → ERPVibration FFT, motor current analysis, bearing temperature trending — all computed on the edge. Works with ABB drives, Schneider Electric motors, and any sensor on Modbus or OPC-UA. Get alerts before the machine goes down.
Ingest → Analyze → AlertYour existing PLCs, energy meters, and machines connect without replacement. EdgeBits reads what's already there — no rip-and-replace, no rewiring, no production downtime.
Legacy Equipment → Live Data → InsightsStart with a single PLC on one line. Deploy fleet-wide across multiple sites without re-architecture. Edge Manager handles topology, config, and deployments from one dashboard.
Pilot → Plant → FleetFrom PLC protocols to cloud sync — one platform, any deployment model.
Modbus TCP/RTU, OPC-UA, EtherNet/IP (CIP), MQTT, IEC 60870-5-104, Siemens S7, REST/HTTP — catalog grows on demand.
Drag-and-drop ingest, transform, and egress nodes. Build data flows visually — no code required. Works on any device with a browser.
Behind corporate DMZ, on air-gapped intranet, or in Docker/K8s. Adapts to your IT policy — not the other way around.
OEE per line, tag explorer, data quality monitor. Correlate machine data with SAP S/4HANA — production orders, cost centers, quality specs. For most manufacturers, Edge Analytics replaces a standalone historian. No inbound access to the plant. Also pushes to Grafana or Power BI via REST egress.
Central dashboard for fleet management. Remote deploy pipelines, push config, monitor health across multi-site fleets — without VPN to any site. SaaS or self-hosted.
Push production data to SAP via RFC/OData, Oracle/Dynamics via REST, or legacy ERPs via batch reports. Close the shop-floor-to-ERP gap in real time.
Every connector, function, rule, action, and egress is a building block in a versioned catalog. Need a protocol that's not listed today? It ships as a new block — not a platform rewrite. That's the architecture, not a roadmap promise.
Catalog grows continuously. New blocks publish from our roadmap, but priorities follow customer pull — if a specific connector or egress is on your critical path, tell us.
Not another cloud product that ignores your network policy.
Works behind your factory firewall — no IT changes needed.
Outbound-only, TLS-secured and encrypted connections. No inbound ports, no VPN concentrators. Works behind strict corporate firewalls and proxy servers.
Every connection is certificate-verified, not just password-protected.
Mutual TLS on every connection. Device identity verified via certificates — not just passwords. Supports custom CA and IP-based SANs for private networks.
Data processed and stored at the edge. Only aggregated, approved data syncs to cloud. Full audit log of what leaves your network, when, and where.
Runs fully standalone on intranet with no cloud dependency. When internet drops, the edge queues data locally, encrypted. Syncs automatically when connectivity returns.
GMP-compliant audit trails, immutable config versioning, role-based access control. Built for pharma, food, auto — where compliance isn't optional.
Four roles — viewer, operator, engineer, admin — with field-level permissions. Every config change tracked with who, when, and from where.
From factory floor to live dashboard in under an hour.
Deploy on bare-metal Linux, in Docker, or on Kubernetes. Enter a one-time claim code — the device registers itself via outbound HTTPS. No firewall changes, no IT escalation.
Your IT installs it once. You manage everything from a browser.
$ curl -fsSL https://get.edgebits.io | sh
$ edgebits onboard --claim EBX-4F7A-9K2M
✓ Registered as edge-gurugram-01
$ docker run -d --name edgebits \
-e CLAIM_CODE=EBX-4F7A-9K2M \
-v /data/edgebits:/data \
edgebits/edge:latest
$ helm repo add edgebits https://charts.edgebits.io
$ helm install edge edgebits/edge \
--set claimCode=EBX-4F7A-9K2M
Open the edge dashboard. Drag ingest, transform, and egress nodes onto the canvas. Configure each node with auto-generated forms — validation, hints, and dependency checks built in.
Edge polls Edge Manager every 30 seconds. Push deployments, pull telemetry, manage config — all through Edge Manager. On-demand WSS tunnel for live debugging when you need it.
Indian manufacturing is at an inflection point. Factories have PLCs and SCADA — but the data stays trapped on the shop floor.
Read ArticleTag discovery, edge transformation, cloud egress, and remote monitoring — the complete data journey in four steps.
Read Article90% less cloud bandwidth, zero VPN licenses, offline resilience, and faster SAP integration — the ROI case for edge.
Read Article4.0 connected the machine. 5.0 connects the human. Here's how your edge infrastructure evolves — without ripping and replacing.
Read ArticleSAP wants real-time data. The plant manager won't open firewall ports. Here's the architecture that satisfies both.
Read ArticleYour factory has legacy PLCs and manual data entry. Here's how to turn it into a connected operation — without ripping anything out.
Read ArticleNo per-tag fees. No data volume charges. Pay per edge node.
Built-in cross-site OEE dashboards, energy monitoring, predictive maintenance, and SAP-enriched reports. Also connects to Grafana, Power BI, or any BI tool via REST. Add-on subscription — works with any plan.
All prices excl. taxes. Annual contracts. Proof-of-value on a single node before you commit.
Customer references shared under NDA during a demo — not posted publicly. Until then, the heritage is verifiable.
Core team members contributed to Fledge IoT under the Linux Foundation Edge umbrella — a project that processes sensor data from industrial equipment worldwide. That work built deep familiarity with OT protocols, brownfield environments, and what ERP systems actually need from the shop floor.
Open-source industrial IoTMQTT for the event bus. ISA-95 for the topic hierarchy. OPC-UA, Modbus, S7, Sparkplug B for the protocols. Standards plant IT teams already understand and trust — no proprietary protocol, no vendor-only file format, no closed catalog.
MQTT · ISA-95 · OPC-UA · Sparkplug BActive engagements across auto parts, pharma, steel, textile, and FMCG manufacturers in North India. If your plant runs Siemens, ABB, Schneider Electric, or Allen-Bradley equipment and your data still lives in spreadsheets — that's exactly who we're talking to. Customer references and pilot data shared under NDA during a demo.
Talk to us →Real questions from plant managers and IT heads — answered without the jargon.
It runs inside your plant network. No cloud dependency for core operation — data ingest, pipelines, alerts, and local buffering all work without internet. If you want to push data to Azure IoT Hub, AWS IoT Core, SAP, or a BI tool, you configure that as optional outbound egress. Nothing phones home unless you tell it to.
Nothing gets replaced. EdgeBits connects to your existing equipment in read-only mode using the protocols it already speaks — Modbus, OPC-UA, S7. Your operators keep using the same SCADA screens. Your PLCs keep running the same programs. EdgeBits adds a data layer on top without touching the control layer.
The only thing you need is a Linux box to run the Edge Node software. If there is already a Linux server or industrial PC in your OT network, use that. If not, a Raspberry Pi 4 (~₹6,000) or a small industrial PC is all it takes.
No inbound ports. EdgeBits polls outbound from the plant to your cloud or central manager — same direction as email or Windows Update. Plant IT teams routinely block inbound connections into OT networks. EdgeBits is designed around that constraint: nothing calls into the plant, everything calls out.
Ingest from shop floor: Modbus TCP/RTU, OPC-UA, Siemens S7, EtherNet/IP, MQTT, REST/HTTP, IEC 60870-5-104. Energy meters, PLCs, SCADA, IoT sensors — if it has a network port, there is a connector for it.
Push to enterprise/cloud: SAP RFC & OData, Sparkplug B, AVEVA PI, REST, MQTT, Grafana, Power BI via REST egress. New connectors are building blocks — the catalog grows without platform changes.
Three practical differences:
Your OT (operational technology) is your control layer — PLCs, SCADA, energy meters, sensors. Your IT is your business layer — SAP, Power BI, ERP, cloud. Right now they do not talk. Production data enters SAP manually, hours after the shift ends. Energy usage shows up on the monthly bill, not today's dashboard.
EdgeBits bridges that gap automatically. It reads from your control systems and delivers structured data to your business systems, in real time — no manual entry, no data delays, no separate teams maintaining separate systems.
In one sentence: your PLCs speak to EdgeBits, EdgeBits speaks to SAP — nothing else changes.
No. EdgeBits is designed to be deployed by your in-house IT or OT team. Install the Edge Node on a Linux box, connect to one Modbus meter, build a pipeline in the browser-based editor — you are live in an afternoon. No certified partner required, no weeks of configuration, no large SI engagement before you see data.
Edge Manager is the control plane. Your IT/OT team uses it — register nodes, manage ISA-95 topology, deploy pipelines to 50 sites at once, monitor fleet health. It does not produce business insights.
Edge Analytics is the data plane. Your plant manager and operations head use it — OEE per line, tag explorer across all sites, data quality monitor, and reports. Edge Nodes push data outbound via REST egress into Analytics' own time-series database. No inbound access to the plant required.
SAP S/4HANA correlation: Edge Analytics cross-references your machine data with SAP production orders, cost centers, and quality specs. Cost per unit, yield vs plan, energy per batch — in one place, not assembled manually in Excel.
Do you need a historian? For most manufacturers, no. Edge Analytics stores raw data for 90 days, 15-minute aggregates for a year, and hourly aggregates for 3 years. AVEVA PI and FactoryTalk Historian are the right choice for highly regulated environments (pharma, nuclear) that require long raw-data retention and audit trails. For OEE, energy, and operational reporting, Edge Analytics covers it at a fraction of the cost.
One sentence: Edge Manager runs the platform. Edge Analytics tells your business what the machines are doing.
No. EdgeBits is not a SCADA and not a historian replacement. It sits alongside your existing systems — Wonderware, iFIX, Ignition, AVEVA PI — and adds the pipeline layer that moves data to ERP, BI tools, and cloud. Your operators keep using the screens they know. Your control layer stays untouched.
Tell us what you're trying to connect and we'll set up a call. No pitch deck, no pressure — just a conversation about your factory and whether EdgeBits fits.
Or reach us directly at
hello@edgebits.io