Patchlamp
How it works
The long version.
A website is $250 once, with a year of Hosting included. For ongoing office work, choose a Patch plan and text Patch, our AI operator, to make an estimate or invoice. Plans run a site you already have or buy separately.
Taylor Remund, American Fork, Utah
How it works
You text. Patch patches it through.
You text
"We're open till 3 on Saturdays now." "Add Tuesday 9am as a booking slot." A photo of the finished job with "put this on the homepage." On SMS you get "Got it — working on this now" right away.
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.
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 itself.
Wondering whether it can do the thing you actually need? Ask it. Patch is 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 it can work in.
This Patch talks. It has no tools here and no access to anyone's site, menu or account — it can't make a change from this page, and it will tell you so. The Patch that does the work is the one clients text. It's Claude, made by Anthropic, under rules Taylor wrote, and it will say that if you ask.
What Patch can do keeps growing
Ask for something it can't do yet and that isn't the end of it.
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
- Your website is hosted separately and stays up regardless — it is served by Cloudflare, not by the machine Patch runs on. Patch itself 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).
- 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 photos, text, lists, bookings, notes and domain are always yours. A website bought for $250 is yours from the day you pay. While we serve it, its code sits in a GitHub repository under the Patchlamp organization, served by Cloudflare Pages. You get the site files and their history when you leave. On request, we move the repository to a GitHub account you control. Patchlamp keeps its tools, templates, software and messaging service.
- 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.
- Web tools
- Besides the pages people see, a site can carry the tool your business runs on: a private page at /admin on your own site, where your quotes, bookings, orders, customers, jobs, routes or stock live. You sign in with a link sent to your email, and change it there or by text. Every list is in your site's own database and leaves with the site. Six tools, each on a live demo.
- 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. American Fork, 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.
That line is Taylor's, not Patch's: he answers it or calls you back. The work goes by text; the phone is for the questions a page can't answer.
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?
Your content and domain are always yours. Buy the website for $250 once and it is yours from the day you pay. A monthly plan runs a site you already have or bought; it does not include a new website. You can take your files when you leave and ask us to move the repository to your GitHub account. Patchlamp keeps its tools, templates, software and messaging service.
Why a monthly fee and a usage allowance?
One-time services need no Patch plan. The website includes a year of Hosting; after that, you choose whether to renew or host it elsewhere. If you choose a monthly plan, the fee pays for keeping the service running and includes a usage allowance. Usage is measured in dollars of AI work and texts sent for your business, rather than a message count.
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?
Your website is hosted separately and stays up regardless: Cloudflare serves it, not the machine Patch runs on. Patch 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.
Can Patch do the thing I actually need?
Ask it — the chat bubble is on every page, and Patch answers that question itself. The everyday work is text, dates, hours, photos, prices, menu items and new pages of a kind your site already has. A shop, a booking calendar or a list of your jobs is a web tool, and Patch builds those too. Something bigger, a members area or logins for your customers, is a conversation with Taylor rather than a text, and it's the kind of request that decides what gets built next.
What happens to my lists if I stop?
They're yours. Every list a web tool keeps is in your site's own database, not a shared one, and it leaves with the site: you get every row as a spreadsheet file (CSV) and as JSON, along with the site itself.
We'll patch you through.
You get your number when your account is set up. Usually the same day.
