Browserbase — Template Selector Panel
Other · Developer Tools
Pricing page · Developer Tools
A four-plan infrastructure pricing comparison with tier cards, included resources and capability lists.
Download DESIGN.md into your project and ask your coding agent to follow it alongside this reference. Review inferred values against the original before implementation.
---
version: alpha
name: Browserbase — Pricing Page
colors:
primary: '#FF4500'
canvas: '#FFFFFF'
ink: '#000000'
surface: '#E1E9F2'
typography:
heading:
fontFamily: gtPlanar, "gtPlanar Fallback", system-ui, Arial, sans-serif
fontSize: 36px
fontWeight: 500
lineHeight: 37.8px
body:
fontFamily: plain, "plain Fallback", system-ui, Arial, sans-serif
fontSize: 16px
fontWeight: 400
lineHeight: 22.56px
---
## Overview
A four-plan infrastructure pricing comparison with tier cards, included resources and capability lists. Inspected at 1440px desktop and 390px mobile widths on September 30, 2026.
## Colors
Palette tokens describe the observed visual roles. Use a precise white grid, black pill actions, orange-red highlights and expressive dithered landscape artwork. Pale blue product demos contrast with dense black interface text. Transparent and gradient text layers must be considered with their painted background, not interpreted as solid-color text.
## Typography
The sampled heading uses gtPlanar, "gtPlanar Fallback", system-ui, Arial, sans-serif at 36px, weight 500, with 37.8px leading. Supporting sample: plain, "plain Fallback", system-ui, Arial, sans-serif, 16px / 22.56px. These are computed styles at capture width, not fixed requirements for every breakpoint. Use licensed font assets or deliberate substitutes.
## Layout
Keep plan names, price hierarchy, included usage and actions consistently aligned. Mobile stacks cards rather than shrinking comparison text. Preserve the source distinction between base price and metered usage. Exact responsive breakpoints were not measured.
## Elevation & Depth
Preserve separation through the reference’s surface contrast, border rules and whitespace. Avoid adding heavy shadows to a flat interface. Shadow strength is visual guidance, not a measured token.
## Shapes
Keep the visible distinction between content panels, fields and actions. Match the photographed corner treatment rather than applying one global radius; measured element radii are retained in the evidence.
## Components
Prices are source content at capture time, not verified purchasing advice. No billing selector, calculator or purchase action was exercised.
## Do's and Don'ts
Do adapt hierarchy, spacing and responsive ordering with your own brand and truthful copy. Do not reuse customer endorsements or performance numbers as your own. Do not infer hover, keyboard, validation, dark-mode or accessibility compliance from static images.
If copying fails, download the file or select the text above.
Design belongs to its original creator. Use this example for inspiration, not as a licensed template.