HydraDB — The Graph AI Runs On

# Build brief — an original marketing website in the taste of HydraDB

> Reference: https://hydradb.com · UIDiscovery: https://uidiscovery.com/sites/hydradb · captured 2026-09-23 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/hydradb/full.png) · [scroll video](https://uidiscovery.com/media/captures/hydradb/preview.mp4)

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as HydraDB — same structure, rhythm and polish, entirely new identity and content.

## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as HydraDB: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse HydraDB's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.

## 3. The taste, in short
- HydraDB (hydradb.com): Developer Tools marketing website, dark.
- 15 sections: Hero → Logo cloud → Stats → Content → Features → Content → Features → Content → FAQ.
- Spacing: about a screen per idea (median section ≈540px).
- Hero headline: 5 words — short and punchy; keep yours under ~9.
- Type: Geist Pixel Square headings over system sans-serif body. Imagery: mostly typography with little or no imagery.

## 4. Page structure (top to bottom)

### 1. Hero — state what the product is and for whom in one glance, and offer the primary action.
- Layout: headline-led stack: eyebrow → H1 → supporting line → actions, with a visual beside or below. Half to one screen (733px at 1440), page background; no images (type-led); 3 text links instead of buttons.
- Slots: Eyebrow / announcement pill (optional); H1 (~5 words, like the reference); Supporting line, 1–2 sentences; Text link action; No image — let type and colour carry it.
- Topic (tone/length only — never reuse): “The Graph AI Runs On.”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-01.webp)

### 2. Logo cloud — borrow trust from recognisable customers or partners.
- Layout: a single row or wall of monochrome marks with a one-line lead-in. Compact band (270px at 1440), page background; 32 image elements (icons, logos, product UI — not 32 photos); no interactive controls.
- Slots: One-line lead-in (e.g. “Trusted by…”); 6–10 monochrome customer/partner marks (your own, with permission).
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-02.webp)

### 3. Stats — prove scale or impact with a few big numbers.
- Layout: 3–4 large numerals with short labels in a row. Compact band (361px at 1440), page background; no images (type-led); 1 text link instead of buttons.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- Topic (tone/length only — never reuse): “$6.5M Raised”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-03.webp)

### 4. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (515px at 1440), page background; no images (type-led); no interactive controls.
- Slots: Heading (~12 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Own Your Memory Layer. No Third-Party Abstraction. No Data Leaving Your Stack.”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-06.webp)

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (632px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Heading (~4 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Similarity Isn't Always Relevance.”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-07.webp)

### 6. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (499px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Section title; 2 items: icon or visual + short title + 1–2 line description.
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-08.webp) · imagery: slot 1

### 7. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (499px at 1440), page background; 2 image/graphics; no interactive controls.
- Slots: Section title; 2 items: icon or visual + short title + 1–2 line description.
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-09.webp)

### 8. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (825px at 1440), page background; 2 image/graphics; no interactive controls.
- Slots: Heading (~5 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “Recall Degradation As A Bottleneck”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-10.webp)

### 9. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (645px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Section title (~6 words, like the reference); 2 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Graph Native Context Infrastructure For Agents”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-11.webp) · imagery: slot 1

### 10. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (540px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Heading (~3 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “Total documents ingested”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-12.webp) · imagery: slot 2

### 11. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (234px at 1440), own dark band #0e0e0e; 3 image/graphics; no interactive controls.
- Slots: Heading; Body copy; Supporting visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-13.webp) · imagery: slot 2

### 12. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (618px at 1440), own dark band #100c0a; 3 image/graphics; no interactive controls.
- Slots: Heading; Body copy; Supporting visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-14.webp) · imagery: slot 2

### 13. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (462px at 1440), page background; no images (type-led); no interactive controls.
- Slots: Heading (~3 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Category”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-16.webp)

### 14. Content — supporting content that deepens one idea.
- Layout: text + media block. Tall, ≈1.4 screens (1242px at 1440), page background; no images (type-led); 4 text links instead of buttons.
- Slots: Heading (~3 words, like the reference); Body copy; Text link action.
- Topic (tone/length only — never reuse): “Pricing”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-17.webp)

### 15. FAQ — remove the last objections before the call to action.
- Layout: question list with disclosure (accordion), often two columns on desktop. Half to one screen (660px at 1440), own light band #ffffff; no images (type-led); no interactive controls; 6 headings → ~5 items under a title.
- Slots: Title; 5 question/answer pairs; Link to support/contact.
- Topic (tone/length only — never reuse): “Frequently Asked Questions”
- [Screenshot](https://uidiscovery.com/media/captures/hydradb/s-18.webp)

Inner pages also captured (Customers, Contact, Security): https://uidiscovery.com/sites/hydradb?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#000000` | page background | — |
| foreground | `#ffffff` | body text, headings | 21.0:1 |
| accent | `#ff571a` | primary buttons, links, highlights — sparingly | 6.6:1 |
| surface | `#0e0e0e` | cards, inputs, alternate bands | text on it 19.3:1 |
| muted | `#757575` | secondary text, borders | 4.6:1 |

Captured palette: `#000000` `#ffffff` `#757575` `#ff571a` `#999999` `#0e0e0e`. Section bands top→bottom: `#000000` → `#ffffff` → `#0e0e0e` → `#100c0a`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, warm) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #000000;
  --foreground: #ffffff;
  --accent: #ff571a;
  --surface: #0e0e0e;
  --muted: #757575;
  --font-heading: "Geist", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Inter", ui-sans-serif, system-ui, sans-serif;
  --radius: 12px; /* calibrate from the screenshot */
}

