Add /government landing page

[clemra]

Adds a dedicated Langfuse for Government landing page at /government, styled after /japan and /launch-week-5.

The page is self-hosting-first and leads with control and accountability:

• Hero: a Langfuse for Government masthead, the catchphrase “Build accountable AI. Keep it under your control.”, and short claims (your environment, open source, your traces)
• Hero copy now says air-gapped, on-premises, or in a government cloud (not private cloud), with a featured Government cloud polaroid
• Hero callout for Langfuse Cloud for Government (coming soon), with NIST SP 800-53 Rev. 5, SSDF, and FIPS 140-3 described as hardening in progress, plus a Contact sales CTA and a link to compare both options
• Two deployment options lower on the page: self-hosted, on-premises Enterprise (available today, including ClickHouse Government) and Cloud for Government (coming soon), with a Contact sales CTA
• Option 02 bullets now also include Run in AWS GovCloud and FEDRAMP Moderate (in-process)
• Narrower editorial layout (max-w-[1000px]) with a featured Government polaroid that lifts and straightens on hover
• Observe, evaluate, and contain loop for AI agents
• Security summary, scoped FIPS image request, and a Docker Compose quickstart

NIST and FIPS items for Cloud for Government are framed as work in progress, not completed authorizations. A Markdown mirror lives in md-override/government.md.

Test plan

• Load /government on desktop and confirm hero, proof strip, sections, and final CTA render
• Check mobile layout (proof strip 2×2, compact hero cards, stacked sections)
• Click primary CTA → /talk-to-us and secondary CTA → /self-hosting
• Copy the Docker Compose snippet
• Confirm footer “Government” link and Enterprise page resource link
• Fetch /government.md and confirm the Markdown mirror matches the page
• Confirm the narrower hero, government masthead, and polaroid hover on desktop
• Confirm government page copy has no em dashes and reads in plain language
• Confirm hero “Coming soon” callout, Contact sales → /talk-to-us, and #government-cloud section (self-host vs Cloud for Government)
• Confirm hero says “government cloud” and Option 02 still lists NIST / SSDF / FIPS hardening with Contact sales
• Confirm Option 02 bullets include AWS GovCloud and FEDRAMP Moderate (in-process)

  

Greptile Summary

Adds a dedicated government landing page centered on self-hosted deployment, observability, evaluation, governance, and public-sector conversion paths.

• Registers /government as a dedicated marketing route with custom metadata, layout, responsive presentation, and CTA behavior.
• Adds a Markdown mirror and links the page from the footer and Enterprise resources.
• Adjusts shared feedback and Ask AI chrome for the custom landing-page experience.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking documentation fix recommended for the incomplete Docker Compose quickstart.

The route, page shell, Markdown override, and internal destinations are coherently connected; the displayed startup commands skip the secret-update step required by the canonical deployment guide.

Files Needing Attention: components/government/GovernmentLanding.tsx

Prompt To Fix All With AI

### Issue 1
components/government/GovernmentLanding.tsx:8-11
**Quickstart skips secret configuration**

The copied quickstart proceeds directly from cloning to `docker compose up`, while the canonical Docker Compose guide requires updating the secrets first. Presenting these commands as the complete setup procedure leaves users with unchanged placeholder secrets or an unsupported deployment setup.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Add /government landing page for public-..." | Re-trigger Greptile}

Context used (4)

• Knowledge Base — Route resolution and layouts
• Knowledge Base — Content publishing automation
• Knowledge Base — Commercial and community experiences
• Knowledge Base — Interactive site services

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
langfuse-docs	Ready	Preview	Sep 4, 2026 3:21pm UTC

[github-actions]

@claude review

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 989357d. Configure here.}