The marketing site (executor.sh) is a high-performance, SSR-enabled web application built with Astro and deployed on Cloudflare Workers. It serves as the primary landing page, blog, and documentation entry point, while also hosting interactive React-based demonstrations of the Executor platform.
The marketing site operates as a separate Cloudflare Worker (executor-marketing) that is proxied by the main Cloudflare Cloud Host worker.
In production, the apps/cloud worker owns the executor.sh apex domain. It uses marketingMiddleware to determine if an incoming request should be handled by the cloud application or proxied to the marketing worker via a service binding apps/cloud/src/edge/marketing.ts35-59
| Path Type | Example Paths | Target Worker |
|---|---|---|
| Marketing | /, /blog, /terms, /_astro/* | executor-marketing |
| App/API | /login, /cloud, /api/tools | executor-cloud |
The isMarketingPath function maintains an allow-list of routes that are routed to the marketing worker apps/cloud/src/edge/marketing.ts16-31
The site uses astro.config.mjs with the @astrojs/cloudflare adapter apps/marketing/astro.config.mjs38 A custom helper, wranglerPublicDefine, synchronizes environment variables from wrangler.toml into the client-side bundle by filtering for keys prefixed with PUBLIC_ and injecting them via Vite's define apps/marketing/astro.config.mjs16-26
Sources:
To maintain privacy and bypass ad-blockers, the marketing site implements a first-party reverse proxy for PostHog analytics.
The onRequest middleware intercepts requests to /_astro/_ph and forwards them to PostHog's ingestion or asset hosts apps/marketing/src/middleware.ts17-34 This ensures that the browser SDK communicates only with the executor.sh domain.
us.i.posthog.comus-assets.i.posthog.comThe Layout.astro component contains a gated initialization script. It only activates if PUBLIC_POSTHOG_KEY is present and uses a dynamic import to avoid shipping the PostHog SDK to users if analytics are disabled apps/marketing/src/layouts/Layout.astro48-84
Sources:
The site performs server-side data fetching for dynamic elements like the GitHub star count, optimizing for Cloudflare's edge environment.
The getStars function in lib/github.ts implements a multi-layered caching strategy apps/marketing/src/lib/github.ts51-64:
TTL_OK_MS) apps/marketing/src/lib/github.ts23-27cf fetch property to hint edge-level caching for 1800 seconds apps/marketing/src/lib/github.ts34-38This diagram illustrates how a request for the homepage is handled across the Cloud Host and Marketing workers.
Sources:
The marketing site includes complex React components to demonstrate the "Executor Hub" concept and the problem of context bloat.
The AnimatedBeamDemo component uses framer-motion (via the motion package) to visualize the flow of data between agents (Claude, Cursor) and integrations (Sentry, GitHub, Linear) through the Executor hub apps/marketing/src/components/animated-beam-demo.tsx140-146
It supports multiple visual variants (e.g., blueprint, cyber, brutalist) defined in variantStyles, which control colors, border radii, and beam properties apps/marketing/src/components/animated-beam-demo.tsx19-113
The following diagram bridges the visual demo concepts to the underlying code entities.
Sources:
The site utilizes Tailwind CSS 4 with a custom "Registry-grade" grayscale palette to match the Executor application's design system apps/marketing/src/styles/global.css15-27
--color-ink (#111111) and --color-surface (#ffffff) to avoid brand hues apps/marketing/src/styles/global.css17-19.pattern-graph masks an SVG to create a technical grid background apps/marketing/src/styles/global.css61-68Sources:
Refresh this wiki