# Apache IoT and Edge Devices for Small Business

StreamPipes, IoTDB and PLC4X solve different device-data jobs. Compare all seven projects, managed prices, trial limits and realistic operating costs.

Author: J.A. Watte
Published: October 30, 2026
Source: https://jwatte.com/blog/apache-iot-edge-devices-small-business/

---

**StreamPipes is the owner/helper option for a contained device-data trial. IoTDB needs a database operator, and PLC4X plus the other projects belong to the developers who build equipment software. For most small businesses, a managed monitoring product is the first comparison to make.**

The practical starting point is one question about a machine: whether a freezer is warming, when a pump ran, or how long a press stood idle. You need a trustworthy measurement, a way to move it, somewhere to store it and a person who knows what to do with the result. A dashboard is only one part of that chain.

This group includes a visual data tool, a database, industrial communication libraries, embedded operating systems and a file format. We read their official pages on October 29, 2026; we have not installed them for this series. The examples below are illustrations. A trial should use copied measurements or a reviewed read-only connection, with existing equipment controls and safety alarms left in the hands of the people qualified to maintain them.

October 30, 2026 update: added setup time and costs when an AI agent does the typing.

## Every project in this group

All seven catalog entries are here. IoTDB’s current 2.0.11 release replaces the catalog’s older 2.0.10 entry. A registry date identifies directory metadata, while an archive date identifies a distribution file. StreamPipes remains the catalog’s owner/helper choice, with the important stable-documentation limit explained below. None of this group’s entries is currently labeled incubating in the series catalog.