/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
  --color-background: var(--background);
  --color-foreground: var(--foreground);
  --color-accent: var(--accent);
  --color-surface: var(--surface);
  --color-muted: var(--muted);
  --font-heading: var(--font-heading);
  --font-sans: var(--font-body);
}
```

### Typography
- Headings: **Geist** (Google Fonts) — reference uses Geist Pixel Square. Free to use.
- Body: **Inter** (Google Fonts) — reference uses system sans-serif. The reference uses the system stack; Inter (or plain system-ui) keeps that neutral feel.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.75rem, 6vw, 5rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.

### Spacing & rhythm
Sections run ≈540px tall at 1440 (median; range 234–1242px, captures cap at 1700px) — roughly a screen per idea. Start with 96–120px vertical padding per section on desktop and about two-thirds of that on mobile. The background changes 6 times down the page — use band changes to mark chapters. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.

### Shape, depth & theme
On dark, separate layers with 1px borders at ~8–12% white and soft glows instead of drop shadows. Read exact corner radius, border and shadow treatment from the screenshots. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.

## 6. Imagery plan

Measured from 5 section screenshots: mostly **typography with little or no imagery** (dark, warm, Developer Tools). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 6. Features, 9. Features → product UI (uncertain)
- Developer Tools sections with many image elements — most likely product UI screenshots/mockups plus icons. Count: one consistent treatment across these sections. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/hydradb/s-08.webp) [ref 2](https://uidiscovery.com/media/captures/hydradb/s-11.webp)
- **Stock** — “laptop blank screen minimal desk”: [Unsplash](https://unsplash.com/s/photos/laptop-blank-screen-minimal-desk?orientation=landscape) · [Pexels](https://www.pexels.com/search/laptop%20blank%20screen%20minimal%20desk/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/laptop%20blank%20screen%20minimal%20desk/?orientation=horizontal)
- **Generate** — `Product-shot backdrop for a UI screenshot: smooth dark gradient from #000000 to #0e0e0e with a soft #ff571a glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: low-key, moody directional light with deep shadows. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people. No UI elements.`
- Build the UI itself in HTML/CSS with realistic sample data from YOUR product (or screenshot your real app). Don't generate UI as an image and don't reuse the reference's screenshots. Stock/AI is only for the backdrop or device frame.

### Slot 2 · 10. Content, 11. Content, 12. Content → abstract 3D / gradient (uncertain)
- Dark Developer Tools section with a few graphics — typically abstract 3D/gradient art or a product shot. Count: one consistent treatment across these sections. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/hydradb/s-12.webp) [ref 2](https://uidiscovery.com/media/captures/hydradb/s-13.webp) [ref 3](https://uidiscovery.com/media/captures/hydradb/s-14.webp)
- **Stock** — “abstract dark gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=portrait) · [Pexels](https://www.pexels.com/search/abstract%20dark%20gradient%203d/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/abstract%20dark%20gradient%203d/?orientation=vertical)
- **Generate** — `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #ff571a and #757575 on a #000000 background. Lighting: low-key, moody directional light with deep shadows; warm tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 4:5. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

- **No imagery (type-led)** — 1. Hero, 3. Stats, 4. Content, 5. Content, 7. Features, 8. Content, 13. Content, 14. Content, 15. FAQ: No imagery needed — type, spacing and colour do the work. If the screenshot shows a background graphic, rebuild it in CSS (gradient, grid, noise) or a short muted video, not a stock photo.
- **Logos** — 2. Logo cloud: Never generate or stock-source logos. Use your real customers'/partners' marks with permission (monochrome, equal height), or neutral wordmark placeholders until you have them. Integration icons: each tool's official brand kit (Simple Icons is a quick start; trademarks still apply).

### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: low-key, moody directional light with deep shadows. Warm colour grade that sits on #000000, #ff571a, #0e0e0e. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient mesh dark” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh-dark?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #000000, #ff571a, #0e0e0e plus one soft neutral, plenty of empty background, consistent line weight, warm mood. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“technology flat illustration” on Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=landscape) (same query works on Pexels/Pixabay)

- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.

## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.

## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.

## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).

---
More: tokens https://uidiscovery.com/api/v1/sites/hydradb/tokens · kit https://uidiscovery.com/api/v1/sites/hydradb/kit · MCP `get_design_brief({ slug: "hydradb" })`, `get_image_plan({ slug: "hydradb" })`. Cite the reference as https://uidiscovery.com/sites/hydradb.