How it works

The long version.

What happens when you text, who answers, what runs where, and what you own. Every sentence on this page is meant to be literally true of the system as it runs today.

How it works

You text. Patch patches it through.

Step 1

You text

"Add Friday's show to the site." "Mark the burger sold out." A photo with "put this on the menu." On SMS you get "Got it — working on this now" right away.

Step 2

Patch makes the change

Patch opens your site's files, makes the change, and puts it live. It works inside a walled-off folder that holds only your things.

Step 3

You get "Patched."

Before it says a change is live, it loads your live site to confirm. Then a plain reply: what changed and where to look. Not what you meant? "Undo that last change" puts it back.

Every change is saved in your site's history, so nothing is lost. Anything Patch shouldn't handle by itself, a domain, a store, a login, anything that needs an account or money, it says so plainly and passes to Taylor. You're told, Taylor gets a note.

Talk to it before you pay for it

Patch answers for himself.

Wondering whether he can do the thing you actually need? Ask him. He's on every page of this site, bottom right: a real conversation, not a recording. Prices, what a plan covers, whether your site is the kind he can work in.

This Patch talks. He has no tools here and no access to anyone's site, menu or account — he can't make a change from this page, and he'll tell you so. The Patch who does the work is the one clients text. He's Claude, made by Anthropic, under rules Taylor wrote, and he'll say that if you ask.

What he can do keeps growing

Ask for something he can't do yet and it doesn't stop there.

The request gets flagged the moment it happens. A separate agent, which can read the code but can't change it, works out what the fix would take and writes it onto Taylor's list with the diagnosis attached. What clients ask for most is what gets built next — that's the whole roadmap, and it's why this page doesn't carry a list of things Patch won't do.

Anything that needs an account, a card, a domain or a login is a person's step by design. Patch says so plainly and it reaches Taylor the same minute.

Or change a real restaurant's website yourself → — the demo restaurant, by text, live in a minute.

Straight answers

What it is, exactly.

Every sentence on this page is meant to be literally true of the system as it runs today. These are the ones people ask about.

Hours: It runs around the clock, on hardware Taylor owns and operates in Utah, not in a data center. That's one machine with a person behind it rather than a redundant cluster, so we don't publish an uptime number and won't pretend to: if it's ever down, a text on SMS or Telegram waits and is handled when it's back (a Discord message sent while it's off needs resending). Your website is hosted separately and stays up either way.
Speed: Texts are picked up within a minute. A typical change, a new date, new wording, a photo, is made and confirmed live in a minute or two. Big jobs take longer. If one can't be finished, you're told rather than left waiting.
When something breaks: You get: "I ran into some difficulties making that change, so I haven't put it live. Taylor's been notified and is on it." Taylor gets what you asked, the actual error, and how long it ran. Same if you hit the daily cap on messages: Patch stops for the day and Taylor is told.
Ownership: Your site is a GitHub repository under the Patchlamp organization, served by Cloudflare Pages. The day we part ways the repository is transferred to an account you control with instructions for hosting it yourself (Cloudflare's free tier serves it as it is), and we keep it live while you move; you'd just change it another way.
Where Patch works: Inside the folder that holds your site and your menu, and nowhere else: anything outside it is blocked, not just discouraged. Only people you've authorized get a response at all. Anything that needs an account, a card, a domain or a login reaches Taylor the same minute, with what you asked for attached — that's the design, and it's why you can hand Patch your website without handing over anything else.
What happens to what you send: Your message and photos go to the relay, where Claude makes the change and writes the reply. Twilio, Telegram or Discord carry the messages; Anthropic runs the model; GitHub hosts the site; Pexels and Google supply stock and generated photos when you ask for one. The privacy page has the full list.

Who's behind it

Taylor Remund. Utah.

A working software engineer. Taylor built Patchlamp so a website could be changed by the person who owns it, from their phone. Patch does the work; Taylor reads the errors.

taylorremund.com

Questions

Before you start.

Do I need to be technical?

No. If you can describe what you want in a text message, you can use everything here. Patch replies in everyday language: "the change is live, check the Shows page on your phone," never file names or commands.

What if Patch breaks something?

It can't break anything permanently. Every change is saved in your site's history before it goes live, any change can be undone by asking, and Patch doesn't say a change is live until it has loaded your live site and seen it. If a change can't be made, you're told and Taylor is notified.

Do I actually own it?

Yes. Your website, its code, your domain, your customer data. The code sits in a GitHub repository under the Patchlamp organization while we work together and is transferred to yours when we stop.

Why a monthly fee and a usage allowance?

They pay for different things. The monthly is the obligation: someone is on the hook, the system is kept running, and there's a person who reads the errors. The usage is what the AI actually consumed doing your changes, measured in dollars and included up to the allowance.

Which apps can I use?

SMS (photos included), Telegram, or Discord: message Patch directly, or Taylor can point a channel in your Discord server or a Telegram group at your project so your whole team can use it. Only people you've authorized get a response.

Is it available 24/7?

It runs around the clock, on hardware Taylor owns and operates in Utah. It's one machine with one person behind it, not a redundant data center, so there's no uptime guarantee and we don't claim one; texts on SMS and Telegram wait and are handled if it's ever down, and your website is hosted separately and stays up regardless.

Can Patch do the thing I actually need?

Ask him — the chat bubble is on every page, and he answers for himself. The everyday work is text, dates, hours, photos, prices, menu items and new pages of a kind your site already has. Something bigger, a store, a booking system, a members area, is a conversation with Taylor rather than a text, and it's the kind of request that decides what gets built next.

We'll patch you through.

You get your number when your account is set up. Usually the same day.

Start See pricing