HTTP + MQTT telemetry workbench

Wire up a sensor. See what it is doing.

Devicecamp is the quick path from a board on your desk to live values and history. Send plain JSON; the useful dashboard assembles itself.

HTTP ingestion online

Direct access

Open a device without signing in

The secret stays in this browser tab and is never added to the URL.

One small contract

Your firmware sends numbers. Devicecamp handles the plumbing.

  1. 01Create a device
  2. 02Publish JSON
  3. 03Inspect live metrics
telemetry.shcurl -X POST https://api.devicecamp.app/v1/devices/…/telemetry \
  -H "Authorization: Bearer dc_dev_…" \
  -H "Content-Type: application/json" \
  -d '{"temperature":22.4,"humidity":51}'
Common questions

Before you connect a device.

What hardware works with Devicecamp?

Anything that can send HTTPS or MQTT messages: ESP32 boards, Raspberry Pi, microcontrollers with a network module, gateways and existing services.

Do I need to define a schema first?

No. Send a JSON object and Devicecamp discovers numeric, boolean and text metrics. You can rename them, add units and choose how each one is displayed later.

How quickly will data appear?

New telemetry normally reaches the workbench in seconds. HTTP and MQTT use the same storage and visualization path.

Can I use several readings in one chart?

Yes. Overlay related metrics in one chart or split them into synchronized charts, then save that view for the device.

How are device credentials protected?

Every device gets its own revocable credential. Traffic uses TLS, workspace access is isolated and secrets are only shown when they are created or rotated.

Can I start for free?

Yes. Free includes five devices, 30 days of raw history, three alert rules and Telegram notifications. No card is required.