WordPress is great to edit. It is hard to host safely.
Sintr keeps the part everyone likes, the editor, and removes the part that causes the late-night emergencies.
Always online, always a target
A public login page and PHP on every request invite bots, day and night.
Visitors get files. There is no login page, PHP or database for them to reach.
Updates that cannot wait
When WordPress is public, every plugin and core patch is urgent.
WordPress sleeps between edits. Nothing public is waiting to be patched tonight.
Slow when it matters
Pages are assembled on every visit, and caching layers need constant tuning.
Pages are built once, at publish, and served as ready files with proper caching.
Edit. Publish. WordPress goes back to sleep.
Edit as usual
Open WordPress from your dashboard and it wakes up. Your editor, your theme, your plugins. Nothing new to learn.
Publish in one click
Sintr builds a complete static copy, wires up forms and search, and switches the site over in one step.
Visitors get the fast version
After 30 quiet minutes WordPress stops. Visitors keep getting the static site, and any earlier build is one click away.
Give every client a portal. Keep the keys yourself.
Run all your client sites from one place, in your own brand, and hand over exactly what each client needs.
- A login for every clientEach client sees only their own sites. They can publish, read form submissions and send site email from their own domain. Backups, settings and other clients stay out of reach.
- Your brand on itYour name, logo and colour on the dashboard and on the editing screen your clients see.
- Their own sign-inClients sign in with their Google Workspace, Microsoft Entra, Okta or Auth0 account. No extra passwords to manage.
- Start every site from your theme Coming soonKeep your starter theme in git, choose it per site, and Sintr installs it when WordPress starts. Git always wins, so nobody drifts off your code.
- Your team, with rolesOwners, admins and members. Destructive actions stay with admins.
| New enquiry: wedding cake | 2 min ago |
| New enquiry: catering for 40 | yesterday |
| Published: new opening hours | Monday |
Your AI tools can run your sites.
Sintr is built around an MCP server, so Claude, Cursor or any MCP client can do what the dashboard does: create sites, write and schedule content, deploy, roll back and back up.
- Connect at mcp.sintr.dev Coming soonPoint your AI client at one address with your personal access token.
- Scoped by tokenGive an AI session one team or one client, not everything. Revoke the token and it stops at once.
- Reaches into WordPress tooA bridge to each site’s own WordPress MCP server covers anything Sintr does not handle itself.
- Content as dataEvery publish can export your posts and pages as JSON and push them to GitHub, ready for a frontend built in Lovable or anywhere else.
create_contentdeploy_sitelist_deploysIllustration. The tool names are real; the conversation is an example.
Everything a static site usually loses.
Forms
Contact Form 7 and other forms keep working, with spam protection, file uploads, an inbox in the dashboard and an email or webhook for each one.
Search
Visitors can still search. Results are ranked, highlighted and shown inside your theme.
Backups and rollback
Daily or weekly backups, a version of every publish, and one-click rollback.
Mail from your domain
Form and site email sent from your own or your client’s domain, with the DNS records handled for you.
Previews for clients
Share a readable preview link, protect it with a password, and keep search engines away from it.
Scheduled publishing
Set a date and the post goes live on its own, even while WordPress sleeps.
This page is what your visitors would get.
It is served by the same static edge that serves Sintr sites.
Not another host. Not just an export plugin.
| Feature | Typical managed WordPress host | Typical static-export plugin | Sintr |
|---|---|---|---|
| What visitors reach | WordPress | Static files | Static files |
| WordPress running around the clock | Yes | Yes, on a server you run | No, only while editing |
| A login for each client, limited to their own sites | Rarely | No | ✓ Yes |
| Forms and search after going static | Not needed | Often a paid add-on | ✓ Built in |
| Your starter theme pulled from git | Varies | No | Coming soon |
| Run it from AI tools over MCP | Rarely | No | ✓ Yes, hosted endpoint coming soon |
A general comparison of categories, not of specific products. Features vary by vendor and plan.
What happens between an edit and a visit.
The whole path, from the editor to the browser
- One container or pod per site
- The database is a single SQLite file
- Stops after idle minutes; only real activity keeps it awake
- Crawls links, sitemaps, feeds, images and CSS
- Rewrites every URL to your public address
- Writes an immutable, versioned build
- Picks the site by its
Hostheader - ETags, gzip and cache headers
- No PHP and no database on the public path
Going live switches to the new build in one step, and rolling back points the edge at an earlier one. Sign-in to WordPress uses a short-lived signed statement from the admin gateway, so there is no second login.
What Sintr does not do
No PHP runs while a visitor is on the page, so carts, member areas and live comments are not supported. WordPress multisite and plugins that run raw SQL on SQLite are not supported either. Bring those as an external WordPress origin instead.
Questions agencies ask first.
Will my theme and plugins still work?
Your theme is published exactly as it renders. Plugins that shape what a page looks like or contains generally work. Anything that needs PHP while a visitor is on the page, such as carts, member logins or live comments, does not run on a static site. Forms and search are replaced by Sintr’s built-ins. WordPress multisite and plugins that run raw SQL are not supported.
What happens to WordPress between edits?
It stops after a period without real activity (30 minutes by default) and starts again when someone opens it from the dashboard. Visitors never notice: they are served the static site the whole time.
Can my clients break anything?
A client login only sees that client’s own sites. Clients can publish, read form submissions and set up email from their own domain. Backups, settings and other clients stay out of reach, and every earlier build is one click away.
Where are sites hosted?
In the EU, on Google Cloud in Finland, with HTTPS certificates from Let’s Encrypt.
Do I need git or AI tools to use Sintr?
No. The dashboard and WordPress are all you need. AI tools over MCP and themes from git are there when you want them; both are rolling out.
How do forms and search work without PHP?
Forms post to Sintr’s edge, which keeps the submissions in your dashboard and sends an email or a webhook for each one. Search runs from an index built with every publish, and results appear inside your theme.
Keep WordPress for editing. Give visitors the fast, safe version.
Your sites, your clients and your AI tools, in one place.