What this preview recorded
The original release note marked a shift from public educational pages toward account-scoped monitoring. Its durable ideas were simple: a user could save places that matter to them, see local weather and risk context, inspect why a signal was elevated, and return later to see what changed. Those ideas remain useful product history. They are not proof that every card, data provider, prediction horizon, or subscription path is currently available. Product interfaces can exist before the operational evidence behind a particular card is ready, so this page now separates design intent from verified runtime state. Source: GeoGridIQ
Archiving is the clearest treatment because a dated preview should not silently evolve into a permanent availability promise. The original publication date is preserved, the review date is visible, and readers are directed to current product surfaces. This approach keeps the release history useful to users and search systems while preventing an old announcement from outranking the current Pricing or coverage state. It also means screenshots and example workflows on this page should be read as dated product concepts rather than evidence of an active forecast at a particular location. Source: GeoGridIQ
What personalized monitoring means
A saved location is an account-owned monitoring record, not a public asset record or a guarantee of service. The intended workflow is to create and verify an account, save an eligible location, review the dated context available for that place, inspect the stated drivers and limitations, and monitor later updates. Server-side checks enforce both ownership and plan limits. That matters because hiding a button in the browser is not an access-control boundary: the server must reject attempts to read or modify another account's locations or to exceed the canonical plan allowance. Source: GeoGridIQ
The card families should be interpreted separately. Weather context reports forecast or observed environmental conditions from its stated source and time. Vegetation context describes a dated screening signal with quality limits. Observed outages report provider events. Outage-risk cards require their own region, horizon, artifact, batch, and freshness checks. Bringing those cards together can reduce navigation, but it does not merge their provenance or turn a missing signal into a zero-risk statement. Each card needs its own timestamp and unavailable state. Source: GeoGridIQ
The reviewed entitlement matrix
As reviewed in the server-side plan source on July 26, 2026, Free defines one saved location, one weather widget, one alert widget, and no vegetation, prediction, or critical-infrastructure widget allowance. Pro defines five saved locations, five weather and alert widgets, three vegetation widgets, three prediction widgets, and one critical-infrastructure widget. Business defines ten saved locations and ten for each of those widget categories. Enterprise uses custom numeric limits rather than an 'unlimited' promise. These values describe entitlement code, not a claim that every data product is available in every region. Source: GeoGridIQ
Business code also contains multi-location, reporting, API-preview, and crew-staging flags. Those flags should be described as plan-gated previews. Crew staging is deterministic planning support rather than autonomous dispatch, route optimization, or a proven arrival-time system. API endpoints are account-scoped and preview-labelled rather than a generally available service with a production service-level commitment. A coded entitlement answers who may use a feature after it is ready; it does not answer whether its dependencies, data, or commercial activation have passed readiness checks. Source: GeoGridIQ
Evidence: Geogridiq Test Output
Reviewed plan limits
Show the server-enforced July 26 entitlement values without implying commercial or data availability.
Scroll horizontally or use the arrow keys to compare every column.
| Plan | Saved locations | Weather / alerts | Vegetation / prediction / CI |
|---|---|---|---|
| Free | 1 | 1 / 1 | 0 / 0 / 0 |
| Pro | 5 | 5 / 5 | 3 / 3 / 1 |
| Business | 10 | 10 / 10 | 10 / 10 / 10 |
| Enterprise | Custom | Custom | Custom |
Coded entitlements reviewed July 26, 2026; they do not establish purchasing or forecast availability.
Figure source: GeoGridIQ
Billing availability is a separate gate
GeoGridIQ checks server-side billing configuration before it offers a paid checkout action. In the July 26 runtime audit, that readiness check returned false. This page therefore does not invite readers to purchase Pro or Business as though checkout were available. Pricing is the current source of truth because its action state is derived from the same readiness check. Plan descriptions can remain visible for comparison even while purchase controls are unavailable, provided the distinction is unmistakable. Sources: GeoGridIQ GeoGridIQ
The billing implementation also separates opening Checkout from receiving access. Paid entitlement begins only after GeoGridIQ verifies the relevant managed invoice outcome. That fail-closed sequence is important, but it is still not evidence that a production subscription can be bought from this archived page. Readers should check Pricing at the time of use. Product documentation should not predict when configuration will change unless an externally committed date exists. Source: GeoGridIQ
A dashboard surface is not proof of forecast availability
Prediction entitlement and prediction trust answer different questions. Quebec's 6-, 24-, 72-, and 168-hour model artifacts are suspended pending leakage-safe retraining, so public Quebec forecast output is unavailable. Previously stored rows may remain for audit, but they are not current forecasts. The safe state is unavailable rather than a model-looking fallback. A user who is allowed to open a prediction card must still see an honest unavailable state when the regional and horizon gates fail. Source: GeoGridIQ
The British Columbia 24-hour artifact passes exact identity and local-cache verification, but the July 26 audit found no current forecast batch. Its registry contained no public performance metrics or calibration rows for this claim. Artifact integrity is necessary, but batch generation and freshness must also pass before a current forecast can be shown. This is why the product status flow has separate gates for entitlement, billing, artifact identity, regional safety, batch existence, and freshness. Source: GeoGridIQ
Evidence: Conceptual Illustration
Five gates, five different questions
Keep account entitlement, checkout, artifact safety, current batch, and freshness separate.
- 1 Entitlement
- May this account open the feature?
- 2 Billing readiness
- Can a paid plan be purchased now?
- 3 Artifact trust
- Is the exact region/horizon artifact safe?
- 4 Current batch
- Was an eligible forecast generated?
- 5 Freshness
- Is that batch still valid for display?
Keep account entitlement, checkout, artifact safety, current batch, and freshness separate.
What this preview does not promise
The preview does not guarantee that an outage will occur, that a saved location is covered by a trusted prediction, that every provider is fresh, or that a card represents a field-verified asset condition. It does not promise outage prevention, restoration timing, crew dispatch, or financial savings. Weather forecasts can change, vegetation data can be cloudy or stale, provider events can be incomplete, and local equipment conditions may not be present in public data. The appropriate use is decision support with visible provenance and limitations, not a substitute for utility or emergency instructions. Source: GeoGridIQ
To try the current workflow, readers can create or open an account, consult Pricing for current purchase actions, and inspect the availability labels attached to their dashboard data. The archive remains useful for understanding why saved locations and plan gates were designed, while current surfaces answer what can be used now. Any future refresh should update the visible facts-reviewed date and re-run the billing, entitlement, model, batch, and freshness checks rather than simply changing marketing copy. Sources: GeoGridIQ GeoGridIQ
Scope and safeguards
Limitations and responsible use
- Product configuration can change after the displayed review date.
- Code-defined entitlements do not establish deployment, billing, provider freshness, or forecast availability.
- This article reports no model accuracy, calibration, savings, or operational-performance result.
- Screenshots and diagrams are dated or conceptual and must not be read as current forecasts.
Frequently asked questions
Questions this article answers
Is this the current GeoGridIQ feature list?
No. It is an archived June 2026 release note. Verify current behavior on Pricing and inside the authenticated product.
How many saved locations does each plan define?
At the July 26 code review: Free 1, Pro 5, Business 10, and Enterprise custom. These entitlements do not make paid Checkout available.
Can I purchase Pro or Business from this article?
No. The audited runtime's billing-readiness check was false. The current Pricing page determines whether a purchase action is offered.
Does a prediction widget mean a trusted forecast is available?
No. Interface entitlement, artifact safety, current generation, and freshness are independent gates.
Evidence register
Sources
Sources were reviewed on . Mutable sources are rechecked on the article review schedule.
-
GGI_PLAN_LIMITS GeoGridIQ. Server-enforced plan limits and tests.
-
GGI_BILLING GeoGridIQ. Billing readiness gate.
-
GGI_MODEL_STATUS GeoGridIQ. Protected-artifact safety and runtime availability audit.
-
GGI_PRICING GeoGridIQ. Current pricing and checkout availability.