A headless CMS with your own database and storage.
Keep each website’s content in its own PostgreSQL and its files in its own S3-compatible bucket. Move them there, and back, any time, with the site online and every link the same.
Your database
Your PostgreSQL. Every record, only there.
Connect a PostgreSQL database and the website’s content moves into its own schema, ready to query, back up and keep for as long as you need. Each website’s own database comes with the Agency plan.
What moves there
- Pages and sections
- Items of every page with many items
- Releases and their history
- Media records
- Forms and leads
- Website analytics
Backups are yours. Once the move finishes, mywebcms keeps no copy and no backup. If data is lost from that database, mywebcms can’t restore it.
What it needs
- PostgreSQL 14 or newer
- A managed service or your own server, reachable over the internet.
- A login for mywebcms
- One that can use only its own schema, mywebcms by default.
- An encrypted connection
- SSL required, or required with the certificate verified.
-- Run as an admin of your databaseCREATE ROLE mywebcms LOGIN PASSWORD 'choose-a-strong-password';GRANT CONNECT ON DATABASE your_database TO mywebcms;CREATE SCHEMA IF NOT EXISTS mywebcms AUTHORIZATION mywebcms;
Admin shows this setup for your database’s name, and tests the connection before anything is saved.
Your storage
Your bucket. The same file links.
Point the media library at your own S3-compatible bucket: new uploads go there, on your bill, with no storage quota from us. Your own bucket comes with every plan.
- Amazon S3
- Cloudflare R2
- DigitalOcean Spaces
- Backblaze B2
- Wasabi
- Any S3-compatible
Tested before it's saved
Saving unlocks only after a real test with your keys: reach the bucket, upload a file, read it back, delete it.ReachUploadReadDeleteKeys stay secret
The access key and secret are encrypted and never shown again; admin shows only the last four characters.••••7Qd2Links never change
Every file is served from the mywebcms files address, wherever it's stored, so moving a bucket never breaks an image.…/hero.jpg=…/hero.jpg
No bucket CORS to set up: uploads go through the API, so the bucket can stay private.
Moving
Move any time, both ways, with the site online.
Connect your own database or bucket on day one or years later, and move back whenever you like. Every move follows the same four steps.
- 1
Test
Nothing is saved until the connection passes: five checks for a database, four for a bucket.Connection test - 2
Copy
Content copies in the background while the site keeps answering. Editing waits until the move is done.Copying your content - 3
Check
Every table's records are counted on both sides. If anything is missing, nothing switches.Checking every record arrived - 4
Switch
One switch and the website reads from its new home, everywhere at once. Files move in batches instead, with Pause and Resume.Switching your website over
FAQ
Questions about your data.
Where it lives, who keeps the backups, and how it moves.
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.