reBuild anything.

Point it at software. Tell it what you want. Let reBot build it.

See it. Want it. Build it.

Your next app already exists.

Start from something real. Tell reBot what you want changed and it builds your version, then checks it against the original and fixes what is off until it works.

Originalstudio.example.com

“Rebuild this site, but make it for my business: Juniper Bakery.”

Your versionjuniper.bakery
Juniper BakerySourdough, pastries and coffeeOrder ahead
Example output
Build yours
  • Websites
  • Web apps
  • Features
  • Repos
  • Contracts
The container

Every reBot has its own machine, so you can build away from your computer.

Each active reBot runs on an isolated machine with a shell, git and a headless browser. It clones, browses, builds and tests there. Your files, conversations and evidence stay saved when the machine shuts down.

  • Work that stays

    A persistent workspace for your project
    Resume when you return
  • Real tools

    Shell · git · headless browser
    Node toolchain
  • Stays in scope

    A build request is the go-ahead
    Asks before going further or deleting
  • Evidence kept

    Findings link to file, line or screenshot
    Reopen or export any time
Compute token

$REBOT pays for the machine.

Every run uses compute: model calls, container time and browser sessions. $REBOT pays for all of it, so there are no API keys to set up and no separate bills. Bigger jobs use more, and the meter ticks in front of you while reBot works.

Ticker
$REBOT
Network
Robinhood Chain
Utility
Pays for model calls and container time
Contract
Published at launch
  • Relative compute per job
  • Ask a question

    An answer with the evidence behind it
  • Recreate a feature

    One flow or component, built and tested
  • Build your version

    A whole site or app, tested and repaired until it works

reBuild anything you see. Point reBot at an app, a website or a feature and it builds your version in a container of its own.

reBot

Launching on Robinhood Chain
Contract published at launch

WORKSPACE / USAGE

Usage, at a glance.

Your current run

Model providerYour API key
Model cost—
Run limit—

Model—
Requests—
Unconfirmed—

Request history

This run only
    Fetching your usage…

    Loading the latest costs and request details.

    reBot settings

    OpenRouter charges your account for model usage. reBot reserves room for each request and pauses when another request cannot fit. This allowance covers usage submitted by this run. OpenRouter accounts that bill a separate upstream provider are not supported yet.

    Remembered keys are encrypted in this browser and restored for your account after sign-in. Clearing site data removes them. The backend holds your key temporarily for runs and receipt checks, for up to 15 minutes. Admitted staging accounts receive limited workspace compute.

    Add a workspace file

    Files up to 32 MiB. Archives are saved as files; they are not automatically extracted.

    Work toward a goal

    reBot continues until the criteria are supported by retained evidence, progress is blocked or a limit is reached. The original inference, tool and time allowances apply across every iteration and resume.