Speed and hosting
Fast pages from one binary and one database.
Hatamoto is a single Go program next to PostgreSQL, with a page cache in memory. There is no PHP and no Node to run alongside it.
A fast site usually means a stack of caching add-ons.
Caching, image tools and hosting tweaks pile up as plugins and services. Speed should be part of the CMS.
What you get
-
A page cache in memory
Public pages are kept in the server's memory, so a repeat visit is answered in a few milliseconds instead of being built again.
Page cache guide -
You set the lifetime
The default is 5 minutes, and you can change it from the environment or the admin.
-
Modern images
Uploads get WebP and AVIF copies. Replace a file and the resized copies are rebuilt.
-
One thing to host
Run one binary and one PostgreSQL database, with Docker or systemd.
Deploy with Docker -
Light pages
The default theme is plain server-rendered HTML.
-
Health checks built in
/health and /ready answer for your load balancer or container platform.
Under the hood
-
What is not cached
Previews, requests with a query string and pages that failed to render.
-
Cache needs a public address
Set PUBLIC_BASE_URL, or nothing is cached.
-
Cache starts empty
It lives in the server process, so a restart or deploy clears it.
Questions people ask
What do I need to run it?
A server that can run one binary, and PostgreSQL. No PHP or Node.
How fast is it?
That depends on your server and your theme. Measure your own site, and treat any number you did not measure with care.