| Project | What it does | Who runs it | Latest release and date |
|---|---|---|---|
| [Apache Celix](https://celix.apache.org) | Builds modular software services for devices and embedded systems. | Your developer | [2.4.0; 2023-09-27 (archive date)](https://downloads.apache.org/celix/celix-2.4.0/) |
| [Apache IoTDB](http://iotdb.apache.org) | Stores and analyzes time series from industrial devices and sensors. | Your IT department or provider | [2.0.11; 2026-09-11](https://github.com/apache/iotdb/releases/tag/v2.0.11) |
| [Apache Mynewt](https://mynewt.apache.org) | Provides operating system components for small connected devices. | Your developer | [1.15.0; 2026-07-21](https://mynewt.apache.org/download/) |
| [Apache Nuttx](https://nuttx.apache.org) | Provides an operating system for embedded devices. | Your developer | [13.1.0; 2026-10-04](https://nuttx.apache.org/download/) |
| [Apache PLC4X](https://plc4x.apache.org/) | Connects software to industrial controllers using different machine protocols. | Your developer | [1.0.0; 2026-09-07](https://github.com/apache/plc4x/releases/tag/v1.0.0) |
| [Apache Streampipes](https://streampipes.apache.org) | Connects industrial data sources to visual processing flows and dashboards. | You, with a capable helper | [0.98.0; 2025-12-15](https://streampipes.apache.org/download/) |
| [Apache TsFile](https://tsfile.apache.org) | Stores time series from industrial devices in a shared file format. | Your developer | [2.5.0; 2026-10-14 (registry record)](https://projects.apache.org/json/foundation/projects.json) |

## StreamPipes: try a useful device dashboard before commissioning it

[StreamPipes](https://streampipes.apache.org/) connects industrial data sources to processing steps and browser dashboards. Its visual interface can help an owner understand what measurements are arriving and what a simple calculation does. A capable helper still has to understand containers, credentials, storage and the boundary between the office network and equipment.

For example, a bakery with two locations and eight employees might want a history of refrigeration temperatures instead of a gap between manual checks. A helper could use copied readings from compatible sensors in a StreamPipes trial and show both locations on one dashboard. On a normal morning, the manager could review whether readings arrived overnight and which sensor needs attention. Our single-host operating floor is $116 to $253/month plus $272 to $817 setup. Sensors, calibration, a gateway, commissioning and a dependable alerting service remain separate. Keep the established food-safety checking procedure throughout the trial.

For example, a ten person machine shop might want to distinguish a stopped machine from a missing measurement. Its integrator could provide a reviewed read-only feed of running and idle states, while StreamPipes displays their history. The owner could review a shift’s idle periods without asking an operator to reconstruct every pause from memory. The same trial-host range applies only if the workload fits the assumed machine. It does not include modifying a controller or integrating a production schedule.

The [download page](https://streampipes.apache.org/download/) identifies 0.98.0, December 15, 2025, and distinguishes stable documentation from upcoming Next documentation. The [stable installation guide](https://streampipes.apache.org/docs/0.98.0/try-installation/) uses the supplied installer and Docker Compose with browser setup. It supports Linux, macOS and Windows 10 or later. Use maintained Docker tools, change initial administrator credentials and keep the trial private.

There is a significant limit in the [stable Docker guide](https://streampipes.apache.org/docs/0.98.0/deploy-docker/): Compose is described for initial tryout and testing, with production guidance pointing toward Kubernetes. The [current deployment guide](https://streampipes.apache.org/docs/configure-operate-deployment/) calls Compose suitable for smaller installations, but that page is labeled Next and unreleased. We do not apply that broader claim to 0.98.0. The run classification here therefore means an owner/helper can evaluate the tool. Production approval needs a provider’s version-specific design and budget.

The stable pages we reviewed give no numerical universal RAM or CPU minimum. We allow one Medium host with 4 vCPU, 8 GiB RAM and 160 GiB disk for this limited evaluation. That is our planning assumption, subject to a test of adapters, storage and retention. Several services sharing one host still share its failure. A configuration that displays sample measurements is not proof that it can monitor the shop reliably for a year.

[Ubidots Professional](https://ubidots.com/pricing/), read October 29 in a browser, is listed at $99/month with 50 devices, ten million dots/month, six months retention and five end users. The published plan also has throughput and alert allowances, including 100 email alerts. We assume ten to twenty devices, two values per device once a minute and two to five end users. The high case produces 20 × 2 × 60 × 24 × 30 = 1,728,000 dots in an assumed 30-day month, within the stated monthly allowance. Stagger transmission and verify burst limits and gateway compatibility; a monthly total does not settle those questions.

The worksheet holds retained backups at 50 GB in both labor cases and assumes 4 to 12 setup hours and 1 to 3 monthly administration hours. Its 36-month column shows what that operating floor would add up to. It is a planning comparison of the simple topology; we do not recommend running an unapproved evaluation deployment as production for three years. A supported production design may cost more.

| StreamPipes evaluation host | Low labor/workload | High labor/workload |
|---|---:|---:|
| Setup labor | $272 | $817 |
| Monthly self hosted | $116 | $253 |
| Self hosted, 36 months | $4,462 | $9,909 |
| Ubidots Professional, monthly | $99 | $99 |
| Ubidots Professional, 36 months | $3,564 | $3,564 |
| Self hosting savings, 36 months | Negative $898 | Negative $6,345 |
| Break even month | Never | Never |

The managed subscription costs less in both cases. Neither figure includes equipment or integration work, and Ubidots still needs a correctly configured data source. Skip self hosting if the business only wants a few dependable measurements and has no reason to maintain the data platform. Start with the stable installation guide, one harmless data source and a written stop condition: missing measurements must be obvious to the person evaluating the system.

## IoTDB: retain device history when a database is justified

[IoTDB](https://iotdb.apache.org/) stores and queries time-stamped measurements. It can be useful behind a custom monitoring application when a business needs history organized around devices and time. It does not supply sensors, calibration or a complete response process when a measurement crosses a threshold.

For example, a twelve person winery might want pump runtime and temperature history available when investigating an interrupted production step. Its provider could load measurements into IoTDB, define retention and provide a query or dashboard around the questions staff actually ask. On a normal day, the production lead could find the relevant period without searching several exported files. Our small single-node allowance is $92 to $229/month plus $272 to $817 setup. Adapters, visualization and machine integration cost extra, and database storage by itself does not prevent a process problem.

For example, a self storage operator with three sites and seven employees might want to compare humidity readings across buildings. A provider could store time-stamped measurements with their sensor identifiers and keep a separate record of calibration or sensor replacements. Staff could distinguish an unusual trend from a sensor that stopped reporting. The same operating range applies to the bounded database case, not the purchase or installation of the sensors. It is also not a promise that stored readings will prevent damage to customers’ property.

The [current download page](https://iotdb.apache.org/Download/) lists 2.0.11, and the [official release](https://github.com/apache/iotdb/releases/tag/v2.0.11) is dated September 11, 2026. Its [release notes](https://downloads.apache.org/iotdb/2.0.11/RELEASE_NOTES.md) raise the minimum JDK to 17 and introduce an Edge package with a combined ConfigNode/DataNode memory allocation of 512 MB. That number describes the process allocation in the package. The operating system, data workload and other services also need resources; a business server cannot be sized from that one number.

The [quick start](https://iotdb.apache.org/UserGuide/latest/QuickStart/QuickStart_apache.html) recommends installing directly on a physical or virtual machine and also offers Docker. The [environment requirements](https://iotdb.apache.org/UserGuide/latest/Deployment-and-Maintenance/Environment-Requirements_apache.html) cover Java and operating-system preparation. Its [resource guidance](https://iotdb.apache.org/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.html) gives a band of two to four CPU cores and 2 to 4 GB memory for up to 100,000 time series at no more than 1 Hz. These are workload-oriented sizing bands that still require testing.

Our example assumes one Small server with 2 vCPU and 4 GiB RAM for a low-impact workload at the lower end of that guidance. [Standalone deployment](https://iotdb.apache.org/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.html) includes ConfigNode and DataNode with replication factor one. One machine has no host-failure tolerance. Important monitoring or a tighter recovery requirement may justify a larger or replicated setup and the cluster labor range instead.

The provider needs to define data types, device identities, retention, credentials and backups. Decide what a missing reading means before an owner relies on a graph. Check whether timestamps come from a device or a receiving service, and account for clock errors. A timestamp that looks precise can still represent the wrong moment if a device buffered measurements while disconnected.

[InfluxDB Cloud Serverless pricing](https://www.influxdata.com/influxdb-pricing/), checked October 29, lists $0.0025/MB written, $0.012 per 100 query executions, $0.002/GB-hour stored and $0.09/GB out, without a minimum commitment. It is a different time-series service, so query and adapter changes need a separate assessment. We exclude the promotional credit.

Our fixed monthly workload assumption is 1,000 MB written, 10,000 queries, an average 10 GB retained including existing history, 730 hours and 1 GB out. Retention keeps that stored volume approximately steady. The monthly arithmetic is 1,000 × $0.0025 + 10,000/100 × $0.012 + 10 × 730 × $0.002 + 1 × $0.09 = $18.39. Both labor cases hold that workload and 50 GB of self hosted backup copies fixed, so the table shows labor uncertainty clearly. The managed service is not an IoTDB-compatible endpoint; application work remains separate on both sides.

| IoTDB single node | Low labor/workload | High labor/workload |
|---|---:|---:|
| Setup labor | $272 | $817 |
| Monthly self hosted | $92 | $229 |
| Self hosted, 36 months | $3,598 | $9,045 |
| InfluxDB usage example, monthly | $18 | $18 |
| InfluxDB usage example, 36 months | $662 | $662 |
| Self hosting savings, 36 months | Negative $2,936 | Negative $8,383 |
| Break even month | Never | Never |

The managed usage example costs less, and self hosting never breaks even at that workload. A need to keep data on a reviewed local system, reuse an existing supported application or use IoTDB-specific functionality can change the decision. Get an implementation quote before treating that requirement as a saving. Start with the official single-node guide, load representative sample measurements and restore a test backup before deciding what uptime commitment is necessary.

## PLC4X: the developer’s connection to a controller

[PLC4X](https://plc4x.apache.org/) provides libraries for communicating with industrial controllers through a common programming interface. This is developer work even though the outcome can be as ordinary as seeing how long a pump ran. A programmer must choose a supported driver, understand the device’s data definitions and handle lost connections. A qualified equipment specialist must approve any connection to a production machine.

For example, an eight person car wash might want a runtime history from an existing compatible pump controller. Its integrator could build a read-only collector using PLC4X and send permitted measurements to the reporting system. On a normal day, the owner could compare recorded runtime with maintenance notes. The operations-only allowance below is $92 to $229/month plus $272 to $817 of service setup. It assumes an existing completed integration; programming, local gateway hardware, connectivity and commissioning need separate quotes.

For example, a fourteen person print shop might want press-state records alongside its job schedule. A developer could read approved status values and record transitions, while the production system continues controlling the press. The supervisor could review the sequence of idle and running periods rather than asking staff to reconstruct it afterward. Use the same operating range only after the completed service has passed a load and reconnect test. A cloud subscription or a generic library cannot identify the correct controller tags without that integration work.

The [download page](https://plc4x.apache.org/plc4x/latest/users/download.html) lists 1.0.0, and the [official release](https://github.com/apache/plc4x/releases/tag/v1.0.0) is dated September 7, 2026. The [Java getting-started guide](https://plc4x.apache.org/plc4x/latest/users/getting-started/plc4j.html) adds API and driver dependencies with Maven, then uses application code to connect and read values. It includes capability checks so the developer can determine what a connection supports. There is no owner installer that produces a finished monitoring system.

The [development-environment guide](https://plc4x.apache.org/plc4x/latest/developers/preparing/index.html) describes Java and Maven prerequisites, but requirements can differ by component and release. Current release material also refers to Java 21 functionality. Have the developer use the selected component’s release requirements rather than assuming an older general Java minimum covers everything. No universal RAM or CPU minimum for a finished application is published in these guides. Our 2 vCPU, 4 GiB allowance concerns a modest existing integration service and must be measured against its actual polling workload.

Keep the controller’s management interface on the reviewed equipment network. A provider can design a local gateway that sends approved measurements outward; a VPS price is not permission to expose a controller to the internet. Agree on polling limits, reconnect behavior and what happens if the reporting service disappears. Keep writes and machine control outside this example. Safety functions require their own qualified design and approval.

[ThingsBoard Cloud pricing](https://thingsboard.io/pricing/), checked October 29 for North America, lists Prototype at $49/month with 50 devices, ten million data points/month and community support. It labels the plan for proofs of concept and minimum viable products. Pilot is $149/month with 100 devices, 100 million points and help-desk support. We use the $49 Prototype plan for a bounded comparison and two to ten devices within its capacity; the appropriate production plan needs its own review.

ThingsBoard’s [Modbus connector](https://thingsboard.io/docs/iot-gateway/config/modbus/) shows another way to buy the outcome for supported equipment without commissioning the same custom PLC4X code. A local gateway, tag mapping and commissioning still exist on that route. There is no claim that the platform replaces every PLC4X driver or that the subscription covers an electrician or integrator.

The worksheet holds 50 GB of backups fixed and prices running an already completed single service with the shared 4 to 12 setup and 1 to 3 monthly administration hours. These hours cover service configuration and operation only. They cannot honestly stand in for an unknown industrial software project. The managed column is a platform subscription slice with common gateway and connection costs excluded; obtain the two implementation quotes before comparing complete totals.

| Existing PLC4X service | Low labor/workload | High labor/workload |
|---|---:|---:|
| Setup labor | $272 | $817 |
| Monthly self hosted | $92 | $229 |
| Self hosted, 36 months | $3,598 | $9,045 |
| ThingsBoard Prototype, monthly | $49 | $49 |
| ThingsBoard Prototype, 36 months | $1,764 | $1,764 |
| Self hosting savings, 36 months | Negative $1,834 | Negative $7,281 |
| Break even month | Never | Never |

Self hosting does not recover its operating cost against that trial subscription. This is not a full project savings claim: the missing development and commissioning quotes can change the decision substantially. Skip a custom collector when the equipment vendor already provides a supported export or monitoring service that meets the need. Start with the official driver documentation and an approved test device or copied data, then have the developer demonstrate a lost connection and safe recovery.

## How we counted the cost

The shared method uses $68.09 per administration hour, an employee compensation estimate from [BLS wages](https://data.bls.gov/oesprofile/?areas=INDUSTRY,STATE,MSA&major_group=150000&measure=01&occupation=151244&year=2025) divided by the [70.0% wages share](https://data.bls.gov/timeseries/CMU2020000000000P). An outside IT provider bills more than this proxy, so get a quote. [DigitalOcean](https://www.digitalocean.com/pricing/droplets) supplies our Small server at $24/month (2 vCPU, 4 GiB RAM, 80 GiB disk), Medium at $48 (4 vCPU, 8 GiB, 160 GiB), and Large at $252 (8 dedicated vCPU, 32 GiB, 100 GiB). These are monthly caps without an annual commitment. [Backblaze B2](https://www.backblaze.com/cloud-storage/pricing) costs $6.95 per decimal TB/month after the first 10 GB free. All were checked October 29, 2026.

Setup = hours × $68.09. Monthly self hosted = server charges + max(0, retained backup GB minus 10) × $0.00695 + administration hours × $68.09. The 36 month total adds setup to 36 monthly bills; savings subtract that total from the alternative. Break even is setup divided by positive monthly savings, rounded up; otherwise it is never. Calculations retain cents internally and display whole dollars.

Our assumptions are 4 to 12 setup hours and 1 to 3 administration hours/month for a bounded single server, or 24 to 60 and 6 to 16 for a small cluster. These exclude application development, migration, training, incidents and on call coverage on both sides. Alternative setup is assumed zero incremental infrastructure labor in these examples. Implementation still takes work. Backup volumes include retained copies. We assume no chargeable backup requests or excess transfer; add them if your usage exceeds the provider allowances. Low and high cases are planning ranges to replace with measured requirements.

## Setup time when Claude or ChatGPT does the typing

We keep the StreamPipes evaluation: one $48 Medium host and 50 GB of backups in both cases. This operating floor is not production approval. Our assumed hours include prompting, review, testing and corrections, not unattended agent runtime. Coding studies do not validate these Apache setup savings. [54]

| StreamPipes: paired planning cases | Low | High |
|---|---:|---:|
| Manual setup hours | 4 | 12 |
| AI setup share; hours | 50%; 2 | 80%; 9.6 |
| Manual administration hours/month | 1 | 3 |
| AI administration share; hours/month | 75%; 0.75 | 100%; 3 |
| Manual total, 36 months | $4,462 | $9,909 |
| Claude Pro subscription total, 36 months | $3,913 | $9,945 |
| ChatGPT Plus subscription total, 36 months | $3,913 | $9,945 |
| API pay per token: Claude Opus 5.5 total, 36 months | $3,727 | $9,859 |
| API pay per token: GPT-6 Astra total, 36 months | $3,750 | $10,030 |
| Opus setup/monthly token charges | $0.764 / $0.382 | $6 / $3 |
| Astra setup/monthly token charges | $1.970 / $0.985 | $15 / $7.50 |

Let S/A be manual setup/monthly hours, q/r the AI shares, H monthly hosting plus backups, and T0/Tm setup/monthly tool charges. We use $68.09/hour and round totals only after calculation.

```text
Manual total = S × $68.09 + 36 × (H + A × $68.09)
AI total = S × q × $68.09 + T0 + 36 × (H + A × r × $68.09 + Tm)
Savings = Manual total minus AI total
```

We budget Claude Pro or ChatGPT Plus at $20 for a separate setup month, then $5/month for 36 operating months: a 25% allocation only when other work uses the rest. Without sharing, add $540. Equal prices do not mean equal allowances; check limits and price extra usage. [42, 43, 44]

Our assumed API budgets are 200,000 to 1,000,000 input and 20,000 to 100,000 output tokens for setup; monthly, 100,000 to 500,000 input and 10,000 to 50,000 output. Low input splits 30% ordinary, 10% short cache writes and 60% reads; high input is uncached. Charges include retries and billed reasoning. The kit shows rates and token arithmetic. [51, 52, 53]

Claude Code or Codex can draft Compose settings and sample-reading tests. Desktop Commander, connected to the server, can install containers, edit configuration and read adapter logs. Claude in Chrome can inspect the provider panel and StreamPipes dashboard while we supervise. [45, 47, 48, 49] ChatGPT’s supported cloud browser is separate from your Chrome session, not a promised equivalent extension. [50]

Our base uses free local Desktop Commander or Codex CLI. Optional Remote Pro adds $20 in setup and $5/month with the same allocation, or $200 overall. [46]

Use a new or staging server, keep secrets out of chat and approve commands or use a restricted sandbox. Watch browser actions; use subscriptions for supervised supported tools and API keys for custom automation. Review every change and test a restore using copied readings, with no controller writes; we still own backups, updates and the decision.

The conclusion stays: Ubidots Professional’s $3,564 over 36 months costs less in every case. Equipment, commissioning and a supported production design remain separate costs. The high case saves no monthly labor; recurring fees can erase setup savings.

## Needs your IT department or a provider

IoTDB is the only IT-tier project in this group and is covered above. Its smallest priced case is one standalone database host with an accepted outage window. Our 1 to 3 monthly administration hours exclude incidents and application work; a replicated installation moves to a separately sized topology and the shared 6 to 16 hour planning range. [Timecho](https://www.timecho.com/product/iotdb-expert-support) publishes commercial IoTDB expert-support services. No fixed support price was verified, so request a quote that identifies versions, response times and recovery responsibilities. InfluxDB’s usage prices above are the managed database alternative.

StreamPipes production operation also needs provider review despite its owner-evaluation classification. Industrial network access, sensor accuracy and machine commissioning are distinct work. A useful quote separates equipment, integration, software hosting and ongoing response so the owner knows which party to call when a graph stops updating.

## Your developer’s toolbox

**Celix** provides a modular C/C++ application framework. You may meet it inside equipment or gateway software. The application developer owns component compatibility and updates; the owner should ask the equipment vendor for its maintenance policy. Its older catalog archive date is a reason to read current project communication before making a new dependency decision.

**Mynewt** supplies operating-system components and services for microcontrollers, including supported-board work. A firmware specialist uses it when building a device. A business buying a finished sensor should ask how firmware fixes are delivered and for how long; installing a different embedded operating system is not ordinary office maintenance.

**NuttX** is a real-time operating system used on embedded hardware. Its supported architectures and system interfaces matter to the device builder. For an owner, the practical questions concern update support, recovery from a failed firmware update and the equipment vendor’s supported lifecycle.

**PLC4X** is discussed at length because a small manufacturer may encounter it in an integrator’s proposal. It remains developer tooling. Keep the connection specification, approved drivers, read permissions and source ownership in the project handover so a future maintainer can understand the collector.

**TsFile** is a file format and supporting APIs for industrial time-series data, including use with IoTDB. You may receive it as an export or meet it inside a vendor’s data pipeline. Ask which reader, version and metadata are required to open exported files years later; an export is useful only if someone can interpret it.

The table’s official homepage links are the starting points for each component. None of these developer entries is a ready-made sensor dashboard that an owner can install and expect to operate independently.

## Risks and support

Review the project notices for [StreamPipes](https://security.apache.org/projects/streampipes/), [IoTDB](https://security.apache.org/projects/iotdb/) and [PLC4X](https://plc4x.apache.org/plc4x/latest/users/security.html), along with [ASF security guidance](https://www.apache.org/security/). Match an advisory to the exact release and driver in use. A quiet feed cannot establish that a system is secure, and a private network does not remove the need for credentials and updates.

Make missing data visible. Test a disconnected sensor, an expired credential and a stopped collector with the people who will read the dashboard. Agree on whether an alert is informational or part of an operational response. Do not let a trial dashboard become the sole temperature alarm or machine safety control through habit. The business should retain its qualified maintenance and safety procedures while evaluating new reporting software.

Back up configuration, pipeline definitions and the underlying persistent data stores using documented procedures. Record external credentials in a protected recovery process. Restore on isolated equipment or sample data, and check timestamps, units and sensor identities afterward. A successful chart rendering does not prove the readings belong to the right freezer or machine.

Before choosing a quiet project, read releases, mailing lists, supported runtimes and the [Apache Attic](https://attic.apache.org/). Ask a vendor which upstream components it uses and who handles a security update. The managed products linked above and Timecho’s support offering are commercial options on their own published terms; a subscription is not automatic support for every self hosted component in your equipment network.

The [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) permits commercial use and modification subject to its conditions, including notices for redistribution. It supplies no warranty and no general permission to use Apache trademarks. Equipment approval, support and response commitments remain separate agreements.

## Download the kit

The [IoT and edge devices kit](/downloads/apache-iot-edge-devices-small-business-kit.md) includes the StreamPipes trial plan, IoTDB provider questions, the PLC4X developer handover, all seven projects and the same operating-cost worksheets.

## Related reading

- [The Apache small business series](/blog/apache-open-source-projects-small-business/).
- [Messaging and event streams](/blog/apache-messaging-event-streaming-small-business/).
- [Databases and operational storage](/blog/apache-databases-small-business/).
- [Monitoring and logging](/blog/apache-monitoring-logging-small-business/).
- [Planning a self hosted server](/blog/self-hosted-ai-server-from-scratch/).

## Fact-check notes and sources

Official pages and the series catalog evidence were read October 29, 2026. Prices are US dollars before tax; billing terms appear with each comparison. We have not installed these projects for this series.

1. [Apache Celix](https://celix.apache.org). Read October 29, 2026, 21:38:41 UTC.
2. [2.4.0; 2023-09-27 (archive date)](https://downloads.apache.org/celix/celix-2.4.0/). Read October 29, 2026, 21:20:13 UTC (catalog observation).
3. [Apache IoTDB](http://iotdb.apache.org). Read October 29, 2026, 21:13:39 UTC (catalog observation).
4. [iotdb release v2.0.11 on GitHub](https://github.com/apache/iotdb/releases/tag/v2.0.11). Read October 29, 2026, 21:40:20 UTC.
5. [Apache Mynewt](https://mynewt.apache.org). Read October 29, 2026, 21:38:38 UTC.
6. [1.15.0; 2026-07-21](https://mynewt.apache.org/download/). Read October 29, 2026, 21:15:07 UTC (catalog observation).
7. [Apache Nuttx](https://nuttx.apache.org). Read October 29, 2026, 21:38:39 UTC.
8. [13.1.0; 2026-10-04](https://nuttx.apache.org/download/). Read October 29, 2026, 21:15:11 UTC (catalog observation).
9. [Apache PLC4X](https://plc4x.apache.org/). Read October 29, 2026, 21:38:34 UTC.
10. [plc4x release v1.0.0 on GitHub](https://github.com/apache/plc4x/releases/tag/v1.0.0). Read October 29, 2026, 21:40:45 UTC.
11. [Apache Streampipes](https://streampipes.apache.org). Read October 29, 2026, 21:13:46 UTC (catalog observation).
12. [0.98.0; 2025-12-15](https://streampipes.apache.org/download/). Read October 29, 2026, 21:37:46 UTC.
13. [Apache TsFile](https://tsfile.apache.org). Read October 29, 2026, 21:38:42 UTC.
14. [2.5.0; 2026-10-14 (registry record)](https://projects.apache.org/json/foundation/projects.json). Read October 29, 2026, 21:00:00 UTC (catalog snapshot).
15. [stable installation guide](https://streampipes.apache.org/docs/0.98.0/try-installation/). Read October 29, 2026, 21:39:04 UTC.
16. [stable Docker guide](https://streampipes.apache.org/docs/0.98.0/deploy-docker/). Read October 29, 2026, 21:39:06 UTC.
17. [current deployment guide](https://streampipes.apache.org/docs/configure-operate-deployment/). Read October 29, 2026, 21:37:44 UTC.
18. [Ubidots Professional](https://ubidots.com/pricing/). Read October 29, 2026, 21:38:55 UTC.
19. [current download page](https://iotdb.apache.org/Download/). Read October 29, 2026, 21:37:47 UTC.
20. [release notes](https://downloads.apache.org/iotdb/2.0.11/RELEASE_NOTES.md). Read October 29, 2026, 21:38:32 UTC.
21. [quick start](https://iotdb.apache.org/UserGuide/latest/QuickStart/QuickStart_apache.html). Read October 29, 2026, 21:39:01 UTC.
22. [environment requirements](https://iotdb.apache.org/UserGuide/latest/Deployment-and-Maintenance/Environment-Requirements_apache.html). Read October 29, 2026, 21:39:08 UTC.
23. [resource guidance](https://iotdb.apache.org/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.html). Read October 29, 2026, 21:39:07 UTC.
24. [Standalone deployment](https://iotdb.apache.org/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.html). Read October 29, 2026, 21:39:10 UTC.
25. [InfluxDB Cloud Serverless pricing](https://www.influxdata.com/influxdb-pricing/). Read October 29, 2026, 21:37:55 UTC.
26. [download page](https://plc4x.apache.org/plc4x/latest/users/download.html). Read October 29, 2026, 21:37:50 UTC.
27. [Java getting-started guide](https://plc4x.apache.org/plc4x/latest/users/getting-started/plc4j.html). Read October 29, 2026, 21:37:52 UTC.
28. [development-environment guide](https://plc4x.apache.org/plc4x/latest/developers/preparing/index.html). Read October 29, 2026, 21:39:13 UTC.
29. [ThingsBoard Cloud pricing](https://thingsboard.io/pricing/). Read October 29, 2026, 21:38:37 UTC.
30. [Modbus connector](https://thingsboard.io/docs/iot-gateway/config/modbus/). Read October 29, 2026, 21:39:55 UTC.
31. [BLS wages](https://data.bls.gov/oesprofile/?areas=INDUSTRY,STATE,MSA&major_group=150000&measure=01&occupation=151244&year=2025). Read October 29, 2026, 21:12:08 UTC.
32. [70.0% wages share](https://data.bls.gov/timeseries/CMU2020000000000P). Read October 29, 2026, 21:17:59 UTC.
33. [DigitalOcean](https://www.digitalocean.com/pricing/droplets). Read October 29, 2026, 21:10:42 UTC.
34. [Backblaze B2](https://www.backblaze.com/cloud-storage/pricing). Read October 29, 2026, 21:10:42 UTC.
35. [Timecho](https://www.timecho.com/product/iotdb-expert-support). Read October 29, 2026, 21:40:57 UTC.
36. [StreamPipes](https://security.apache.org/projects/streampipes/). Read October 29, 2026, 21:40:13 UTC.
37. [IoTDB](https://security.apache.org/projects/iotdb/). Read October 29, 2026, 21:40:15 UTC.
38. [PLC4X](https://plc4x.apache.org/plc4x/latest/users/security.html). Read October 29, 2026, 21:38:35 UTC.
39. [ASF security guidance](https://www.apache.org/security/). Read October 29, 2026, 21:39:57 UTC.
40. [Apache Attic](https://attic.apache.org/). Read October 29, 2026, 22:09:30 UTC.
41. [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0). Read October 29, 2026, 21:39:56 UTC.

42. [Claude plans](https://claude.com/pricing). Read October 29, 2026, 23:31:08 UTC; reused for this update.
43. [ChatGPT plans](https://chatgpt.com/pricing/). Read October 29, 2026, about 23:27 UTC in a regular browser.
44. [Codex plan access](https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan). Read October 29, 2026, 23:31:16 UTC; reused for this update.
45. [Codex CLI](https://developers.openai.com/codex/cli). Read October 29, 2026, 23:32:01 UTC; reused for this update.
46. [Desktop Commander pricing](https://desktopcommander.app/pricing/). Read October 29, 2026, 23:31:08 UTC; reused for this update.
47. [Desktop Commander setup and permissions](https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/main/README.md). Read October 29, 2026, 23:31:41 UTC; reused for this update.
48. [Claude in Chrome](https://support.claude.com/en/articles/12012173-get-started-with-claude-in-chrome). Read October 29, 2026, 23:31:11 UTC; reused for this update.
49. [Chrome permissions](https://support.claude.com/en/articles/12902446-claude-in-chrome-permissions-guide). Read October 29, 2026, 23:31:09 UTC; reused for this update.
50. [ChatGPT cloud browser](https://help.openai.com/en/articles/20001280-using-cloud-browser-in-chatgpt). Read October 29, 2026, 23:32:01 UTC; reused for this update.
51. [Claude API pricing](https://platform.claude.com/docs/en/about-claude/pricing). Read October 29, 2026, 23:31:14 UTC; reused for this update.
52. [OpenAI API pricing](https://developers.openai.com/api/docs/pricing). Read October 29, 2026, 23:31:13 UTC; reused for this update.
53. [OpenAI prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching). Read October 29, 2026, 23:32:00 UTC; reused for this update.
54. [METR coding study limitations](https://metr.org/blog/2026-02-24-uplift-update/). Read October 29, 2026, 23:31:09 UTC; reused for this update.

*Apache, the Apache feather logo and the Apache project names are trademarks of The Apache Software Foundation. This site is not affiliated with or endorsed by the ASF. Other product names are used for identification only.*


---

Canonical HTML: https://jwatte.com/blog/apache-iot-edge-devices-small-business/
RSS: https://jwatte.com/feed.xml
JSON Feed: https://jwatte.com/feed.json
Hero image: https://jwatte.com/images/apache-iot-edge-devices-small-business.webp