Skip to content

Static site, dynamic data: the parts of a site that still need a backend

A static site can do almost everything a website needs. Here is what still needs a backend, and why a contact form should not be the reason you build one.

• Sunil Kumar
A small team working on laptops around a table, with the title Static site, dynamic data and the PaceForms logo

TL;DR

  • Static sites are fast, cheap and safe, but they cannot store anything a visitor sends.
  • Real backends are still needed for logins, payments, comments and data that changes all the time.
  • A form is the odd one out. Building a whole backend for one contact form costs weeks of work and a monthly server bill, even in months when nobody writes to you.
  • A form API does the job instead: your own HTML form, your own fields, your own thank-you page, with storage, spam filtering and notifications handled for you.
  • Speed of reply matters more than the tool. A lead you answer a month late is a lead you have already lost.

What a static site does well, and where it stops

A static site is a set of ready-made files: HTML, CSS, JavaScript and images. A server, or more often a CDN, hands those files to every visitor exactly as they are. Nothing is built on the fly.

That gives you a lot for very little:

  • Speed: the pages are already built, so they load fast.
  • Low cost: many hosts serve static files for free or close to it.
  • Fewer things to break: no database and no server code means much less to attack and much less to patch.

The limit is simple. A static site can show data, but it cannot keep data. The moment a visitor sends you something, like their name, a comment, an order or a message, that data needs somewhere to go. That “somewhere” is a backend.

The parts of a site that still need a backend

Not every dynamic feature is equal. Some truly need a server you control. Others only need storage and a way to tell you that something arrived.

Chart of website features and what each needs: pages, blog and docs need nothing; site search can be built as a static index; forms can use a form API; comments, payments and logins need a backend

Here is the pattern:

FeatureNeeds a backend?Why
Pages, blog, docsNoThe content is known when the site is built
Site searchOften noA search index can be built with the site and searched in the browser
Contact and lead formsYes, but not your ownSomething must store answers and notify you; a form API does that
CommentsYesOther visitors must see new data, and someone must moderate it
PaymentsYesPrices and payment results must be checked on a server, never in the browser
Logins and accountsYesPasswords, sessions and private data must stay on a server

If your site sells, has members, or lets people talk to each other, you will need a real backend sooner or later. But if the only dynamic thing on your site is a form, building a backend for it is a poor business decision. It is like renting a warehouse to store one letter.

Websites exist to bring in leads. A site that makes it hard to capture them is failing at its main job. So the question is not whether to capture leads. It is how to do it without taking on a server you do not need.

A founder’s story: one form, one backend, months of work

This is what happened when I needed a contact form for my own company website.

My analytics showed people visiting the contact page, trying to send a message, and leaving. The form was not working. I did not look for a tool. I did what developers do and built one myself:

  1. I wrote a backend to receive and store the form answers.
  2. I bought a server and deployed the backend on it.
  3. I connected the form on my static site to that backend.

A few months later I noticed something worse. I had never checked the submissions. They were sitting in a database nobody looked at. So I built a dashboard to read them. Then I added a notification channel so I would hear about new ones. Then I had to look after the credentials, the server and the updates.

All of that for one form, and the server bill came every month whether anybody wrote to me or not.

Two paths for one contact form: building your own backend takes six steps that never end, from writing code to maintaining a server; a form API takes four steps and then it is done

When I finally looked at form tools, most were either paid or forced their own look onto my site. They gave me an iframe or a widget with their branding and styling. I tested a few locally, and they simply did not look like my website. That is why I switched to a form API, where the form is mine and only the data handling is theirs.

How a form API works on a static site

A form API turns the hardest part of a form, the server side, into a single address. Your form stays plain HTML on your own page. When someone presses Send, the browser posts the answers to that address.

How a form API works: a visitor fills in your own form, it posts to your form endpoint, the submission is stored in your inbox, you are notified by email, Slack or Google Chat, and the visitor sees your own thank-you page

With PaceForms, setting one up looks like this:

  1. Create a form in your dashboard. It takes a few clicks.
  2. Copy its endpoint. Every form gets its own unique, permanent address.
  3. Build the form your way. Write the HTML yourself, or give the endpoint to an AI assistant and ask it to write a form with the fields you want in your site’s style.
  4. Deploy your site. When the page goes live, the form is live.

That is the whole setup. There is no server to rent, no database to run, no email service to wire up and nothing to patch later. The plain HTML guide shows a complete working form in a few lines.

Your fields, your design, your thank-you page

The best part of a form API is what you do not have to do. You do not have to define every field in a builder first.

Any field your form sends is stored. Add a “Company size” dropdown today and a “Budget” field next week. Change your HTML, deploy, and the new fields simply appear in your submissions.

