Static website hosting, with a way back.
DeployBeacon publishes built HTML, CSS and JavaScript. Upload your finished website, inspect its files, create a private preview and choose when to publish a release.
Who is it for?
Developers and people building websites with AI who already have a finished static build. It fits landing pages, portfolios, documentation and frontend applications that can be served as browser files. Bring the output from your existing tools; DeployBeacon does not build or run customer source code on the hosting server.
A frontend that calls an external API still depends on that API's availability and browser permissions. Keep server credentials in the external backend. Check whether your build is suitable.
From upload to a live address
- Create a project and upload a ZIP containing built files.
- Review the document root and inspection findings.
- Create a private preview if you want to review before publishing.
- Confirm publication, then open the returned website address.
- Connect a domain you own when you need a normal website origin.
Publishing prepares a candidate release and checks its HTTP response before selecting it for visitors. Test your own links and interactions too; that check does not exercise every website feature.
What stays with your project?
Inspections, release history, publication results and an activity record. Retained successful releases can be restored without rebuilding. You can download the original uploaded ZIP and manage website files through the dashboard. Editing files prepares a new inspection; publishing remains a separate decision.
Contact messages without customer server code
Add a native HTML form to a published static website and receive its declared text and email fields in a workspace inbox. Configure a disabled receiver, copy its snippet, publish the website update and enable it. Authorized developers, admins and owners can read messages, archive and restore them, and export CSV. Files and outgoing email delivery are not supported. Set up a contact form.
Own domains and HTTPS
Add a published project to a domain you own using the A and ownership TXT records shown in the workspace. After DNS and ownership checks pass, the service requests HTTPS and connects the domain. The beta uses DNS-only IPv4 routing. See the supported domain workflow.
What is outside the beta?
Customer Node or Python processes, PHP, server-rendered applications and managed customer databases. Source-only repositories must be built before upload. Dynamic runtime hosting, self-service billing and automatic Git push deployments are not available. Workspace allowances are visible and enforced.
Shared preview and platform addresses use a browser sandbox with restricted storage. Verified customer-owned custom domains have their own browser origin. Understand those boundaries before choosing your hosting route.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.