Welcome to LaunchVerseQuickstartDashboard OverviewImporting Projects
LaunchVerse ForgeScale-to-ZeroEnvironment Variable VersioningRollbacks & PromotionsPreview Environments
Helix CopilotEphemeral SandboxesAI Log Explainer
The LaunchVerse EdgeCustom Domains & TLSDomain PurchasingTwo-Factor Authentication (TOTP)IP Allowlists
Managed DatabasesDatabase Backups & RestoresLog DrainsObservability
Project GroupsRole-Based Access Control (RBAC)
Student ProgramDeveloper Streaks
AuthenticationProjectsDeploymentsDomainsDatabasesError Codes & Conventions
Changelog
Deployment GuideEnvironment Variables & SecretsTeam ManagementWeb ShellHow Builds Work (Forge)
JavaScript SDKPython SDK
API Reference (Redoc)

The LaunchVerse Edge

Every application deployed on LaunchVerse is automatically distributed and protected by the LaunchVerse Edge Network, powered by an enterprise-grade global Anycast network.

Automatic Edge Caching

When you deploy a static site, a Next.js application with ISR (Incremental Static Regeneration), or any application that returns valid Cache-Control headers, LaunchVerse automatically caches your responses at over 300 Edge locations globally.

This means a user in Tokyo requesting your site will be served instantly from the Tokyo Edge node, rather than waiting for a response from your primary engine server in Ashburn, Virginia.

Edge Security & Firewalls

You do not need to configure complex Web Application Firewalls (WAF). The LaunchVerse Edge natively includes:

    1. DDoS Mitigation: Automatic layer 3, 4, and 7 DDoS protection. If a massive attack occurs, traffic is scrubbed at the Edge before it ever reaches your container.
    2. Bot Protection: LaunchVerse integrates Turnstile and intelligent JS challenges to block scrapers, spammers, and malicious bots from hammering your APIs.

Edge Analytics

Because all traffic flows through the Edge, LaunchVerse can provide you with deep, privacy-respecting observability without injecting tracking scripts into your frontend.

Navigate to the Observability tab in your project to view:

    1. Global traffic heatmaps.
    2. Bandwidth consumption and cache hit rates.
    3. Error rates (4xx and 5xx responses).
    4. Top referrers and request paths.

> [!TIP]

> If you are experiencing a sudden traffic spike and want to ensure maximum cache hit rates, verify that your application is emitting Cache-Control: s-maxage=86400, stale-while-revalidate headers. LaunchVerse Edge natively respects stale-while-revalidate for zero-downtime cache invalidation.

Edit this page on GitHub↗