Notes

Why a site without a database is safer and cheaper

Most small sites, like a clinic, a lawyer, a portfolio or a product page, keep their pages in a database only because the system they run on was built that way. The database does not make the site better for visitors, but the owner pays for it every month in updates, risk and hosting.

Here is what a database costs a small site, what you lose without one, and how to tell whether your site really needs it.

How a usual site answers a visitor

A site on WordPress or a similar system keeps its texts in a database. When someone opens a page, the server runs a program in PHP, asks the database for the text, puts it into the template and only then sends the page. This happens on every visit, for every visitor, even though the page has not changed for months.

A static site does that work once, when you publish. The pages are ready files, and the server only sends them. What a static site is

What the database costs

Updates that never end

The system, its plugins, PHP and the database each get updates. Skip them and the site becomes vulnerable; install them and something may break.

Static site: The server sends files. There is no program on it to update besides the web server itself.
In numbers of tasks: A typical small WordPress site has a core, a theme and ten to twenty plugins, each with its own updates.
What remains for you: With the image, updating HERON means changing one line in site.yaml when you want to, not when a plugin forces you.

A door for attacks

Most break-ins on small sites go through an outdated plugin, the admin page or a request that tricks the database. The site does not have to be famous: robots scan everything.

Static site: No admin page, no database, no PHP on the server. There is nothing to log into and nothing to trick.
The image: Holds only finished pages and nginx; the build tools and your source files never reach the server.
If you add data: The optional database module talks to the site over a private key; the page only reads or sends requests, and nothing can be injected into the built container.

Hosting that grows with traffic

Every visit runs a program and a database query, so a busy day needs a stronger server or a cache that someone must configure.

Static site: Files can be hosted for free on GitHub Pages or Cloudflare Pages, or on the smallest server, and a busy day costs nothing extra.
One server, many sites: A small VPS from about €5–6 a month serves several static sites at once. Where a site can live

Speed on a phone

A page that is put together on every visit is slower to arrive, and slow pages lose visitors and positions in search.

Static site: The page is ready before the visitor asks. A new HERON site scores 100 for performance in Lighthouse on mobile, with a 3 KB home page.
Pictures too: HERON cuts every photo into WebP and AVIF sizes, so a phone downloads a small file, not the original.

What you lose

Things a static site does not do by itself

An admin panel in the browser where you click «Edit»
Comments, user accounts, a shop with a cart
Search inside the site without a small script or an outside service
Forms that save requests without a helper service

How these are covered

Pages are text files: any editor, a configurator for settings, or an AI agent that edits them for you
Comments and shops live in services made for them and plug into the page
Search can work in the browser from a ready index
Forms go to email or a CRM through a small helper, or into your own database through an optional database module

When a database is really needed

A database earns its cost when the content changes by itself, many times a day, or is different for each visitor: an online shop with stock and orders, a forum, a personal account, a booking system with live slots. For those, choose a system built around a database, or put the live part into a separate service and keep the rest of the site static.

For a site that changes only when you edit it, like services, prices, articles, contacts or a portfolio, a database is a cost without a benefit.

How HERON does it

HERON keeps the site as a folder of text files and builds ready pages from it: with search settings, translations, sitemap, schema.org and llms.txt. You publish with one git push or by copying a folder.

If one part of the site needs live data, such as a booking calendar, you do not have to move the whole site onto a database. HERON connects a database through an optional module: the live block reads it over a private key, and every other page stays a ready file. Flat-file CMS without a database · Database module

Questions

Is a static site safe from hacking?

There is far less to attack: no admin page, no database, no PHP. The server and your accounts at GitHub or the hosting still need good passwords and two-factor sign-in.

Can I edit a static site without a programmer?

Yes. Pages are plain text files, and the configurator explains every setting next to its field. Many people let an AI agent make the edits.

Can I move my WordPress site?

Yes. Move the texts into pages and list the old addresses in each new page. HERON writes real 301 redirects, so search rankings move with the pages.