Keep your frontend.
Use Astro, plain HTML or your preferred static generator. Keep the form and its design in your own code.
CONTACT FORMS FOR AGENCIES & FREELANCE DEVELOPERS
Keep your frontend. At launch, Site Services will validate and store requests and notify you by email. One shared backend, without a separate form handler to build and maintain for every client.
Validated against your rules
The complete contact-form flow at launch: API, storage and email notifications.
LESS INFRASTRUCTURE. MORE CRAFT.
A custom form handler for every client means maintaining validation and storage again and again. Keep each site’s frontend and reuse the backend with Site Services.
Use Astro, plain HTML or your preferred static generator. Keep the form and its design in your own code.
Set up fields and validation rules for each project with us during personal onboarding.
Use the same server-side validation and storage across client sites instead of maintaining separate form handlers.
INDEPENDENT BY DESIGN
Built for agencies and freelance developers delivering static client sites. Separate client workspaces and test/live environments keep each project’s configuration and requests apart.
INTEGRATION
Your form sends requests through a same-origin proxy on your website. This hosting setup is required; we review it with you during onboarding. Start with the Astro guide or explore the API.
FOUNDING ACCESS
Bring a client project. We’ll discuss the form, personal setup and pilot terms together, including how requests reach the responsible person before launch.
Request early accessNo. Your site remains yours. Site Services provides a contact form backend for your own frontend.
That is who we are building for. Request early access with a project in mind; together we’ll review the form setup and required follow-up workflow before any client go-live.
Server-side validation and storage are implemented. We configure fields and rules with you. The complete contact-form flow — API, storage and email notifications — is committed for launch; operational email setup is pending. An inbox, webhooks and native waitlists are planned separately. Request access to discuss a pilot, not to activate an account immediately.
No. It requests a personal discussion about fit, setup and terms. Access is by invitation; the request does not confirm a pilot, a start date or a price.
YOUR NEXT PROJECT
Tell us where a form backend would help. We’ll get back to you personally.
hello@squibble.ch