Replace your plugin stack
Ten things you add to WordPress are already in the box.
Builder, SEO, redirects, caching, security and more ship in core, under one licence, with nothing to install or keep patched.
Every plugin is another update, another conflict and another thing to trust.
A typical site collects plugins for jobs the CMS should do itself. Each one has its own schedule, its own settings and its own failures.
| You usually add | In Hatamoto core |
|---|---|
| Page builder | Visual builder |
| SEO plugin | Titles, canonical, noindex, social tags, sitemaps |
| Structured data plugin | JSON-LD from the entity |
| Redirect manager | Redirect rules and a 404 log |
| Page caching plugin | In-memory page cache |
| Security plugin | Private admin address, two-factor and rate limits |
| Maintenance mode plugin | Coming soon, maintenance and password modes |
| Tag manager plugin | Tracking tags and a consent banner |
| Update manager | Signed automatic updates with rollback |
| Crawler analytics add-on | AI analytics |
What you get
-
One thing to update
Core, the builder and these features update together and roll back together.
-
One set of docs
Each feature is documented in the same place and works the same way.
Read the docs -
Open source core
The core is Apache 2.0.
Questions people ask
Does Hatamoto have every plugin WordPress has?
No. Shops, comments and many niche plugins have no equivalent. See what is not imported before you decide.
Can I still add plugins?
Yes. Hatamoto plugins run in a sandbox, and the plugin SDK is below 1.0, so its API can still change.