FROST-Server

Azure Applications 1 variation

FROST-Server is the reference implementation of the OGC SensorThings API, storing sensor observations in PostgreSQL and serving them over a standards based REST interface.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.

ProductCloudOperating systemVersion
FROST-Server 2.8 on Ubuntu 24.04 LTS Azure Ubuntu 24.04 2.8 View · Guide

Overview

FROST-Server is the Fraunhofer IOSB reference implementation of the OGC SensorThings API, the open standard for managing and sharing Internet of Things sensor data. It models the real world as Things that carry Sensors, each Sensor feeding a Datastream of Observations of an ObservedProperty at a Location, and exposes that model through a clean, queryable REST interface. Clients create, read, update and delete entities with ordinary HTTP requests and navigate between them by following links, while the built in query language lets a caller filter, order, page, expand and aggregate observations without any custom server code.

Every observation is persisted in PostgreSQL with the PostGIS spatial extension, so location aware queries, geospatial filtering and long term historical storage all come from a database engine built for the job. Because it implements a published OGC standard rather than a proprietary API, data recorded through FROST-Server is portable across the growing ecosystem of SensorThings clients, dashboards and analytics tools, which makes it a common backbone for environmental monitoring networks, smart city deployments, industrial telemetry and research data collection.

Why the cloudimg image

cloudimg delivers FROST-Server as a complete appliance with the servlet container, the Java runtime, PostgreSQL with the PostGIS extension and a hardened reverse proxy already installed, tuned and wired together, plus a small sample dataset of Things, Datastreams and Observations in place, so a SensorThings query returns real observation values as soon as first boot finishes. Security is the reason to take this image rather than assemble it yourself. FROST-Server's default is an open, unauthenticated read and write API, which on a public address lets anyone inject or delete your sensor data; this appliance ships with the authentication plugin enabled so that reads stay public while every write is refused unless it carries an administrator credential that is generated uniquely on each instance at first boot and written to a root only file. The database listens only on the loopback interface and requires a per instance scram-sha-256 password that is also minted at first boot, the servlet container listens only on loopback behind a reverse proxy that forwards an explicit allowlist of paths and answers everything else with a not found, and the captured image contains no database password, no service credential and no private key at all before first boot runs. The base is fully patched with unattended security upgrades enabled, the heap and database buffers are sized for the instance you launch, and every deployment is paired with a step by step deploy guide and backed by 24/7 cloudimg support.

Common uses

  • Collect and store IoT sensor observations through the open OGC SensorThings API
  • Back environmental, smart city or industrial monitoring networks with a standards based data store
  • Give applications a queryable REST interface over sensors, datastreams and observations