Static
The server hands over a file that already exists. Nothing is assembled and no database is queried, which is why it is fast and why there is almost nothing to attack. Hosting can cost very little.
Agencies here quote both and rarely explain the difference in terms that help you choose. It is a business decision about how often things change and who changes them.
A static website serves ready-made files: fast, cheap to host, and very hard to compromise, but changes need someone who can edit files unless a CMS is layered on. A dynamic website builds pages from a database, which you need for logins, search, frequent publishing or content that differs per visitor.
The server hands over a file that already exists. Nothing is assembled and no database is queried, which is why it is fast and why there is almost nothing to attack. Hosting can cost very little.
The page is built when requested: query the database, apply the template, send the result. That is what allows logins, search, and content that changes without anyone editing a file.
Most static sites today are generated rather than hand-written. A generator takes content from a CMS and builds every page in advance, so you get static speed with a real editing interface. This is our default for content sites without logins.
How often content changes, who changes it, and whether you need accounts or search. Not which sounds more advanced, which is how the choice is usually made here.
Static hosting is dramatically cheaper and needs almost no maintenance. Dynamic sites need a server, a database, updates and security attention. Over three years that difference is real.
A static site has almost no attack surface. Most compromised business sites in this market are unmaintained dynamic installs, which is a maintenance problem rather than a platform one.
| Your situation | Better answer | Why |
|---|---|---|
| Five pages, rarely changes | Static or generated | Fast, cheap, nothing to maintain |
| Publishing weekly | Dynamic or generated with a CMS | Your team needs to publish without a developer |
| Customer logins | Dynamic | Accounts need a database |
| Search across many pages | Dynamic, or static with a search service | Depends on volume |
| Online store | Dynamic or a platform | Carts and inventory are inherently dynamic |
| Content differs per visitor | Dynamic | That is the definition |
| Very low budget, simple needs | Static | Cheapest to build and to run |
The common mistake is choosing dynamic by default because it sounds more capable. Capability you do not use is cost and attack surface you pay for anyway.
| Ask them | A good answer sounds like | Walk away if |
|---|---|---|
| Who owns the code and files? | You do, unconditionally, in the contract | Ownership depends on staying with them |
| Can I open three sites you built? | Live URLs you can check yourself | Screenshots and a portfolio PDF |
| Who maintains it after launch? | A named arrangement agreed up front | Nobody has thought about it |
| What is explicitly not included? | A written list with change pricing | Everything is included, which means nothing is defined |
The maintenance question matters most on custom stacks, because unmaintained bespoke code ages faster and more dangerously than a platform.
In this market this frequently means a small hand-coded site with no CMS. Confirm whether you can edit it yourself, because often the honest answer is no.
Usually means WordPress or a PHP admin panel. Ask which, because a bespoke undocumented admin is a very different proposition from WordPress.
Can my team change prices and add a page without calling you? That single question resolves the choice faster than any discussion of the terms themselves.
A static site serves files that already exist, so it is fast and cheap to host. A dynamic site builds each page from a database when requested, which is what allows logins, search and content that changes without editing files.
For a small brochure site that rarely changes, static or statically generated is cheaper, faster and safer. If you publish regularly or need your team to update content, you need a CMS, which usually means dynamic or a generated site connected to one.
Yes. Form handling is done by an external service or a small function. You do not need a dynamic site for forms, and this is the most common misconception in these conversations.
To host, dramatically, and it needs almost no maintenance. To build it is broadly similar. The saving is mostly in what you pay every month afterwards for three years.
Not inherently, though static sites tend to be faster and speed is part of page experience. Search engines care about content, structure and links. A well-built dynamic site ranks identically.
Only if it was built with a CMS layer, which modern static setups include. Ask this directly before agreeing to a static package, because a hand-coded static site with no CMS means calling someone for every change.
Static, considerably, because there is almost no attack surface. Most compromised business sites we are asked to clean up are unmaintained dynamic installs, and the vulnerability is nearly always a known one in an outdated plugin.
Send us what you are trying to fix and we will tell you what it takes, what it costs, and whether we are the right people for it. If we are not, we will say so.