# Anyone here tried non-OpenGeoSys tooling for small model visualizations?

**URL:** <https://discourse.opengeosys.org/t/anyone-here-tried-non-opengeosys-tooling-for-small-model-visualizations/2065>\
**Category:** Uncategorized\
**Created:** [November 16, 2026, 7:15pm UTC](https://discourse.opengeosys.org/t/anyone-here-tried-non-opengeosys-tooling-for-small-model-visualizations/2065 "2026-11-16T19:15:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![michaellewis](https://discourse.opengeosys.org/letter_avatar_proxy/v4/letter/m/d78d45/32.png) [@michaellewis](https://discourse.opengeosys.org/u/michaellewis)\
**Post date:** [November 16, 2026, 7:15pm UTC](https://discourse.opengeosys.org/t/anyone-here-tried-non-opengeosys-tooling-for-small-model-visualizations/2065/1 "2026-11-16T19:15:01Z")

</div>

I’m a graduate student in Little Rock working on a small groundwater flow model for a class project, and I’ve been using OpenGeoSys for the simulation side. The meshing and solving parts have been fine, but I’m now trying to put together a simple interactive viewer for my results so my classmates can look at the outputs without running the full toolchain themselves. I came across this comparison of app builders that caught my eye: [Best Rork Alternatives (2026)](https://aibuildercompare.com/alternatives/rork). I’m wondering whether anyone here has tried building a lightweight front end for OGS result files using a no-code or low-code app builder rather than a full web stack. My main concern is whether these tools can handle the data formats OGS spits out, or if I’d end up re-exporting everything anyway. I don’t want to sink time into something that can’t read VTU or CSV outputs cleanly. Has anyone gone down this route and found it workable? Would appreciate hearing what actually worked.
