A friendly guide to the sea near you: which beach is good for swimming today, and the best hour tomorrow. It is built from public data, in the open, as citizen science, and it says "no data" when it does not know.

marola.dev: the live map (Florianópolis, Rio de Janeiro, Salvador) · docs.marola.dev: using and building marola

• Open and non-profit. Much of Brazil's ocean data sits with private holders, and nobody can forecast water quality, climate disasters or environmental accidents without it. A non-profit that promises to share everything can ask for that data; one more company could not.
• Water quality first. Sanitation in Brazil is far from solved, so marola starts with the question "can I go in this water?". A national bathing-water ranking is under discussion.
• A water super app. One place that hands you the answer, not the tools: what Sequoia calls services as software.
• Open source, for the long term. With AI, code is no longer the secret. Brazil needs projects that outlive the people and the governments that started them.
• Partners, not money. We welcome storage, GPU time or data from companies, credited discreetly on the site. No ads, no tracking.

One project, many small repos: a distributed monolith. A shared plan and rules let AI agents see the whole picture, while each repo keeps its own tests and releases and pins the others' published versions instead of reading their code.

marola started as one repo. By September 2026 that one tree forced one build on everything: a CSS change to the map waited on a Scala compile, and parallel agent sessions needed 30+ worktrees to stay out of each other's way. Splitting into separate repos fixes the builds but loses what the single repo did best: an agent could see the whole project at once.

The umbrella keeps both. marola holds no code, only the team layer (plans, rules, the phase list, the docs site) and every other repo as a git submodule. Clone it with --recurse-submodules and the whole project is one directory again, with the shared rules at the root and each repo's own rules inside it. Each repo still builds, tests and releases alone, and talks to the others only through versioned artifacts it pins.

The idea is an old one: a "meta-repo" that pins many repos into one workspace, as Android's repo manifest does. marola adopted it in MIP-0070 (2026-09-30), which also lists the alternatives it turned down.

Help out: use the map and tell us when it is wrong, or open an issue in Portuguese or English. More in Contributing.