End-of-Life Effective: 31 December 2023

OCEASOFT ThermoServer

OCEASOFT ThermoServer–ThermoClient reached end-of-life on 31 Dec 2023. See the risks of staying and your independent migration path to ATEK.

Book a free migration assessment See the facts

The facts

Affected products

  • ThermoServer–ThermoClient software platform
  • Cobalt 1 / Cobalt 2 legacy 915 MHz data loggers
Manufacturer
OCEASOFT (Dickson)
Status
End-of-Life
Effective
31 December 2023

Sources

Every status on this page is drawn from a public source you can verify yourself:

Why staying on it is a risk

Discontinued monitoring systems put regulated facilities at risk — here is what is at stake.

Support

Platform reached a hard end-of-life — no new development

Dickson set a formal end-of-life of 31 December 2023 for the ThermoServer–ThermoClient / Cobalt 2 platform, and stopped selling new licenses back in 2020. The Windows application receives no further development — every site on it is now running unsupported software of record.

Compliance

Audit exposure under 21 CFR Part 11 / GxP

ThermoServer–ThermoClient was the 21 CFR Part 11 cornerstone of the Cobalt monitoring system. Continuing to rely on a vendor-declared end-of-life platform as your system of record for temperature data is difficult to defend during an FDA or Health Canada inspection, where data integrity and system validation are scrutinized.

Spare parts

Aging Cobalt 1 / Cobalt 2 hardware on the way out

The legacy 915 MHz Cobalt 1 and Cobalt 2 data loggers tied to ThermoServer are being phased out in favor of LoRaWAN-based Cobalt X / ML3 hardware. As the installed base ages, replacement loggers and spares for the discontinued generation become harder to source.

Data continuity

Migration is mandatory — so it should be on your timeline

Because the platform is end-of-life, moving off it is not optional. Doing it under pressure during an incident or a failed audit is the worst time to plan a data migration and re-validation.

Your migration path to ATEK

ATEK replaces the discontinued ThermoServer–ThermoClient platform with a modern, continuously maintained, cloud-native monitoring system — backed by a Canadian-based team, included A2LA-accredited calibration, and all-inclusive per-point pricing. Because migration off ThermoServer is mandatory either way, it is the right moment to evaluate an independent platform rather than defaulting to the vendor's own OCEAView path. We run in parallel with your existing system so compliance coverage never lapses during the cutover.

Modern, maintained platform

Continuously updated, security-patched cloud platform built for 21 CFR Part 11 — not a frozen Windows application at the end of its lifecycle.

Canadian local support

24/7 monitoring specialists with a guaranteed 5-minute live response and bilingual (EN/FR) support — and Canadian data hosting under PIPEDA.

Calibration included

In-house A2LA-accredited calibration with NIST-traceable certificates bundled in — no separate calibration contracts to manage.

All-inclusive pricing

Hardware, platform, calibration, validation and support in one per-monitoring-point rate — no surprise re-platform invoices.

How the migration works

  1. 1

    Inventory & assessment

    We map every ThermoServer monitoring point, alarm rule, and compliance report so nothing is lost in translation.

  2. 2

    Parallel deployment

    ATEK sensors install alongside your ThermoServer–ThermoClient system and run simultaneously through the validation window — continuous documentation, zero gap.

  3. 3

    Validation (IQ/OQ/PQ)

    Included qualification protocols demonstrate the new system meets or exceeds your existing compliance requirements.

  4. 4

    Decommission

    Once ATEK is validated, the end-of-life ThermoServer platform and its aging Cobalt loggers are retired for good.

Understanding the ThermoServer end-of-life

For years, OCEASOFT’s ThermoServer–ThermoClient software was the backbone of the Cobalt continuous monitoring system in pharmacies, laboratories, and life-science facilities tracking temperature and environmental conditions. OCEASOFT was acquired by Dickson in 2019, and the legacy Windows platform has since been wound down.

In 2020, Dickson announced that OCEASOFT would stop selling new licenses of the ThermoClient–ThermoServer solution. It then set a hard cutoff: the ThermoServer–ThermoClient / Cobalt 2 platform reached end-of-life on 31 December 2023. Existing customers could expand their sites and receive legacy loggers through that date, but no further development was pursued on the platform.

