cmsspot is a headless CMS for hand-built HTML and PHP sites. It connects to a server over SFTP and edits the files that are already there. The Free plan costs $0 with no card, no commitment and no time limit, and it is aimed at developers, agencies and their clients.
The point of the tool is to let a client edit PHP website content without touching code: a heading, a paragraph, an image or a button on a page that was written by hand, with the PHP in that file left as it was. Nothing is installed on the site, so there is no plugin, no database and no theme layer to maintain.
This article covers how the editor finds fields, what happens on save, the features that go beyond a single page, the two plans, and one area where the product is still thin.
How pages become editable without markup
Most CMSs need a template or a set of tags before anything can be edited. cmsspot takes a different route. When a file is opened, headings, paragraphs, images, links and buttons become editable fields on their own, with nothing to mark up first. A developer does not need to wrap content in special attributes, convert the page to a new format, or move it into a database.
The live site is untouched. cmsspot is never installed on the site; pages load exactly as built, with nothing added. For a PHP site this means there is no runtime dependency on a third party, no script that has to load before the page renders, and nothing new for the host to run.
For the people who do want to see the code, a Code tab shows the whole file as code for developers, with a syntax check before it goes live. A client sees fields; the developer who built the site can still open the raw file in the same place.
Edit PHP website content without touching code
The save model is what makes this workable on PHP files. When a field is changed, only that field is written back; the rest of the file stays byte for byte, PHP included. A client editing a paragraph does not reformat the file, strip a comment or move an include. The product calls these surgical saves.
Pasted content is cleaned on the way in. removes Word formatting and scripts so they never reach the page. That closes the most common way a hand-built page gets filled with stray span tags after a client pastes from a document.
A conflict check warns when the file changed on the server since it was opened, rather than overwriting it. This covers the case where a developer uploaded a change while a client still had the page open in the editor.
Together these mean a client can be given access to a real PHP file with a lower chance of breaking it than a shared FTP login would carry.
Globals, groups and menus
Three features handle content that lives in more than one place or repeats on one page.
The globals feature lets a phone number, address or tagline be marked once and updated everywhere in one save. For a site with the same footer repeated across many static pages, that removes the usual find-and-replace across files.
The groups feature turns repeated blocks, such as team members, services or cases, into a list that can be added to, reordered and removed from. A hand-built team page becomes a managed list without being rebuilt as a template.
The Menu tab adds, renames, changes the target of, or removes navigation links, and writes the result back into the header. Navigation is often the one piece of a static site that a client cannot touch at all; this tab makes it a form.
Connection to the server is over SFTP with key or password. Credentials are encrypted and never shown again after they are entered, so a client cannot read the server password out of the editor later.
Editor login uses a one-time emailed link that expires quickly. There is no password for a client to lose, reuse on another service, or write on a note.
There is also an AI access option via MCP. It connects Claude or another assistant to one site with a token at one of three permission levels. Any file can be hidden from the assistant, and access can be revoked at any time. This is the same file-editing surface the human editor uses, scoped by the token rather than by a separate integration.
Plans
There are two plans. The Free plan above includes the full editor, globals and groups, the menu, header and footer tabs, SEO tools, a cookie banner, backups, team access, and AI access via MCP. Nothing in the editing features listed earlier in this article sits behind a paid tier.
The Enterprise plan is listed as "Contact us" and priced per agreement. On top of Free it adds white-labeling, editor customisation, custom features, priority support and migration help. These are agency concerns: putting the agency's own name on the editor, adjusting it for a specific client, and getting help moving sites in.
Moving from Free to Enterprise later changes nothing for existing sites. An agency can connect its first client sites on Free and decide about white-labeling once it knows how many clients it will hand the editor to.
Where it is still limited
Clean URLs and redirects are the thin spot. There is no managed redirect table. Instead, redirects are handled as raw rules in .htaccess, which is edited directly in the Technical tab. A backup is taken before each save, so a bad rule can be rolled back, but the editor does not validate a redirect, list existing ones in a form, or help a client who has never seen an Apache rewrite rule. On a site with many redirects, that job stays with the developer for now.
Two other points are worth stating plainly from the fact sheet. The tool works on the files it finds over SFTP, so a site that is generated at build time or stored in a database is not the target. And the AI token is per site, which is a reasonable default but means a multi-site agency sets up access site by site.
What to check first
A sensible first step is to connect one existing HTML or PHP site on the Free plan, which asks for no card and has no time limit, and open a page to see which fields are detected automatically. Edit a single heading, confirm in the Code tab that the rest of the file is unchanged, and try the one-click restore. If the site is for a client who needs to update a phone number across every page, mark it as a global and save once. An agency that expects to hand the editor to several clients under its own brand can then compare that experience against the Enterprise additions before contacting sales.