Salt Atlas

Salt Atlas is an interactive world map and evidence-based encyclopedia of more than 300 salts, built as a hackathon project by a single developer. The description states it allows users to search and filter by origin, source, production method, and color; explore culinary profiles; receive transparent recommendations; and follow interactive stories tracing salts from their source to the table or along historic trade routes. It is presented as a web application with bilingual support, structured data in YAML and SQLite, and deployed on Cloudflare infrastructure.

The project appears to be an exploratory tool for salt enthusiasts, historians, or culinary professionals interested in the geography, history, and craft of salt. It does not appear to have any commercial revenue, customers, or traction beyond its own self-description. The author claims it is designed for deployment on Cloudflare Pages with Cloudflare Functions and D1, but no evidence of actual usage or adoption exists.

The single most important open question is: What is the intended use case for Salt Atlas beyond a hackathon demo? There is no indication that this project has moved beyond prototype stage or has any commercial or user traction. The author states future plans to expand geographic coverage, add verified photography, and invite expert submissions, but these are unverified claims without evidence of execution.

The description states Salt Atlas is an interactive world map and evidence-based encyclopedia of more than 300 salts. It allows users to search and filter by origin, source, production method, and color; explore detailed culinary profiles; receive transparent recommendations; and follow interactive stories tracing salts from their source to the table or along historic trade routes.

The product is described as a lightweight bilingual web application with interactive mapping, custom cartographic styling, filters, comparison tools, guided recommendations, and narrative experiences. It uses structured YAML dataset compiled into GeoJSON for the map and SQLite for local querying. The frontend is designed for deployment on Cloudflare Pages, with Cloudflare Functions and D1 supporting community submissions.

The author states it combines more than 300 mapped entries with evidence tracking, culinary guidance, interactive production stories, historic salt roads, recommendation tools, and a distinctive hand-drawn cartographic identity.

The description states Salt Atlas is positioned as an experience that feels like exploring an old atlas rather than browsing a conventional database. It aims to make the stories of salt visible through interactive mapping and narrative experiences.

The author claims it turns a large structured dataset into an experience that is both practical and exploratory, combining evidence tracking, culinary guidance, interactive production stories, historic salt roads, recommendation tools, and a distinctive hand-drawn cartographic identity.

There is no evidence of prior positioning or evolution in the description. The project appears to be a single self-reported iteration with no indication of how it has changed over time or whether it was previously positioned differently.

The description does not clearly identify target customers or an ideal customer profile (ICP). It states that users can explore culinary profiles, receive transparent recommendations, and follow interactive stories tracing salts from their source to the table or along historic trade routes. The author mentions that it is designed for salt enthusiasts, historians, or culinary professionals interested in the geography, history, and craft of salt.

However, there is no evidence of specific customer segments, personas, or user research. The description does not state whether the product targets end consumers, businesses, educators, or researchers.

The description does not provide any evidence of a business model or pricing structure. It states that Salt Atlas is an interactive world map and evidence-based encyclopedia of more than 300 salts, but there is no mention of monetization, subscriptions, licensing, or fees.

There is no indication of whether the product is free to use, paid, or supported by advertising. The author mentions future plans to invite experts and producers to improve entries through moderated submissions, but this does not imply a revenue model.

The description states that Salt Atlas was built using a structured YAML dataset compiled into GeoJSON for the map and SQLite for local querying. The frontend is described as a lightweight bilingual web application with interactive mapping, custom cartographic styling, filters, comparison tools, guided recommendations, and narrative experiences.

It is designed for deployment on Cloudflare Pages, with Cloudflare Functions and D1 supporting community submissions. The author mentions that they learned that uncertainty should be shown rather than hidden: location precision, missing translations, incomplete evidence, and editorial guidance are all communicated directly in the interface.

There is no evidence of scalability, performance metrics, or production-grade infrastructure beyond its deployment on Cloudflare.

The description states that Salt Atlas is a hackathon project submitted to the OpenAI 2026 hackathon. It was built by a single developer (heyaozh He) and has no evidence of user adoption, customer base, or revenue.

The author mentions accomplishments such as turning a large structured dataset into an experience that is both practical and exploratory, but there is no evidence of actual usage or impact beyond the project's own description. The project does not appear to have moved beyond prototype stage.

The description does not provide any information about competitive landscape or similar products. It does not mention competitors or how Salt Atlas differentiates from existing salt-related tools or databases.

There is no evidence of market analysis, competitive positioning, or differentiation strategy in the description.

• Lack of commercial traction: The project is described as a hackathon submission with no evidence of revenue, customers, or adoption.
• Single developer team: The project was built by one person, which raises questions about scalability and long-term maintenance.
• Unverified future plans: The author states future plans to expand geographic coverage, add verified photography, and invite expert submissions, but these are unverified claims without evidence of execution.
• No business model: There is no indication of how the product will generate revenue or sustain itself.
• Limited scope: The project focuses on salt, which may limit its appeal or potential for growth beyond a niche audience.

1. What is the intended use case for Salt Atlas beyond a hackathon demo?
2. How does the team plan to scale the product and maintain it beyond the initial prototype?
3. Are there any plans to monetize the platform or generate revenue?
4. What are the specific challenges in expanding geographic coverage and adding verified photography?
5. How will expert and producer submissions be moderated, and what quality control measures are in place?
6. Is there any interest from culinary professionals, historians, or educators in using this tool?
7. What is the timeline for moving from prototype to a production-ready version?