KetchUp – Open-source SketchUp alternative built with Rust and WebGPU

An open-source, browser-based SketchUp alternative written in Rust and WebGPU is drawing attention for its impressive performance and licensing freedom, but also criticism for rough edges in usability, inconsistent workflows, and even its SketchUp-adjacent naming. Commenters debate how close it comes to SketchUp’s famously intuitive UI, noting issues like mandatory object naming, nonstandard push–pull behavior, and limited export options, while still welcoming a free desktop-friendly path for hobbyists and ex-SketchUp users frustrated by Trimble’s pricing and web focus. The project also becomes a springboard for broader arguments about “vibe-coded” AI-generated tools: whether individuals should now build their own custom software, how sustainable that is to maintain, and what it means for collaboration and software quality.

Project scope and positioning

  • Open-source, Rust/WebGPU-based SketchUp-like 3D modeler, aimed at being free and fast in the browser.
  • Seen as filling a gap for hobbyists and light professional work who can’t justify SketchUp’s subscriptions or dislike the web/SaaS direction.
  • Several users note they still rely on old SketchUp 2017 or would otherwise move to Blender/FreeCAD.

Naming, branding, and legal concerns

  • Original name “KetchUp” is widely criticized as too close to “SketchUp” and potentially infringing.
  • Project appears to be mid-renaming (KetchUp vs BenchUp), causing confusion; some doubt whether this is sufficient to avoid trademark issues.
  • There’s also a name collision with an existing open-source “ketchup” drawing tool.

UX, features, and quality

  • Strong praise for the idea and for how responsive and “native” the Rust/WebGPU UI feels in the browser.
  • Multiple complaints that it “falls short” of SketchUp’s intuitiveness:
    • Forcing users to name every rectangle.
    • Non-intuitive push/pull workflow and snapping behavior.
    • Trackpad navigation not working like SketchUp; menu interactions feel off.
    • Reports that basic extrude operations can glitch.
  • Suggestions: curated example files, feature showcases, and better parity with SketchUp’s established habits.

Formats, interoperability, and ecosystem

  • Export: STL and OBJ supported; seen as fine for 3D printing but limiting for building CAD.
  • Import: there is at least some support for SketchUp (.skp) via an external library.
  • Several comparisons and pointers to other emerging or alternative tools (hew3d, Ingetrazo, Solidcraft, GeoLibre, etc.).
  • Some users emphasize the importance of something like SketchUp’s 3D Warehouse and plugin ecosystem.

AI “vibecoding”, trust, and maintainability

  • Tool is described as largely AI-generated (“vibe-coded”), sparking a large meta-discussion:
    • Enthusiasts: AI makes complex tools like CAD plausible for solo developers; performance claims are strong.
    • Skeptics: many AI-cloned apps feel 80% finished, with subtle bugs, odd decisions, and poor polish; concern about long-term maintenance and security.
    • Broader debate on whether people should build their own tools with LLMs vs. contribute to mature OSS, and whether the proliferation of solo AI projects harms collaboration and trust.