ClickHouse — Fast Open-Source OLAP DBMS

Platform
Websites
Category
Developer Tools
Style
Dark
Type
Basier, Inter
Updated
Sep 2026

Build with AI

An original design in the taste of ClickHouse — structure, tokens, font swaps and an imagery plan (2,675 words).

Paste into any AI tool. Every screenshot in the prompt is a public link the tool can open, and you can attach the screenshot link as a visual reference. It tells the agent to build something original: new copy, your brand, licensed or generated images.

Open in

Long prompts are copied to your clipboard first — paste them in when the tool opens.

Connect via MCP

claude mcp add uidiscovery \
  --env UIDISCOVERY_URL=https://uidiscovery.com \
  -- node /path/to/uidiscovery/mcp/server.mjs

Then ask your agent (it calls get_design_brief({ slug: "clickhouse" }) and get_image_plan({ slug: "clickhouse" })):

Use the uidiscovery MCP server: call get_design_brief({ slug: "clickhouse" }) and get_image_plan({ slug: "clickhouse" }), look at the preview images, then build an original site for [my brand] that follows the brief. Cite https://uidiscovery.com/sites/clickhouse.

Download kit ↓Brief as Markdown ↗API docs
Preview the prompt
# Build brief — an original marketing website in the taste of ClickHouse

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as ClickHouse — 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 ClickHouse: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse ClickHouse'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
- ClickHouse (clickhouse.com): Developer Tools marketing website, dark.
- 12 sections: Hero → Logo cloud → Features → Content → Features → Content → Features → Footer.
- Spacing: about a screen per idea (median section ≈664px).
- Hero headline: 5 words — short and punchy; keep yours under ~9.
- Type: one family (Basier). Imagery: mostly abstract 3D / gradient art, some product UI screenshots/mockups.

## 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 (574px at 1440), page background; no images (type-led); primary + secondary button.
- Slots: Eyebrow / announcement pill (optional); H1 (~5 words, like the reference); Supporting line, 1–2 sentences; Primary + secondary action; No image — let type and colour carry it.
- Topic (tone/length only — never reuse): “The leading database for AI”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/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 (338px at 1440), page background; 63 image elements (icons, logos, product UI — not 63 photos); primary + secondary button, 61 links (link lists / navigation).
- 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/clickhouse/s-02.webp)

### 3. 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 (569px at 1440), page background; 8 images/icons (a set of cards or a small gallery); 4 text links instead of buttons; 5 headings → ~4 items under a title.
- Slots: Section title (~6 words, like the reference); 4 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Built for every modern data challenge”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-03.webp) · imagery: slot 1

### 4. 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. Tall, ≈1.9 screens (1700px at 1440), page background; 6 images/icons (a set of cards or a small gallery); 14 buttons (tabs, toggles or per-card actions).
- Slots: Section title (~6 words, like the reference); 6 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Build real-time data products that scale”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-04.webp) · imagery: slot 2

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (960px at 1440), own dark band #1c0000; 8 images/icons (a set of cards or a small gallery); 6 text links instead of buttons.
- Slots: Heading (~3 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “Why ClickHouse?”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-05.webp) · imagery: slot 3

### 6. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (784px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Heading (~5 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “Seamlessly integrate with your stack”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-06.webp) · imagery: slot 3

### 7. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (774px at 1440), page background; 3 image/graphics; one primary button.
- Slots: Heading (~5 words, like the reference); Body copy; Supporting visual (see image plan); One primary action.
- Topic (tone/length only — never reuse): “Why is ClickHouse so fast?”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-07.webp) · imagery: slot 3

### 8. 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. About one full screen (1031px at 1440), own dark band #620f45; 4 images/icons (a set of cards or a small gallery); 3 buttons (tabs, toggles or per-card actions); 4 headings → ~3 items under a title.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Deploy your way”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-08.webp) · imagery: slot 1

### 9. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (290px at 1440), page background; 5 images/icons (a set of cards or a small gallery); 5 text links instead of buttons.
- Slots: Heading (~7 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “Join the 100k+ developers using ClickHouse today”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-09.webp) · imagery: slot 3

### 10. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (386px at 1440), page background; no images (type-led); 5 buttons (tabs, toggles or per-card actions).
- Slots: Heading; Body copy; Primary + secondary action.
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-10.webp)

### 11. 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 (406px at 1440), page background; 1 image/graphic; primary + secondary button.
- Slots: Section title (~7 words, like the reference); 2 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Get started with ClickHouse Cloud for free”
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-11.webp) · imagery: slot 1

