Change the words on your site yourself. Live in one to two minutes.
Open the editor at its own address, enter the code sent to your work email, and edit the labelled fields chosen for your site. Save once: the site re-renders, checks itself and redeploys. Nothing from the editor ships to your visitors.
What can I change without asking anyone?
The words. Headings, paragraphs, the small label above a heading, button text, contact lines, and lists such as certifications. Open a tab per page and edit what that page says. Edit the footer and the lines that appear on every page in one shared tab, so one change lands everywhere at once. Where a page offers them, the browser tab title and the description Google shows sit last.
The layout and the theme stay out of reach, and so do the facts several pages depend on: a book's page numbers and its ISBNs, for example. Those live in the build, so an edit cannot make one page disagree with another. Where a figure is offered, it is a labelled field the build checks before it publishes.
Will I know what each field does?
Yes. Every field carries a label written for your site, not a key name: "Phone (optional, leave blank to hide)", "Line under the logo", "Small label above the heading". On sites built to the current rule, a field with no written label is not offered at all. Fields sit in the order the page reads, top to bottom, so the section you see on your live site is the section you find in the editor.
Some lines carry a value the build fills in. A note under that field says so and asks you to edit the words around it. A list with a fixed number of entries appears as one field per entry, so you can reword every item and never change the count the page depends on.
What happens when I press Save and Publish?
Five things, in order. The service keeps a copy of the content as it was. It straightens any typed dashes. It writes the new content file. It re-renders every page from that file, and the render is the check: on a site that carries figures, a price typed as a word, a price typed into an answer, or a fill-in token the site cannot fill each fails it. If the render passes, the result goes to Cloudflare Pages, and the editor tells you the site is publishing and will update in about one to two minutes.
If the render fails, the previous content goes back, nothing is published, and the editor shows you the reason. Before you save, a dot on each page tab marks the pages you have touched, so you know exactly what a publish will carry.
Will the editor slow my site down?
No. None of it is on your site. The editing page lives on edit.trulata.com. On our static path, your public site is a set of static files on Cloudflare Pages: no content system answering a visitor's request, no editor script in the page, no database call. The only thing that reaches your site is the re-rendered files. Why the public page carries nothing extra has its own page.
Who can open my editor?
Only the people on its list, checked in three layers. First, edit.trulata.com is its own Cloudflare Access application with its own guest list. Sign-in is a One-Time PIN: no account, no password, a code at your work address. Second, the tunnel fences that hostname to the editor path alone; every other path returns a 404, so the address reaches nothing else we run. Third, our service keeps a list of verified emails per site, so one client can never open another's editor.
The link we send you is plain, with nothing secret in it, and the page holds no credential: your browser carries the sign-in on its own. Our own team can open any site it manages. The three layers in detail have their own page.
Will it work on my site?
On a site we build, yes. Two client sites run on it today, plus concept sites in build. Each has a content file and a generator that renders the pages from it, and the editor is the front of that pair. A site hand-built elsewhere needs that generator written first, and we have done that for a site that arrived as hand-authored HTML. WordPress has its own path: a save writes the copy into the site's own store and clears its cache instead of redeploying, and it cannot touch the theme or the layout.
There is no generator that turns a prompt into a site. The editor changes your own words on a site we built, safely, with no content system riding on the public page. See the website view for what the Command Center shows about the same site, and our website services for the design and build itself.
The editor, step by step.
| Step or layer | What happens | Where it runs |
|---|---|---|
| Sign-in | Cloudflare Access, its own application and guest list, One-Time PIN to your work address | edit.trulata.com |
| Path fence | The hostname reaches the editor path only; every other path returns 404 | The tunnel |
| Site map | A verified email list per site; our team can open any site it manages | Our service |
| Fields | Labels written per site; on current builds a field with no label is not offered; facts held in the build are not offered | Per site |
| Save | Previous content kept, dashes straightened, content file written | Our service |
| Publish | Every page re-rendered and checked, then deployed to Cloudflare Pages, about 1 to 2 minutes | Cloudflare Pages |
| Failed render | Previous content restored, nothing published, reason shown in the editor | Our service |
| On the public page | No runtime content system, no editor script | Your site |
The editor lives on its own address behind its own login, and the only thing that reaches your site is the re-rendered static files.
Questions, answered.
Do I need an account or a password?
No. A One-Time PIN arrives at your work email each time you sign in. There is no password to keep, and the link we send carries nothing secret.
Can a save break my site?
No. A page that fails to render is never published. The service keeps the previous content before it writes anything; if the re-render fails, that content is restored, nothing ships, and the editor shows you the reason.
How long until my change is live?
About one to two minutes after Save and Publish. The site re-renders, deploys to Cloudflare Pages, and the editor tells you it is publishing.
Can I change prices, hours or the page layout?
Words yes, layout no. The layout and theme are not editable. Figures depend on the site: where one is offered, it is a labelled field the build checks, so a price typed as a word is refused. Some figures stay in the build, such as a book's ISBNs and page numbers, and our team changes those for you.
Can someone else at my company edit too?
Yes. Ask us to add their work email. We put it on the guest list and map it to your site. An address not on the guest list cannot sign in at all; one that signs in but is not mapped to your site sees a message to ask us, and nothing else.
Does it work with a WordPress site?
Yes, on its own path. A save writes the copy into the site's own store and clears its cache instead of redeploying. It cannot touch the theme or the layout. Most sites on the editor are on our static path.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.