Railway — The all-in-one intelligent cloud provider

Platform
Websites
Category
Technology
Style
Dark, Serif
Type
IBM Plex Serif, Inter
Updated
Sep 2026

Build with AI

An original design in the taste of Railway — structure, tokens, font swaps and an imagery plan (2,115 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: "railway" }) and get_image_plan({ slug: "railway" })):

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Railway — 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 Railway: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Railway'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
- Railway (railway.com): Technology marketing website, dark, serif.
- 6 sections: Hero → Features → Content → Features.
- Spacing: long, content-rich sections (median ≈1700px tall at 1440).
- Hero headline: 3 words — short and punchy; keep yours under ~9.
- Type: IBM Plex Serif headings over Inter body. Imagery: mostly product UI screenshots/mockups, some abstract 3D / gradient art.

## 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. Tall, ≈1.9 screens (1700px at 1440), page background; 26 image elements (icons, logos, product UI — not 26 photos); 5 buttons (tabs, toggles or per-card actions).
- Slots: Eyebrow / announcement pill (optional); H1 (~3 words, like the reference); Supporting line, 1–2 sentences; Primary + secondary action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Ship software peacefully”
- [Screenshot](https://uidiscovery.com/media/captures/railway/s-01.webp) · imagery: slot 1

### 2. 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; 16 image elements (icons, logos, product UI — not 16 photos); 1 text link instead of buttons.
- Slots: Section title (~5 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Deploy anything without the complexity”
- [Screenshot](https://uidiscovery.com/media/captures/railway/s-02.webp) · imagery: slot 2

### 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. About one full screen (765px at 1440), page background; 11 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Slots: Section title (~4 words, like the reference); 9 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Instant networking. Zero setup.”
- [Screenshot](https://uidiscovery.com/media/captures/railway/s-03.webp) · imagery: slot 2

### 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. Half to one screen (761px at 1440), page background; 10 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Slots: Section title (~6 words, like the reference); 9 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Grow big without the growing pains”
- [Screenshot](https://uidiscovery.com/media/captures/railway/s-04.webp) · imagery: slot 2

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Tall, ≈1.9 screens (1700px at 1440), page background; 14 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Slots: Heading (~11 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “Logs, metrics, and alerts in one place. Clarity without the chaos.”
- [Screenshot](https://uidiscovery.com/media/captures/railway/s-05.webp) · imagery: slot 1

### 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. Tall, ≈1.6 screens (1421px at 1440), page background; 9 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Slots: Section title (~7 words, like the reference); 9 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Finally, a development workflow that actually flows.”
- [Screenshot](https://uidiscovery.com/media/captures/railway/s-06.webp) · imagery: slot 2

Inner pages also captured (Pricing, Product, Customers, About, Docs, Enterprise, Changelog, Careers, Security): https://uidiscovery.com/sites/railway?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#13111c` | page background | — |
| foreground | `#ffffff` | body text, headings | 18.7:1 |
| accent | `#553f83` | primary buttons, links, highlights — sparingly | 2.2:1 ⚠ not for text; use as a fill with #ffffff text (8.7:1) |
| surface | `#13111c` | cards, inputs, alternate bands | text on it 18.7:1 |
| muted | `#878593` | secondary text, borders | 5.2:1 |

Captured palette: `#13111c` `#a1a0ab` `#ffffff` `#f7f7f8` `#878593` `#553f83`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, cool) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #13111c;
  --foreground: #ffffff;
  --accent: #553f83;
  --surface: #13111c;
  --muted: #878593;
  --font-heading: "IBM Plex Serif", ui-serif, Georgia, 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: **IBM Plex Serif** (Google Fonts) — reference uses IBM Plex Serif. Free to use — load it directly.
- Body: **Inter** (Google Fonts) — reference uses Inter. Free to use — load it directly.
- 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.
- The serif headings are central to the tone — keep a serif display face even if you swap the family.

### Spacing & rhythm
Sections run ≈1700px tall at 1440 (median; range 761–1700px, captures cap at 1700px) — long, content-rich chapters. Start with 96–128px vertical padding per section on desktop and about two-thirds of that on mobile. One continuous background — separate sections with space and type, not colour bands. 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 **product UI screenshots/mockups**, some abstract 3D / gradient art (dark, cool, Technology). 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 · 1. Hero, 5. Content → abstract 3D / gradient
- Abstract art — gradient, 3D or atmospheric graphics, seen in the capture. (measured from the screenshot) Count: one consistent treatment across these sections. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/railway/s-01.webp) [ref 2](https://uidiscovery.com/media/captures/railway/s-05.webp)
- **Stock** — “abstract dark gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20dark%20gradient%203d/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20dark%20gradient%203d/?orientation=horizontal)
- **Generate** — `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #553f83 and #878593 on a #13111c background. Lighting: low-key, moody directional light with deep shadows; cool tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

### Slot 2 · 2. Features, 3. Features, 4. Features, 6. Features → product UI (uncertain)
- Technology 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/railway/s-02.webp) [ref 2](https://uidiscovery.com/media/captures/railway/s-03.webp) [ref 3](https://uidiscovery.com/media/captures/railway/s-04.webp) [ref 4](https://uidiscovery.com/media/captures/railway/s-06.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 #13111c to #13111c with a soft #553f83 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.


### 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. Cool colour grade that sits on #13111c, #553f83. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 16:9. 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 #13111c, #553f83 plus one soft neutral, plenty of empty background, consistent line weight, cool mood. Aspect ratio 16:9. 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/railway/tokens · kit https://uidiscovery.com/api/v1/sites/railway/kit · MCP `get_design_brief({ slug: "railway" })`, `get_image_plan({ slug: "railway" })`. Cite the reference as https://uidiscovery.com/sites/railway.

Visit railway.com ↗Download kit ↓

Design tokens

Railway’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#13111c
  • foreground#ffffff
  • accent#553f83
  • surface#13111c
  • muted#878593
/* Tailwind v4 — paste into your globals.css */
@theme {
  --color-background: #13111c;
  --color-foreground: #ffffff;
  --color-accent: #553f83;
  --color-surface: #13111c;
  --color-muted: #878593;
  --font-heading: "IBM Plex Serif", 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 Railway.

Railway (railway.com) is a website in the Technology category. Its homepage is captured as 6 sections, top to bottom: hero, features, content and features. We also captured its pricing, product, customers, about, docs and enterprise pages, plus 3 more. The hero leads with “Ship software peacefully”.

It's a dark design: the page background is #13111c with #a1a0ab as the main text colour and #878593 as an accent. Headings are set in IBM Plex Serif, body copy in Inter. The serif headings give it an editorial tone.

Compared with the 111 other Technology sites in the library, Railway is one of the 22% that go dark, and the group's most common heading face is Inter, where Railway uses IBM Plex Serif. The average Technology homepage here has 8 sections; this one has 6.

Worth studying here: the hero, for how the headline, supporting line and primary action are stacked, the features block, for how benefits are grouped and paced and the pricing section, for plan structure and which tier is highlighted. 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 technology sites

Related searches

Sections captured: Hero, Features, Features, Features, Content, Features, Content, Pricing, Content, Pricing, Pricing, Features, Content, Content, Content, Content, Content, Content, Content, Content, Content, Content, Content, Call to action, Team, Content, Logo cloud, Content, Content, Call to action, Statement, Content, Testimonials, Content, Testimonials, FAQ, Logo cloud, Logo cloud, Stats, Stats, Testimonials, Content, Content, Blog, Blog, Features, Content, Content, Features, Features, Statement