For facilities that depend on ThermoServer as a compliance system of record, that is the definition of an obsolete platform that needs to be replaced, not maintained — it was the 21 CFR Part 11 cornerstone of the Cobalt system, and it is now frozen.

Migration is mandatory — so evaluate independently

Dickson’s default migration path moves ThermoServer users onto its current OCEAView solution and newer LoRaWAN-based Cobalt X / ML3 hardware. To be clear, OCEAView and the Smart-Vue line are still actively sold — they are not end-of-life. But the legacy Windows platform and its Cobalt 1 / Cobalt 2 loggers are, and moving off them is no longer optional.

Because you have to migrate anyway, it is the right moment to evaluate a genuinely modern, independently supported system rather than defaulting to the same vendor’s lifecycle. The cost and disruption of a platform change are the same — the difference is whether you land on a platform that fits your compliance, support, and data-residency requirements.

Migrating to ATEK without a compliance gap

ATEK’s approach is built around continuity. We inventory every ThermoServer monitoring point, alarm configuration, and reporting workflow, then deploy ATEK sensors in parallel so both systems capture data simultaneously through the validation window. Included IQ/OQ/PQ documentation demonstrates equivalence or improvement, and only once ATEK is validated is the end-of-life ThermoServer platform decommissioned.

The replacement is all-inclusive: a continuously maintained, 21 CFR Part 11-ready cloud platform with Canadian data hosting under PIPEDA, in-house A2LA-accredited calibration with NIST-traceable certificates, and a Canadian-based team available 24/7 with a five-minute live-response guarantee and bilingual support.

If you are still running OCEASOFT ThermoServer, book a free migration assessment below and we will map your path off it.

Related

Compare ATEK vs OCEASOFT (Dickson)

Related

Biotech & Pharma

Learn more

Hospital Pharmacy

Learn more

Freezer & Refrigerator

Learn more

Book a free migration assessment

We map your current deployment, plan a parallel cutover with continuous compliance coverage, and quote an all-inclusive replacement.

Free assessment of your current deployment

Parallel migration with no compliance gap

Validation documentation (IQ/OQ/PQ) included

Get a rescue quote in 1 day

Tell us how many monitoring points you need to convert and we will price an all-inclusive replacement.

Book a free migration assessment

Frequently Asked Questions

Is OCEASOFT ThermoServer still supported?

No. Dickson set a formal end-of-life of 31 December 2023 for the ThermoServer–ThermoClient / Cobalt 2 platform, and stopped selling new licenses in 2020. It receives no further development and customers are directed to migrate off it.

Does this mean OCEAView and Smart-Vue are also discontinued?

No. Only the legacy Windows-based ThermoServer–ThermoClient platform and its Cobalt 1 / Cobalt 2 generation hardware reached end-of-life. Dickson's current OCEAView solution and the Smart-Vue product line remain actively sold — but if you are migrating anyway, it is worth comparing independent alternatives.

Why is staying on ThermoServer a compliance risk?

ThermoServer–ThermoClient was the 21 CFR Part 11 cornerstone of the Cobalt system, but it is now vendor-declared end-of-life and no longer developed. In a GxP or FDA 21 CFR Part 11 context, an end-of-life system of record is hard to defend during an inspection.

Can ATEK migrate our ThermoServer data and monitoring points without downtime?

Yes. ATEK deploys in parallel with your ThermoServer–ThermoClient system and runs both simultaneously through validation, so compliance documentation is continuous and there is no monitoring gap during the cutover. IQ/OQ/PQ is included.

Get off an end-of-life system before it costs you

Talk to a Canadian-based monitoring specialist about a compliant, locally supported replacement.

Book a free migration assessment View the full EOL registry

This page summarizes the end-of-life status of OCEASOFT ThermoServer based on the publicly available sources cited above, current as of June 2026. Product lifecycles change — if any detail is inaccurate or outdated, please report an inaccuracy and we will review it promptly.