ReefMind in July 2026: what we measured and what it means for your tank

Hi ReefMind community,

This is the July report. Once a month I want to show you what ReefMind actually did — not a highlight reel, but the real counts, the windows they cover, and what they mean for the tank in your living room.

July was our busiest month so far. On July 1 ReefMind handled about 363,000 requests. On July 31 it handled more than 1.17 million — over three times as much by the end of the month. Behind those requests are reef tanks checking in around the clock, keepers reviewing trends, Collectors syncing readings, and Captain Chris working through what a tank is doing.

The part that matters is not that we got busier. It is that the service kept turning controller data, photos, and hand-entered observations into clearer, more useful information while that growth was happening.

July at a glance

• 20.1Mrequests handled
• 629,891tank readings recorded
• 337tanks reporting readings
• 138new accounts
• 4,930image analyses
• 805weekly summaries sent
• 72Collectors online, as of the August 2, 2026 snapshot

A clearer picture of what is happening

ReefMind recorded 629,891 readings in July, and 337 tanks reported readings during the month — that figure means tanks that sent readings in July, not every tank that has ever been created. A continuously connected controller can produce thousands of readings on its own; a tank you track by hand may produce a handful. Both are valid. The job is to keep that history useful, to tell fresh information from stale information, and to help you see change over time instead of reacting to one isolated number.

Monitoring without handing us your equipment

The Collector runs on a Raspberry Pi or a Docker system on your own network. It reads supported equipment locally, holds readings if your internet drops, and catches up when the connection comes back. Connecting a Collector does not automatically give ReefMind control of your equipment. Monitoring is read-only by default, and any supported control path is separate, opt-in, bounded, and protected by device-specific safeguards.

What Captain Chris did

Captain Chris runs on Google Gemini through Vertex AI. In July he supported tank analysis, chat, camera analysis, weekly summaries, coral analysis, dosing intelligence, translation, and other reef-specific work. Before he answers, ReefMind gathers the relevant evidence from your tank, runs deterministic checks for the calculations and the rules, validates the response, and rejects results that do not hold up. If the model is unavailable, the system fails safely instead of inventing an answer.

Across the 27 days of July we still have telemetry for, Captain Chris and related features made 22,997 measured AI calls and processed 127.9 million tokens. Of those calls, 4,930 included images. The measured AI-call failure rate was 0.57%. Numbers like that describe the work behind a short answer; the goal stays simple, which is useful guidance grounded in your tank’s own data.

Photos that help without becoming an endless archive

ReefMind finished July holding 6.68 GB of photos, up 4.04 GB over the month. Live camera snapshots rotate out instead of piling up forever — the snapshot storage actually got smaller during July. That keeps camera analysis useful while we hold on to less than we otherwise would.

What we worked on

Freshness and confidence. More work on telling a live reading from an old one, so an old value is not quietly presented as current. This matters more than another chart: you need to know whether the number in front of you reflects the tank right now.

Collectors and integrations. Much of July went into the hard seam between real equipment and software — controller identity, dosing channels, device mappings, reconnect behavior, and Collectors that temporarily go offline. Every reef setup is different, so these fixes usually start with someone saying “this does not match what my controller shows.”

Captain Chris and weekly summaries. Tank summaries became more useful, dosing and correlation work continued, and we moved our AI models forward while keeping everyone’s traffic flowing. Identical requests are cached and simultaneous requests for the same analysis are combined, so nobody waits on duplicate work.

Small releases instead of big ones. ReefMind merged 398 pull requests and completed 377 production deployments in July, and automated checks ran 1,835 times; changes that failed those checks were stopped before release. That pace is not a scoreboard, it is a choice. Small, reversible releases mean a problem you report can be corrected more quickly without waiting for a large, risky launch.

How these numbers were made

Your data stays separated by account from collection through storage and display, and every Collector has credentials separate from your personal login. The aggregate figures here were produced by counting operational records. No customer names, emails, account identifiers, tank identifiers, Collector identifiers, private photos, or photo locations are included in them.

We also did not fill measurement gaps with guesses. The AI figures cover 27 of July’s 31 days, because older application logs had already expired when this report was put together. We can measure total service traffic but not the Collector-only share accurately, so there is no Collector upload number here — a made-up one would be worse than none. And the 72 Collectors online is an August 2, 2026 snapshot rather than a July total.

Where August attention goes

• Make controller and dosing integrations more consistent across real-world setups.
• Improve how ReefMind detects and explains Collectors that go quiet.
• Close measurement gaps so future reports can be even clearer.
• Keep improving data freshness, Captain Chris, camera analysis, and weekly summaries without weakening privacy or equipment safeguards.

A community-built reef tool

ReefMind added 138 accounts in July, bringing the total to 454, and 157 reefers are now part of the Captain Chris Crew. The Crew is a community and a status — not an affiliate or recruiting program.

The most valuable improvements still start with you. A Collector that drops overnight, a dosing channel that appears under the wrong name, a dashboard value that does not match the controller, or advice that does not fit the tank: these reports show us where real reef systems differ from the setups we can reproduce ourselves.

If something looks wrong, please tell us in Discord. Specific examples get read, investigated, and turned into better monitoring for everyone.

Thank you for trusting ReefMind with your reef.

Brett Miller
Founder, ReefMind

Report a bug or ask a question in the ReefMind Discord:
https://discord.gg/Mz6AMz9ZKa

Report window: July 1–31, 2026 UTC. Collector count is an August 2, 2026 snapshot. AI figures cover 27 of 31 days.