Every website we build comes with the Limatulus Agent: you change your live site by describing the change in plain language. No dashboard to learn, no tickets, no waiting on a developer to update a phone number. Here is exactly what you do — and what happens behind it.
What you do
You sign in, pick your site, and write what you want in your own words: “Add a short FAQ to the Services page”, “Swap the hero photo”, “Update the phone number in the footer.” That is the whole interface — a sentence.
What you see before anything goes live
The Agent prepares the change and shows you a visual preview: the real page, exactly as it will look, before it is public. You read a plain-language summary of what changed and compare it to what's there now. Your live site has not changed yet.
You decide
You have three moves: Approve & publish and it goes live; Request a change if it is not quite right; or Send it to us if you would rather a person handle it. Approve and it deploys in seconds. Reject and it costs nothing. And anything you publish can be rolled back to the previous version.
What it costs
The Agent is metered by outcome: one change — described, previewed, approved and shipped. Your plan includes a generous monthly quota, and you always see the count before anything is deducted. Drafting and previewing are always free; you only spend when a change goes live.
When a person steps in
Some work should not be guessed at — pricing logic, payments, anything that touches your data model or a third-party integration, or a change that is simply out of scope. The Agent does not improvise on those. It routes them to the Limatulus team, where they are reviewed before they ever touch your site. Escalation is part of the design, not a failure.
How the system actually works
The panel you use never holds your source code or your deployment secrets. It records two things: your request, and your approval. A separate, sandboxed worker — the only part with real access — does the work: it makes the change on its own branch, builds the site, runs the quality checks (performance, accessibility, types), and produces the preview you saw.
When you approve, that same worker deploys to production and writes everything to an audit log: the request, the exact diff, the credit cost, and who approved it. A rollback simply re-publishes the last known-good version. Nothing reaches your live site unseen, and every change is reversible.
Why it is built this way
This is the whole studio in miniature — engineering, simplicity, performance, effectiveness. You get the speed of changing a site with a sentence, the safety of preview, approval and rollback, and a real engineering team behind it for anything bigger. You stay in control at the only step that matters: approval.
Software, Refined.