Hardware From Us, Software From You

Most concrete monitoring systems are sold as a closed package: their sensors, their app, their reports, and no straightforward way out. That is a problem if your organisation already runs on something else โ€” a project management platform, an ERP, a quality system, a BI dashboard, or software your own team wrote.

CONTEMP is built the other way around. You can buy the hardware and nothing else. Every reading the loggers collect, and everything the platform calculates from it, can be delivered into your systems automatically: pushed to you the moment it arrives, or served when you ask for it.

No middleware, no exports, no one copying numbers into a spreadsheet. Point CONTEMP at an endpoint of yours, or call ours โ€” and the concrete data your projects generate shows up where your people already look.

Two Ways to Move the Data

Webhooks โ€” real time, pushed to you

You give us a URL of yours; CONTEMP posts to it as things happen on site. Nothing polls, nothing waits for a nightly job.

  • New readings as the loggers upload them.
  • Temperature alarms โ€” minimum, maximum and differential โ€” at the moment the limit is crossed.
  • Pour milestones, including a pour reaching its target strength or maturity.

This is what turns concrete monitoring into a live input to your own workflows: a notification in your own channels, a task created in your own system, a site dashboard that updates itself.

REST API โ€” on demand, pulled by you

When your system would rather ask than listen, the CONTEMP REST API answers. Request what you need, when you need it, and build whatever you like on top of it.

  • Readings from the ambient sensor and the two embedded sensors.
  • Pours โ€” their configuration, their status and their history.
  • Maturity and estimated strength, as calculated from your calibration formula.
  • Loggers and sensors โ€” what is deployed and what state it is in.

The API is documented endpoint by endpoint, so your developers can read it once and get on with the work instead of reverse-engineering responses.

What People Build With It

  • One pane of glass. Concrete temperature and strength beside the rest of your project data, in the system your team already opens every morning.
  • Automatic quality records. Pour data filed into your document or QA system as each pour completes, without anyone remembering to do it.
  • Alerts in your own channels. Route a differential-temperature alarm to the people and places your organisation already uses for urgent notices.
  • Schedule triggers. When a pour reaches target strength, let your own scheduling or workflow tool react to it.
  • Your own analytics. Pull the raw history into your warehouse and look at curing performance across every project, mix and season.

Or Use the CONTEMP Dashboard

Integration is an option, not a requirement, and it is not the fallback either. The CONTEMP dashboard comes with the hardware, carries no per-seat charge, and has just been rebuilt from the ground up: a simpler path from signing in to watching a live pour, guided setup for loggers, sensors, calibration formulas and pours, and AI help built in so you can ask a question in plain language instead of searching a manual.

Plenty of customers run entirely on the dashboard. Plenty run entirely through the API. Using both is common too: the dashboard for the field crew, the API for the systems behind them.

Getting the Documentation

The webhook and API documentation is not published on this site โ€” we send it to you. Contact us and tell us roughly what you want to connect, and we will get the documentation to your team so they can scope the work before you commit to anything.

Already a customer? Ask us for API access on your existing account โ€” the hardware you have deployed does not need to change, and neither does anything your crews are doing today.

The Rest of the Picture

Ready to put concrete data into your own software? Contact us for the API and webhook documentation, or sign in at dashboard.contemp.live to look at the platform first.