Model Edit Release
One CMS for every website you build.
Design each site your own way. mywebcms gives your clients one simple place to change every word, image and form, and delivers it to any frontend over a fast API.
- Works with any tech stack
- Development and Production
- Access per team member
AI importBeta
Show us the design. Get the API.
Drop in a screenshot or a page URL. mywebcms reads it and proposes the sections, fields and content, and you review every one. Create the page, and it has its own API, ready for whatever frontend you build.
Every part of the design becomes a section you review.
Find what's on this page
Sections, fields and content, from the design alone.
The usual headless CMS
- 1Plan the content types on paper
- 2Create every field by hand, one at a time
- 3Copy the text in, section by section
- 4Upload and attach every image
- 5Look up the API and wire it to your frontend
…and only then does your frontend get its first field.
With mywebcms
- 1Drop in a screenshot or a page URL
- 2Review the sections and fields it found
- 3Create the page. Its API is ready
Your frontend can call it straight away, in Development.
How it works
You build the frontend. Your clients run the content.
mywebcms is a CMS for agencies and developers who build custom websites. Focus on the frontend: there is no backend to build or maintain. Your clients keep every word up to date, and changes go live through a release you control.
Build
Build your frontend, then connect it
Design the site your way, with no backend to write. Give each page the fields your design needs, like a tour's title and price, then swap your hardcoded text for one API call.
Edit
Your client fills it in
Clients change text, images and prices in one simple editor. They work in Development, so nothing reaches the live site by accident.
Release
Release it to Production
Group changes into a release, review it and merge. Your site reads the new content as JSON from the API, whether it runs on Next.js, PHP or plain HTML.
One account
Every client website, one account.
Sign in once and run every site you build for clients. Each website keeps its own pages, content structure, team and API keys, so clients only ever see their own.
How multi-site worksForms & leads
Every enquiry lands as a lead.
mywebcms does more than manage content. Every form on your client's site sends its enquiries straight into their leads, with the page and campaign each one came from. Their team picks it up, calls back and logs every step, so no enquiry slips through.
Clear statuses
Every lead moves through the same six statuses on every website, so nothing sits in limbo.NewContactedQualifiedWonLostSpamOwners and follow-ups
Give each lead an owner, a priority and a follow-up date. Overdue follow-ups stand out.PRTomorrow, 11:00OverdueEvery touch logged
Log calls, WhatsApp chats, emails, meetings and notes. The history is kept as it happened, never edited.CallWhatsAppEmailMeetingNoteExport, without the spam
Export any filter to CSV. A honeypot, rate limits and an optional CAPTCHA keep junk out.CSVHoneypotRate limitsCAPTCHA
Developers
Your stack. Our API.
Every page, section and form arrives as plain JSON over HTTP, so you build each site in whatever you like: Next.js, React, Vue, PHP, Laravel, WordPress or plain HTML. No SDK to install, no framework to adopt.
// A server component: the key never reaches the browser.export default async function Home() { const res = await fetch(`${process.env.MYWEBCMS_API_URL}/pages/home`, { headers: { Authorization: `Bearer ${process.env.MYWEBCMS_API_KEY}` }, next: { revalidate: 60 }, }) const { data } = await res.json() return <h1>{data.sections.hero.values.title}</h1>}
{ "data": { "page": { "title": "Home", "slug": "home", "seo": { … } }, "sections": { "hero": { "key": "hero", "kind": "content", "values": { "title": "Built for you, kept up to date by you", "button_label": "Get in touch", "button_link": "/contact" } } } }}Same request, same JSON, whatever you build with.
Pages by address
Ask for any page by its address and get its SEO and every section. A page with many items comes as a list you can filter, sort and page through.GET /v1/pages/about200Forms that validate
Send a form's fields as JSON. You get the success message back, or a clear error for each field that needs fixing.POST …/contact-us/submit422 · emailLocked to your domains
Each key belongs to one website and one environment, and browsers can only call it from the domains you allow.yourclient.comother-site.com
Your data
Your content. Your database.
Start on our database and storage. Whenever you or your client want the data in-house, move a website's content to your own PostgreSQL and its files to your own bucket, or back again. The site stays online, and every link keeps working.
Move any time, both ways
Every website can move on its own, whenever it's ready. Changed your mind? Move it back.mywebcmsYoursThe site stays online
Content and files are copied in the background and checked before the switch. Visitors never notice.Site onlineLinks never change
Page addresses and file URLs stay exactly the same, wherever the data lives./team-photo.jpgunchangedYour keys stay locked
Database passwords and bucket keys are encrypted and never shown again after you save them.••••a7f2
Sign-ins, team access and settings always stay with mywebcms, and files are served from the mywebcms files address wherever they're stored.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.