Maker.inside BoxClaw Sign in Open in BoxClaw
Software & Dev · app builder

Describe it. Watch it get built. Then decide if it ships.

BoxClaw Maker is your software-engineering department. Troy takes the ask on the phone, in a text or in the chat, turns it into a brief, and hands it here. You get a link you can open — and a Publish button that does not deploy until you press it.

Turned on from the store. No signup here, nothing to install, nothing to host.

How it runs

You never open a tool. You answer a message.

Troy is the only one you talk to — call, text, Telegram, WhatsApp, Signal or the chat. The Maker is one of the hands Troy holds.

A brief, not a promptTroy asks one question or none, then writes the brief. What it is for, and how you will know it worked.
A real machineNode, Python, git and a Docker daemon of its own. Its own database, cache and storage per project.
It is still there on ThursdayYour files, your database and your git history persist. An idle project has no container running and has lost nothing.
The code is yoursIt pushes to your GitHub. Exportable without Troy, and it stays yours if the membership ends.
The rule

Preview is free. Publish needs a person.

Two buttons, side by side, and they are not two speeds of the same action. A preview is a link only you can open. Publishing does not deploy — it puts the exact bytes in front of you and waits.

▸ Preview free · reversible · reaches nobody ⇧ Publish needs your yes, every time

An approval is about specific bytes. Commit again and it does not transfer — a new build is a new thing to look at. Troy cannot approve its own work, and neither can the Maker.

Where it runs

Ours by default. Yours if you'd rather.

Signing in puts you on the hosted engine with nothing to configure. If you would rather run the machine yourself, both other ways still work.

BoxClaw Cloud · defaultThe hosted engine, already running, already signed in. You never type a host.
LocalYour own agent-server on your own machine. Point the Maker at it.
RemoteYour own box, over an SSH tunnel, ngrok or a TLS proxy.