← Previous24 / 27Next →

Respan AI Observability Page

RespanThe fastest open-source AI gateway, with built-in observability and evals

Design with AI

Create a new design inspired by Respan AI Observability Page, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 882 words

# Design from Reference: Respan AI Observability Page

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Respan
- **Category:** Features Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/a54203bc716205216519-1600.webp)
- **Source:** https://www.respan.ai/ai-observability

Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.

## Visual Design Context

## Respan — shared visual language

- **Theme**: dark, developer-first marketing site. Near-black page (#000000 / #1E1E23 surfaces, #2E2E33 hairline borders) with a thin announcement bar ("Launching the open-source gateway") in letter-spaced type above a slim top nav (logo "[ . ] Respan", Product, Models, Docs, Pricing, Resources; GitHub stars, "Book a demo", white "Dashboard").
- **Typography**: Inter everywhere. Hero H1 72px/600 with very tight tracking (-3.24px); page H1 64px/600 (-1.6px); content-page H1 40px/500 (-1px). Body 14–16px in light greys (#F9FAFC, #B1B3BC). Roboto Mono for code samples, numbers and small labels.
- **Colors**: monochrome greys with saturated accents used inside product mocks and customer cards: blue #2679F3 / #1B3FE0, green #0D7C5C, purple #8F74E0, pink and red for charts; periwinkle #6483F0 for highlighted plans.
- **Components**: 36px buttons with 6px radius (white primary, #1E1E23 secondary); 12px-radius cards on #1E1E23; live code blocks with a "Copy" button and syntax colors; logo strips; testimonial cards with photos on bright color fills; a giant pixelated "[ . ] Respan" wordmark above a dense multi-column footer.
- **Layout**: centered ~1200px content, left-aligned heroes on product pages, long scrolling pages alternating code, product mocks and metric callouts ("Up to 70% off tokens", "1,000+ models").
- **Tone**: technical and blunt, numbers first ("The fastest OSS AI gateway", "Built for AI agents. Break less. Ship more.").

## Respan app (platform.respan.ai) — product UI

- **Theme**: dark app, page #151519, panels #1E1E23, raised #26262B, borders #2E2E33; text #F9FAFC and #B1B3BC; accent periwinkle #6483F0.
- **Typography**: Inter for UI (13–14px), "Respan Mono" for numbers, model ids and code.
- **Sidebar**: project switcher ("saasframe"), a "Finish setup 2 of 3" checklist card, then Inbox, API keys, Gateway, Models, Metrics, Logs, Users & identifiers, Playground, Prompts, Datasets, Red teaming, Settings; an "Open source" GitHub card and a "Credits" card ($0.00, "Auto reload off") at the bottom; a status bar with Community, Docs, Book a demo, version and "Ask Respan agent".
- **Components**: 28px compact buttons with 4px radius, filter chips, isometric line illustrations for empty states, data tables with tiny mono numbers.

### Overall aesthetic
- **Style:** black page built around monitoring UI: waterfall, pass/fail lists, sparklines.

### Page composition
- **Hero:** eyebrow, headline, lead "Traces, evals, metrics and alerts for every agent.", buttons "Get API key" / "Read the docs"; wide trace card to the right.
- **Features:** three-up grid of product cards (Tracing, Evals, Metrics), then settings, compliance, testimonials, CTA.

### Typography
- **Headline:** Inter 72px w600, -3.24px; **H2:** 44px w600; **card titles:** 26px w500.
- **Data:** Roboto Mono 11–12px for span names and durations.

### Colors & surfaces
- **Spans:** white bars on #1E1E23, the selected span in blue; failed eval row in red text.

### Components
- **Waterfall:** indented span tree with duration column and horizontal bars.
- **Metric tile:** label, value, colored delta, 24h sparkline.

### Responsive
- **Mobile:** the trace card is cropped and scrolls; feature cards stack one per row.

### Adaptation guidance
- **Lesson:** show one believable failing case (a policy contradiction) next to passing ones; it explains evals faster than copy.

## Content

**Instructions:**

Generate realistic example content that fits the selected design reference.

Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.

If a product or business description is provided, use it to guide the content.

Otherwise, invent a plausible fictional SaaS product appropriate for the reference.

Keep the content concise, coherent, and visually balanced.

Do not present fictional statistics, customer names, or testimonials as verified facts.

## Design Direction

**Instructions:**

Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.

Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.

Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.

Introduce original design decisions where they improve usability, composition, or brand consistency.

The result should clearly reflect the reference's visual language without looking like a direct reproduction.

Follow the visual identity of the reference design.

Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.

Do not introduce an unrelated visual identity.

## Output

**Instructions:**

Generate a high-fidelity visual mockup of the requested interface.

Present the design as a polished, realistic website or product UI screenshot.

Prioritize visual composition, typography, spacing, colors, alignment, and component details.

Use the available image-generation or visual-design capabilities.

Do not replace the mockup with source code, a written design specification, or a textual description.

If direct visual generation is unavailable, clearly explain the limitation.

## Constraints

- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance.

Reference imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.

Visit live page

Tech Stack

Vercel

Added on

November 12, 2026

A trace waterfall as the hero

The AI Observability page pairs "See every step of every call." with a real-looking trace of a "support_agent": nested spans such as "classify_intent", "retrieve_policies" and "openai.chat" on a 0–3s timeline, with the user input and model output under it.

Each feature gets its own working fragment

Under "Respan traces every call and flags the bad ones.", an evals list marks one row "failed" for "contradicts policy", and a metrics strip shows requests, errors and error rate with sparklines and deltas like "+38%". Each fragment carries a "Tap to open" hint.