Keep credentials out of browser files and control who publishes.
DeployBeacon inspects built files, scopes access to workspaces and projects, and requires human approval for MCP publication proposals. These controls support your publishing workflow; they do not certify the uploaded application as secure.
What file inspection checks
Checks include unsafe archive paths, symlinks, duplicate entries, size limits, sensitive filenames, recognizable embedded credentials, the document root and supported local asset references. Credential inspection runs locally without sending the candidate credential to a provider or showing secret values. Publication and preview promotion repeat the relevant checks.
Unknown, encoded or obfuscated secrets can be missed. Inspection is not a malware analysis or a complete application-security audit. Remove and rotate exposed credentials and rebuild before sharing the files. Never place a server secret in browser JavaScript.
Separate shared addresses from custom domains
Shared platform and preview addresses apply a restrictive Content-Security-Policy sandbox. Their browser origin is opaque: cookies, local storage and some APIs requiring a normal same-origin context are unavailable. A verified customer-owned custom domain serves at its own browser origin with normal storage support.
DeployBeacon's dashboard credentials do not grant access to a hosted application's separate backend. Protect any external APIs with their own authentication and authorization; hiding a URL or using a public client key does not establish permission.
Choose scoped access
Use your own invited account and select only the token scopes your tool needs. Keep tokens in a private environment variable, never in source control, public documentation or an uploaded ZIP. Review workspace membership and revoke tokens, assistant connections and sessions when access is no longer needed.
Available actions depend on workspace role and token permissions. Direct API or CLI deployment-write tokens can publish with explicit confirmation; only grant that access to a trusted workflow.
Review assistant proposals
A compatible MCP assistant proposes an exact publication or restore target. Review it in Agent approvals; the assistant cannot approve itself. The review and execution windows are time-limited, and the result is recorded. An expired proposal needs a fresh proposal rather than an assumed retry.
Handle private preview links carefully
A preview link is a bearer credential. Anyone who receives it can view the release until expiry or revocation. Keep private URLs out of public content and messages intended for wider audiences. Revoking a preview link does not erase previously downloaded files.
When a request fails
Retain the visible error code and reference ID so the operator can investigate. Do not include tokens, passwords, private URLs or secret values in a support request. Account security controls and activity history are available inside the invited workspace.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.