MongoDB Logistics United Kingdom

Ceto

Predictive Maintenance · Real-time Analytics

Ceto needed a more scalable and reliable way to process high-frequency vessel sensor data for predictive maritime analytics after its previous platform could not keep up with fleet growth.

Each vessel is equipped with thousands of sensors, each operating at a frequency of 50–100Hz, which translates to 300 to 400MB of raw data per vessel daily.
MongoDB’s Time Series Collections reduced data storage needs from 300MB to 3MB per vessel per day.
Predictive maintenance capabilities saved approximately $20,500 per vessel annually.
This results in approximately 90,000 JSON documents per day, each storing around 100 unique time-series measurements.

Reported impact

Business outcome

Ceto reduced storage needs from 300MB to 3MB per vessel per day, saved about $20,500 per vessel annually through predictive maintenance, and created a platform that can scale to much larger fleets.

  • Cost Reduction
  • Risk Reduction
  • Scalability

Solution

Ceto rebuilt its maritime analytics platform around MongoDB Atlas and Time Series Collections so it could ingest high-frequency vessel telemetry and turn it into predictive maintenance insights at scale. Each vessel emits thousands of sensor signals at 50-100Hz, creating around 300-400MB of raw data per day and about 90,000 JSON documents containing 100 time-series measurements. Ceto configured Atlas clusters to handle that throughput, then used Time Series Collections to compress, store, and query readings efficiently while preserving a single operational platform. Real-time processing on top of those collections lets the company analyze fleet conditions as data arrives, helping it predict failures, lower fuel consumption, and reduce operational risk. The architecture also gives Ceto headroom to expand from a handful of vessels to a much larger connected fleet without rewriting its data model or accepting downtime.

Data flow

Thousands of vessel sensors stream telemetry into MongoDB Atlas, where Time Series Collections compress and store the readings; real-time analytics then process those series to flag likely failures, support maintenance decisions, and feed operational insights back to maritime teams.

Solution architecture

2 components · 1 layer
  1. Storage
    • MongoDB Atlas Provides the scalable cluster layer that Ceto uses to ingest and process fleet telemetry continuously.
    • Time Series Collections Stores and compresses high-frequency vessel sensor readings for real-time predictive analytics.

Architecture clues

  • Ceto expects to grow toward supporting 1,000 vessels and 180 million documents per day.
  • Ceto originally relied on InfluxDB before moving to MongoDB.
  • The initial Atlas setup was accomplished in just a few months.
  • The production system processes thousands of data points per second per vessel.

Evidence from the source

MongoDB’s Time Series Collections reduced data storage needs from 300MB to 3MB per vessel per day.
“MongoDB enabled real-time data processing, allowing Ceto to achieve immediate analysis and actionable insights.”
“The existing data management system simply wasn’t capable of scaling with our rapid growth.”
“We’ve managed to maximize data accessibility and readability while minimizing storage size.”
Transparency Evidence & methodology 100/100 reference value · 82% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. MongoDB

    Ceto customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/ceto
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. Ceto

    Contact

    First-party
    https://ceto.ai/contact

    The contact page states: 'CetoAI is registered in the UK under no 12472339 at Hoults Yard, Mailing Exchange 120, Walker Road, Newcastle Upon Tyne, NE6 2HL, United Kingdom.'

    Source type
    company website
    Supports
    • Region

Date evidence

  • First archived Aug 4, 2024 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 17, 2025 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.