Add Solutions section, BYOC deployment cards, mobile stack snap - #66
Conversation
- New "Built for every kind of agent" section on the homepage with five solution cards (coding agents, agent app builders, company-specific agents, personal agents, realtime apps), each with a CSS-only hover vignette animation (hover-capable pointers, reduced-motion respected). - Deployment options: "Local & Self-Host", "Rivet Cloud", and a new "BYOC" card; BYOC added to pricing comparison, enterprise page, on-prem pillar, and footer. Docs untouched. - Agent stack section: scroll-snap cards on phones so each card fits between the sticky diagram and the bottom of the screen. - Dev server: pre-bundle heavy deps via vite.optimizeDeps (dev only). Amp-Thread-ID: https://ampcode.com/threads/T-01a0a1bf-48c6-77f8-b65d-0b681d9f18a9 Co-authored-by: Nicholas Kissel <nicholas@rivet.gg>
![the-company-company[bot]](https://avatars.githubusercontent.com/in/3874572?s=60&v=4){kind=small}
| diagram: DeploymentDiagramVariant; | ||
| cta: string; | ||
| href: string; | ||
| primary: boolean; |
There was a problem hiding this comment.
🟠 Medium · Show the bring-your-own-compute boundary accurately
This card explicitly offers a configuration where the backend runs on Vercel, Railway, Cloudflare, AWS, or Kubernetes, but its managed diagram and accessible description place the backend inside the Rivet Cloud boundary. The comparison therefore tells visitors choosing that advertised option that Rivet Cloud operates their backend, which contradicts the card copy and the deployment model.
Use a diagram/ARIA variant that separates customer compute from Rivet Cloud for this option, or present bring-your-own compute as its own model rather than attaching it to the fully managed diagram.
Amp-Thread-ID: https://ampcode.com/threads/T-01a0a1bf-48c6-77f8-b65d-0b681d9f18a9 Co-authored-by: Nicholas Kissel <nicholas@rivet.gg>
| diagram: DeploymentDiagramVariant; | ||
| cta: string; | ||
| href: string; | ||
| primary: boolean; |
There was a problem hiding this comment.
🟠 Medium · Show the bring-your-own-compute boundary accurately
This card explicitly offers a configuration where the backend runs on Vercel, Railway, Cloudflare, AWS, or Kubernetes, but its managed diagram and accessible description place the backend inside the Rivet Cloud boundary. The comparison therefore tells visitors choosing that advertised option that Rivet Cloud operates their backend, which contradicts the card copy and the deployment model.
Use a diagram/ARIA variant that separates customer compute from Rivet Cloud for this option, or present bring-your-own compute as its own model rather than attaching it to the fully managed diagram.
| const title = 'Enterprise Infrastructure'; | ||
| const description = | ||
| 'Run Rivet on-prem, in your VPC, inside customer environments, or fully air-gapped with an enterprise control plane and no required outbound connections.'; | ||
| 'Run Rivet in your VPC with BYOC, on-prem, inside customer environments, or fully air-gapped with an enterprise control plane and no outbound connections.'; |
There was a problem hiding this comment.
🟠 Medium · Do not promise no outbound connections for BYOC
The description now advertises BYOC while saying the deployments have “no outbound connections.” BYOC requires the in-cluster operator to poll Rivet Cloud and report status, and its documented outbound requirements also include release downloads, log uploads, cloud APIs, and registries. This makes the Enterprise search description promise an unsupported network posture.
Keep “no required outbound connections” for self-hosted/air-gapped deployments, or qualify the claim so it excludes BYOC.
2 participants
Summary
SolutionsSection.tsx+ CSS module), placed before Observability. Five cards: coding agents, agent app builders, company-specific agents, personal agents, realtime apps. Each vignette replays a short CSS-only story on hover/focus (hover-capable pointers only,prefers-reduced-motionrespected). Rest state is the finished frame.vite.optimizeDeps(dev only; production build unchanged).Verification
tscclean for touched files.Thread: https://ampcode.com/threads/T-01a0a1bf-48c6-77f8-b65d-0b681d9f18a9