### 12. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. Half to one screen (664px at 1440), own dark band #070000; 3 image/graphics; primary + secondary button, 58 links (link lists / navigation).
- Slots: Brand mark + one-line description; 3–5 link columns; Newsletter or contact (optional); Legal row + social icons.
- [Screenshot](https://uidiscovery.com/media/captures/clickhouse/s-12.webp)

Inner pages also captured (Pricing, Product, Customers, About, Blog, Docs, Contact, Security): https://uidiscovery.com/sites/clickhouse?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#131312` | page background | — |
| foreground | `#ffffff` | body text, headings | 18.6:1 |
| accent | `#620f45` | primary buttons, links, highlights — sparingly | 1.5:1 ⚠ not for text; use as a fill with #ffffff text (12.5:1) |
| surface | `#070000` | cards, inputs, alternate bands | text on it 20.8:1 |
| muted | `#590000` | secondary text, borders | 1.3:1 — borders / large text only |

Captured palette: `#131312` `#070000` `#590000` `#620f45` `#ffffff` `#000000`. Section bands top→bottom: `#131312` → `#1c0000` → `#620f45` → `#070000`. 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: #131312;
  --foreground: #ffffff;
  --accent: #620f45;
  --surface: #070000;
  --muted: #590000;
  --font-heading: "Inter", 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: **Inter** (Google Fonts) — reference uses Basier. “Basier” is likely a custom or licensed face. Inter is a neutral stand-in — pick a closer free match by eye from the screenshot.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- 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 ≈664px tall at 1440 (median; range 290–1700px, 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 5 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

Best guess: mostly **abstract 3D / gradient art**, some product UI screenshots/mockups (dark, warm, Developer Tools). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.

### Slot 1 · 3. Features, 8. Features, 11. 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/clickhouse/s-03.webp) [ref 2](https://uidiscovery.com/media/captures/clickhouse/s-08.webp) [ref 3](https://uidiscovery.com/media/captures/clickhouse/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 #131312 to #070000 with a soft #620f45 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 · 4. Features → photography
- Photography, seen in the capture (people). (measured from the screenshot) Count: a set of ~6 in one consistent style. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/clickhouse/s-04.webp)
- **Stock** — “abstract gradient mesh close up dark”: [Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh-close-up-dark?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20gradient%20mesh%20close%20up%20dark/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20gradient%20mesh%20close%20up%20dark/?orientation=horizontal)
- **Generate** — `Photograph: abstract gradient mesh close up. Composition: tight crop, identical framing and background across the whole set. Lighting: low-key, moody directional light with deep shadows. Warm colour grade that sits on #131312, #620f45, #070000. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

### Slot 3 · 5. Content, 6. Content, 7. Content, 9. 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/clickhouse/s-05.webp) [ref 2](https://uidiscovery.com/media/captures/clickhouse/s-06.webp) [ref 3](https://uidiscovery.com/media/captures/clickhouse/s-07.webp) [ref 4](https://uidiscovery.com/media/captures/clickhouse/s-09.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 #620f45 and #590000 on a #131312 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, 10. Content: 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).
- **Icons** — 12. Footer: Use one open-source icon set at one stroke weight — Lucide, Phosphor or Heroicons (MIT) — tinted with the text or accent token. Social icons: Simple Icons.

### 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:
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #131312, #620f45, #070000 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/clickhouse/tokens · kit https://uidiscovery.com/api/v1/sites/clickhouse/kit · MCP `get_design_brief({ slug: "clickhouse" })`, `get_image_plan({ slug: "clickhouse" })`. Cite the reference as https://uidiscovery.com/sites/clickhouse.

Visit clickhouse.com ↗Download kit ↓

Design tokens

ClickHouse’s palette and type, mapped to roles. Drop the rules file into Cursor, Claude Code or Codex so what they build stops looking like a template.

  • background#131312
  • foreground#ffffff
  • accent#620f45
  • surface#070000
  • muted#590000
/* Tailwind v4 — paste into your globals.css */
@theme {
  --color-background: #131312;
  --color-foreground: #ffffff;
  --color-accent: #620f45;
  --color-surface: #070000;
  --color-muted: #590000;
  --font-heading: basier, ui-sans-serif, system-ui, sans-serif;
  --font-sans: Inter, ui-sans-serif, system-ui, sans-serif;
}

About this design

Written from the capture data for ClickHouse.

ClickHouse (clickhouse.com) is a website in the Developer Tools category. Its homepage is captured as 12 sections, top to bottom: hero, logo cloud, features, content, features, content, features and footer. We also captured its pricing, product, customers, about, blog and docs pages, plus 2 more. The hero leads with “The leading database for AI”.

It's a dark design: the page background is #131312 with #070000 as the main text colour and #620f45 as an accent. Headings are set in Basier, body copy in Inter.

Compared with the 66 other Developer Tools sites in the library, ClickHouse is one of the 42% that go dark, and the group's most common heading face is Inter, where ClickHouse uses Basier. The average Developer Tools homepage here has 8 sections; this one has 12.

Worth studying here: the hero, for how the headline, supporting line and primary action are stacked, the logo cloud, for how social proof is placed without shouting and the features block, for how benefits are grouped and paced. Open any section for its palette, fonts and a build prompt you can hand to Claude, Cursor or v0.

More references: browse all websites.

More developer tools sites

Related searches

Sections captured: Hero, Logo cloud, Features, Features, Content, Content, Content, Features, Content, Content, Features, Footer, Content, Content, Content, Content, Content, Call to action, Content, Content, Blog, Blog, Blog, Blog, Content, Content, Features, Features, Content, Features, Features, Features, Content, Content, Features, Content, Features, Features, Call to action