The contact form backend problem every standalone site hits
You chose static hosting for speed and cost. Then you needed a contact form. This is the gap Reachase was built to close.
Leif Andersson · Founder
Standalone sites, the kind that are not part of a larger app, share a common arc. You pick a static site generator or a simple framework. You deploy to free hosting. The site is fast and costs nothing. Then someone asks for a contact page.
That single feature forces a decision that affects hosting, cost, and maintenance for the entire project.
The three bad options
Most teams pick one of these and live with the downsides:
- Add a backend. Spin up a VPS or serverless API just for forms. Now you pay monthly and monitor uptime for a five-page site.
- Use mailto: links. Free, but spam-prone, no submission history, and poor UX on mobile.
- Embed a third-party widget. Works, but iframes break your design and feel outsourced to visitors.
What a standalone site actually needs
The form backend should be a service, not part of your site infrastructure. Your pages stay static files on a CDN. Submissions go to a dedicated system with spam filtering, notifications, and an inbox you can search later.
That is the model Reachase is built around. One embed on your contact page. One dashboard for your team. No servers on your hosting bill.
For small sites
Most websites are small: portfolios, local businesses, agency client sites, early MVPs. They do not need Kubernetes. They need a reliable way for strangers to send a message.
Reachase keeps those sites fully static while handling spam filtering, rate limits, and searchable submissions. Deploy anywhere for free. Pay only when you outgrow the free tier.