Technology Architects
Work  /  Websites

Websites with nothing to patch

Two business websites moved from WordPress to static pages. With no database, no admin sign-in and no plugins, there's no software on the site to patch.

Two businesses we host · 2026

Pages Plain HTML and CSS Images in several sizes No database, no admin sign-in, no plugins Deploy script Unlock Publish Lock On the server Files owned by the system, not by the web server Locked against changes Before and after: check the cloud Shared web space, scoped rules The site The firm's cloud
One release of a static site. Explanatory, not a server map.

What we built

Each site is plain HTML and CSS, with images in several sizes so phones download less. On the server, the files belong to the system rather than to the web server, and they're locked against changes. The deploy script unlocks them, publishes, and locks them again.

One site runs no scripts, has no forms and makes no requests to other sites, and a strict content security policy holds it to that. The other shares its web space with the firm's file-sharing cloud. Its rules are scoped so they can't affect the cloud, and a check before and after each release confirms that the cloud still answers exactly as it did.

How it holds up

Each site publishes with one command. Between releases there's nothing on the site to update and nothing to sign in to.

Need something like this?

Tell us what you’re working on. You’ll get a straight answer on whether we’re the right firm for it.

Start a conversation