Skip to content

Hexby +

Your production UI lives in another git host? Here’s what happens next.

How it works

Four moves, then you ship

  1. 01

    Connect

    • Connect the repository behind your production UI to Hexby.
    • Hexby works on the code that actually runs your product.
  2. 02

    Visualize

    • Hexby extracts your UI into a visual workspace.
    • Designers, PMs, and developers see the real production UI.
  3. 03

    Iterate

    • Review and iterate visually.
    • Use your preferred AI agent to implement changes.
  4. 04

    Ship

    • Push changes back to the repository.
    • Review and merge.

Before you start

What you’ll need

  • Your production codebase

    An existing product whose UI lives in git.

  • Access to the repository

    Connect the repository behind the product.

  • Your preferred AI agent

    Use any agent you’re comfortable with (e.g. Cursor, Claude, etc).

Turn your code into a visual workspace.

Try Hexby