You also keep full control of the look:

  • The form matches your site, because it is your own HTML and CSS. No iframe, no foreign fonts, no logo you did not ask for.
  • The success message is yours. You are not stuck with a platform’s generic “Thanks!” screen. Send people to your own thank-you page, or show a message in your own JavaScript.
  • The next step is yours too. A thank-you page can say “Our team is reviewing your request and will reply soon”, link to your case studies, or offer a booking link.

This is where many hosted form tools fall short. They are quick to embed, but the moment a visitor fills in your contact form, they land on someone else’s design. For a company website, that break in look and feel costs trust. If you are comparing options, see how a form API differs from an embedded form builder in PaceForms vs Tally.

Time is money: get notified the moment someone writes

Storing submissions is only half the job. The other half is knowing about them.

Picture this. You build websites for clients. Someone fills in your contact form to talk about a new website. You have no notifications set up, and you check your submissions a month later. You write back, and they reply that they already started with another agency. The lead was real. Your reply was just too late.

That is why notifications are not a nice extra. They decide whether a lead turns into a client. Quick notice also gives you time to prepare: you can read the request, look at the person’s current site and come to the first call with a rough proposal already in hand.

PaceForms can notify you in the places you already watch:

  • Email for every new submission
  • Slack and Google Chat, for the team channel where someone is always around

Spam and security, handled for you

Any public form attracts bots. They fill in forms far faster than a person can, stuff them with links and junk, and send them again and again.

A form API handles this at the endpoint, before junk reaches your inbox. With PaceForms you get:

  • A honeypot field: a hidden field people never see but bots fill in. Any submission with it filled is dropped.
  • Cloudflare Turnstile: an optional check that tells people from bots, usually without making anyone solve a puzzle.
  • Rate limits: a cap on how many submissions one form takes in a short time, so a flood cannot bury real messages.

Submissions travel over HTTPS and are stored by the service. One simple rule still applies to any contact form: do not ask for passwords, card numbers or other sensitive data in it.

The trade-offs, honestly

A form API is not magic. It is worth knowing what you give up.

  • Your data lives on someone else’s system. It is stored securely, but it is still a third party. Pick a service you trust and read its privacy policy.
  • If the service is down, a submission can fail. Plan for it. Show a clear error message, and keep a plain email address or other contact details next to the form. A visitor who really wants to work with you will use them.
  • You should be able to leave. Make sure you can get your data out. PaceForms lets you export submissions as CSV and send each new one to your own URL with a webhook, so your sheet or CRM can keep its own copy.
  • Test entries pile up. Submit the form yourself before launch to check it works, then delete the test submissions from your inbox.

None of these is a reason to build your own backend. Your own server can go down too, and then you are the one who has to fix it.

Who should use a form API

A form API fits anyone who has a static site and needs to hear from visitors, but does not want to run a server for it:

  • Developers and founders who would rather not pay for a backend that does one thing
  • Agencies that build sites for clients and do not want to deploy and look after a backend for each one
  • Indie founders launching a landing page or a waitlist
  • Portfolio owners who want a simple “hire me” form
  • Students and hobby builders who want their project’s form to actually work

When you really do need your own backend

Use this simple test. Build or rent a real backend when your site must:

  • Know who the visitor is, with logins, accounts or private pages
  • Take money, where amounts and results must be checked on a server
  • Show visitors each other’s data, like comments, reviews or a community
  • Run your own logic on every request, beyond storing it and telling you

If none of these is true and your only dynamic need is “people send me things”, you do not need your own backend. You need a form endpoint.

FAQ

Can a static site have a working contact form?

Yes. The form is plain HTML on your page, and it sends its answers to a form API endpoint. The endpoint stores the submission and notifies you, so your site needs no server of its own.

Which parts of a website still need a backend?

Anything that must store or check data on a server: logins and user accounts, payments, comments, and search over data that changes often. Forms also need one, but a form API can be that backend for you.

Do I have to define every form field in advance?

Not with a form API like PaceForms. Every field name your HTML form sends is stored as a field, so you can add or change fields in your own code.

Can I use my own thank-you page instead of the platform's?

Yes. Send people to your own page after they submit, or handle the answer in your own JavaScript and show your own message in your own design.

What happens if the form service is down?

The submission fails and your page should say so. Always show a plain email address or another way to reach you next to the form, so a serious lead can still contact you.

Is a form API secure enough for business leads?

Submissions travel over HTTPS and are stored by the service. Spam protection such as a honeypot field, Cloudflare Turnstile and rate limits keeps bots out. Keep sensitive data like passwords or card numbers out of contact forms.

Resources