Verified context
Official company and regional sources support public operating footprints and industry concentration. ClickHouse’s announcement verifies the RunReveal acquisition claim, with its displayed publication date cited.
Public regional and corporate sources establish context. Analytical workload hypotheses connect that context to ClickHouse. The distinction is intentional.
Official company and regional sources support public operating footprints and industry concentration. ClickHouse’s announcement verifies the RunReveal acquisition claim, with its displayed publication date cited.
Industry-to-workload fit and the 30/60/90 narrative are independent analysis. Qualitative confidence describes the strength of that use-case inference, not commercial intent, account priority, or probability of adoption.
No regional deployment, technology stack, data access, buying intent, or commercial relationship is verified for the enterprise examples. This research uses no private customer records or personal contact information.
40 distinct commercial parent groups and 18 geographically specific public/defense mission prospects are independent workload hypotheses—not existing customers, active solicitations or verified buying intent. 12 official ClickHouse customer references are a separate, outside-region evidence category. State and locality filters never turn those references into local deployment claims. Every ecosystem record includes mission, workload, fit, public evidence and a deployment or procurement boundary.
Government eligibility is not established: FedRAMP, DoD Impact Level, classified capability, certifications and procurement vehicles require independent verification for the actual service, workload and sponsor. Self-managed software is not automatically authorized.
Illustrative sector examples. Not confirmed ClickHouse customers.
Shipment-event exploration and network exception analytics.
Direct relationship between event-heavy logistics and analytical latency; workload unverified.
Corporate sourceOperational observability and digital journey analytics.
Public aviation footprint supports the use-case thesis; architecture unverified.
Corporate sourceFraud investigation and banking-service performance.
Sector relevance is established; governance and technical need require validation.
Corporate sourceUtility asset telemetry and operational visibility.
Energy operating context is public; data accessibility and platform fit are unknown.
Corporate sourceSecurity-data investigation and analytical infrastructure.
Public security-platform focus aligns with event analytics; no deployment asserted.
Corporate sourceCommerce-event analytics and application observability.
Retail/restaurant commerce context, distinct from NCR Atleos after the 2023 separation. No customer status asserted.
Corporate sourceNon-patient operational capacity and service telemetry.
Healthcare operations suggest potential; regulatory and architecture review are essential.
Corporate sourceNetwork-service event investigation and operational observability.
Public corporate address supports Jackson-area context; traffic scale, analytical stack and data access are unknown.
Corporate sourceDistribution milestones and operating-event analysis.
Headquarters and food-production context are public; event availability and analytical requirements are unverified.
Corporate sourceJourney disruption and fleet-service event exploration.
Corporate Miami context; cruise brands are not repeated as separate enterprise examples. Workload remains unverified.
Corporate sourceParent groups are represented once: Carnival cruise brands and NextEra subsidiaries are not repeated as separate enterprises. NCR Voyix is distinct from NCR Atleos after the 2023 separation. Every regional example is located in Florida, Georgia, Alabama or Mississippi.
High: the public business model has a direct relationship to event-intensive analytics. Moderate: sector relevance is plausible, but constraints or technical evidence are less specific. Neither label is an account score. All workload needs remain unverified.
Primary sources preferred. Company sources are self-reported and may change.
Source register narrowed to the four-state scope on October 16, 2026. Retained citations preserve the prior link-review limitations: some official sources block automated requests, so their current browser availability is not certified. Company and agency material establishes public context; no vendor story is an independent audit.
Public context · Lakeland / FL
Filing identifies Lakeland principal office and grocery operations. Private-company platform priorities and proprietary data access are unverified.
Public context · Plantation / FL
Company filing documents Plantation corporate location and e-commerce business. Dual-location corporate context; engineering authority may be outside Florida. Exclude pharmacy/personal customer data.
Public context · Fort Lauderdale / FL
Citrix official office page establishes Fort Lauderdale operating footprint. Represent Cloud Software Group once. Existing analytics products and parent-level platform ownership require validation.
Public context · Orlando / FL
SEC company record establishes Orlando corporate address. Brands are not separately counted. Existing reporting may suffice; confirm event feeds and store-system permissions.
Public context · Jacksonville / FL
Filing identifies Jacksonville principal office and freight operations. Carrier/agent event rights and existing visibility platforms may constrain a second analytical layer.
Public context · Coral Gables / FL
Official health-system leadership source documents South Florida operating context. Begin with non-patient events. Confirm HIPAA obligations, data rights and contractual/security controls before regulated use.
Public context · Miami / FL
Official investor source establishes company energy-services and Miami context. Trading and operational systems remain authoritative; source integration and global platform ownership are unverified.
Public context · St. Petersburg / FL
Company filing identifies St. Petersburg principal office and financial-services business. Retain regulated surveillance and transactional controls; privacy, retention and reconciliation require design.
Public context · Clearwater / FL operating office
Official investor-contact page documents Clearwater office; not sole global headquarters. Confirm decision authority at the Florida operating site and rights to global distribution-event feeds.
Public context · St. Petersburg / FL
Company filing identifies St. Petersburg principal office and manufacturing context. OT data separation and historian coexistence matter; no control-loop or industrial safety function is proposed.
Public context · Atlanta / GA
Company filing establishes Atlanta office and specialty-retail business. Validate event volume and existing warehouse latency; batch reporting may be the better answer.
Public context · Atlanta / GA
Official investor source documents Atlanta payment-technology company context. Confirm current corporate perimeter and event ownership; preserve authorization, reconciliation and existing analytics controls.
Public context · Atlanta / GA parent headquarters
Filing documents parent and operating-company structure across the region. Count parent once; Georgia Power, Alabama Power and Mississippi Power are not separate commercial records. No SCADA replacement or grid-control access.
Public context · Sandy Springs / GA operating headquarters
Official state release documents planned North American headquarters consolidation in Atlanta; completion is not independently certified. Count parent once, including Alabama manufacturing context. Validate current consolidation status and parent-governed platform decisions.
Public context · Atlanta / GA
Official investor filing establishes Atlanta principal-office context. Mature internal platforms may already meet the need; evaluate coexistence only with a bounded, measurable decision gap.
Public context · Atlanta / GA
Official headquarters FAQ identifies Atlanta location. Private-company vendor decisions are unknown; restaurant event rights and operator permissions require confirmation.
Public context · Atlanta / GA
Official corporate facts document Atlanta logistics-company context. No analytics stack or buying intent is established. Confirm event rights, identifiers and coexistence with existing operational systems.
Public context · Atlanta / GA
Official investor source establishes named airline business and Atlanta corporate context. Reservation and safety-critical systems retain their roles. Confirm retention, partner permissions and data minimization.
Public context · Atlanta / GA
Official company locations source documents Atlanta presence; distinct from NCR Atleos. Verify tenant isolation and current product ownership. No ClickHouse usage, customer-level data access or platform gap is asserted.
Public context · Birmingham / AL
Official company FAQ establishes Birmingham headquarters context. A bounded workload must justify operational overhead. Banking privacy, reconciliation and retention gates apply.
Public context · Birmingham / AL
Official investor source documents Birmingham industrial-company context. Preserve historians and operational controls; confirm OT/IT separation and permitted event extraction.
Public context · Huntsville / AL subsidiary operations
Official acquisition source establishes Dynetics as Leidos subsidiary with Huntsville footprint. Count Leidos once. Verify contract data rights, export control, classification and sponsor approval; no restricted/DoD-approved deployment is asserted.
Public context · Mobile / AL subsidiary operations
Official company overview documents Mobile shipbuilding operations. Count Austal parent once. Defense-contract requirements and export controls must be verified; no CMMC or platform authorization claim is made.
Public context · Birmingham / AL subsidiary headquarters
Official FY2025 statutory statements document Protective Life Insurance Company’s Birmingham headquarters and Dai-ichi ownership in the parent/affiliates section. Count parent group once; validate current group structure and local authority. Retain actuarial and contractual systems of record.
Public context · Birmingham / AL
Company filing identifies Birmingham principal office and hospital business. Governance and HIPAA applicability require review. No clinical decision support or patient-data approval is implied.
Public context · Huntsville / AL
Company filing identifies Huntsville corporate context and networking business. Verify telemetry ownership, tenant separation and existing network analytics; product presence is not demand evidence.
Public context · Tuscaloosa / AL
Official company homepage explicitly identifies Tuscaloosa headquarters and production/distribution facilities. Food-safety and proprietary process data need access review; no platform budget or streaming need is established.
Public context · Birmingham / AL
Official company profile establishes Birmingham banking headquarters context. Financial controls, privacy, reconciliation and source access are distinct gates; no existing customer relationship is inferred.
Public context · Ridgeland / MS
Official corporate media-room source establishes Ridgeland/Jackson-area company context. Traffic scale, data rights and current analytical stack are unknown. Protect subscriber and tenant information.
Public context · Ridgeland / MS
Official corporate contact source establishes Ridgeland headquarters context. Verify event-feed availability, food-safety constraints and workload size; batch reporting may meet the need.
Public context · Gulfport / MS
Company filing documents Gulfport principal-office context. Keep core banking and regulated controls authoritative. Confirm current governance, privacy and reconciliation requirements.
Public context · Flowood / MS
Official corporate-services source establishes Flowood operating headquarters context. Private-company platform ownership is unverified. Preserve control systems and review process-data export rights.
Public context · Pascagoula / MS facility
Official refinery source establishes Pascagoula facility and refining mission. Count Chevron parent once. Local facility is not an independent buying center; global IT/OT and security approval must precede evaluation.
Public context · Lee County / MS manufacturing footprint
Official state development source documents Lee County manufacturing expansion; not Mississippi corporate headquarters. Parent-level platform decisions and current facility status require confirmation. Preserve industrial control systems.
Public context · Greenwood / MS subsidiary operations
Official company support/corporate-office source documents Greenwood presence. Count Middleby parent once. Confirm parent ownership and local platform authority; manufacturing events and data rights are unverified.
Public context · Pascagoula / MS division operations
Official HII division source establishes Ingalls’ Pascagoula shipbuilding footprint. Count HII parent once. Defense-contract, export-control, classification and security gates require verification; no approved restricted-data capability is asserted.
Public context · Juno Beach / FL
Official corporate overview establishes Juno Beach energy-company context. Parent group appears once; Florida Power & Light is not a separate commercial record. No SCADA or safety-control replacement is proposed.
Public context · Tampa / FL
Official company contact source establishes Tampa headquarters context. No ClickHouse adoption or partnership is asserted. Verify product architecture, tenant controls and telemetry rights.
Public context · Altamonte Springs / FL
Official headquarters source establishes Altamonte Springs corporate context. Use non-patient events first; contractual, HIPAA and security review are required before any regulated data evaluation.
Public context · Miami / FL
Official investor-contact source establishes Miami corporate context. Parent group counted once; cruise brands are not separate prospects. Verify partner feeds, passenger-data minimization and current corporate perimeter.
Public context · Tallahassee / FL
Official DMS overview establishes the Florida state shared-services mission. Confirm state acquisition process, interagency data permissions and classification; no current solicitation or approved cloud service is established.
Public context · Orlando / FL
Official OUC source identifies a public utility; automated access is blocked, so current page availability is not certified. Verify utility procurement and security requirements; exclude control-loop/SCADA actuation and customer identifiers. Source requires human availability review.
Public context · Jacksonville / FL
Official JAXPORT site establishes the Jacksonville public-port footprint. Verify authority procurement and partner feed rights; port-security data requires separate handling approval. No bid or vendor relationship is asserted.
Public context · Tampa / FL
Official base overview establishes Tampa installation and air-refueling mission context. Verify contracting sponsor, data classification, enclave and agency authorization. No FedRAMP, DoD IL, ATO, classified capability or contract vehicle is verified; exclude restricted mission data.
Public context · Space Coast / FL
NASA’s official Kennedy page establishes the Florida launch-center mission. Verify center acquisition route, data ownership, export controls and NASA authorization. No procurement vehicle eligibility or flight/safety-system capability is asserted.
Public context · Atlanta / GA
Official GTA overview establishes state technology-service responsibilities. Validate state contracting route and interagency permissions; investigate current authorization and security requirements. No live solicitation or approved service is inferred.
Public context · Atlanta / GA
Official university overview establishes Atlanta public research-university context. University procurement, privacy and sponsor terms require review. Exclude classified or export-controlled research; no GTRI restricted-data access is implied.
Public context · Savannah / GA
Official authority overview establishes Georgia public-port operations. Verify authority acquisition rules and terminal/rail partner feed permissions. Customs and port-security information requires separate authorization; no solicitation is asserted.
Public context · Warner Robins / GA
Official Robins overview documents Georgia sustainment/depot mission context. Verify sponsoring command, acquisition path, classification and network authorization. No DoD IL, ATO or restricted engineering-data eligibility is established.
Public context · Montgomery / AL
Official OIT mission page establishes Alabama state IT responsibilities. Review actual state purchasing authority, agency data rights and service approval. No statewide contract eligibility or active analytics solicitation is established.
Public context · Auburn / AL
Official Auburn overview establishes Alabama public-university context. Confirm university procurement, sponsored-research terms and identity minimization. Restricted research is out of scope absent separate authorization.
Public context · Mobile / AL
Official authority source establishes the Mobile public-port footprint. Confirm authority purchasing and partner event access. Exclude badge/security data without explicit port-security review; no current procurement or ClickHouse relationship is verified.
Public context · Huntsville / AL
Official NASA page documents Marshall’s Huntsville engineering mission. Review NASA acquisition, export control, data classification and center authorization. Redstone co-location does not grant tenant access; no safety/control or classified capability is implied.
Public context · Montgomery / AL
Official Maxwell overview establishes Montgomery education/base mission context. Verify education-data privacy, sponsor and contracting requirements, network boundary and authorization. No IL or ATO claim; operational or restricted personnel records are excluded.
Public context · Jackson / MS
Official Mississippi ITS site establishes the state technology-service organization. Verify actual state acquisition process, agency permissions, retention and cloud approval. No available solicitation or approved deployment is established.
Public context · Starkville / MS
Official university overview establishes the Starkville public-research footprint, not a Jackson metro location. Review university purchasing, sponsor restrictions and research-data rights. Classified/export-controlled datasets are excluded without explicit authorization.
Public context · Gulfport / MS
Official authority overview establishes the Gulfport public-port mission. Verify authority bid requirements and carrier data permissions. Security and access-control data needs distinct approval; no current solicitation or customer relationship is asserted.
Public context · Biloxi / MS
Official Keesler source establishes the Biloxi training installation. Verify sponsoring organization, acquisition, data classification, enclave and authorization. No FedRAMP, DoD IL or ATO status is established; exclude restricted student/mission data.
ClickHouse · official customer reference
Official Visa story describes ClickHouse-backed conversational analytics. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse video documents Deutsche Bank’s sensitive-data warehouse use. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story names SEON’s anti-fraud platform deployment. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story describes streaming payment data for analytics. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story describes Trio’s payment analytics usage. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official named story documents real-time transaction analysis at Juspay. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse Cisco story names the Talos reputation workload. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story describes cancer-research use at the named center. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story documents Lyft’s analytics migration to ClickHouse Cloud. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official story documents Borderless360’s logistics analytics on ClickHouse. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story names Picnic’s real-time analytical use. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · official customer reference
Official ClickHouse story describes the precision-marketing workload and edition. No Southeast deployment is established. Vendor-published evidence is not an independent audit; validate current edition, data rights, security and workload comparability. Reported outcomes are not regional targets.
ClickHouse · displayed publication date: September 1, 2026
Primary acquisition announcement. Describes security workloads and RunReveal’s bring-your-own-database model. The page’s structured metadata lists September 16; this research uses its visible editorial date.
ClickHouse · product documentation / positioning
Primary description of real-time analytical workloads. Performance and economics must be validated on representative data, not inferred from marketing.
ClickHouse · official documentation
Supported ingestion paths and CDC capabilities. Not evidence of a turnkey connector for every incumbent platform.
ClickHouse · official documentation
Context for open-format data access. Supports a coexistence discussion—not a universal migration claim.
Georgia Department of Economic Development
Public basis for the Atlanta–Savannah logistics corridor. Regional concentration does not establish account-level demand.
Mississippi Development Authority
Public basis for logistics and distribution opportunities in Mississippi.
ClickHouse · vendor-published deployment evidence
A separate category from regional account hypotheses. No regional company in this microsite is represented as a verified deployment.
Primary public source · Miami
Establishes regional operating context only. Workload fit and regional ClickHouse adoption are not verified.
Primary public source · Gulfport
Establishes regional operating context only. Workload fit and regional ClickHouse adoption are not verified.
RunReveal · September 1, 2026
Corroborating first-party acquisition announcement; not regional demand evidence.
ClickHouse · documentation
Workload boundary: retain transactional systems of record.
ClickHouse · engineering
Architecture context, not proof of catalog or platform compatibility in a particular environment.
Independent research, not an official ClickHouse publication or endorsement. Sources reflect public information reviewed for this research; changes in source pages can affect dates and facts. No speculative revenue, pipeline forecasts, or customer-level private data are included.