← Previous2 / 15Next →

Unabyss Security Page

UnabyssShared memory for every AI tool you use: one live context from your apps, served to Claude, ChatGPT and Cursor over MCP.

Design with AI

Create a new design inspired by Unabyss Security 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 759 words

# Design from Reference: Unabyss Security 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:** Unabyss
- **Category:** Security Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/ee601af1b81e741f12e1-1600.webp)
- **Source:** https://unabyss.com/security

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

## Unabyss — shared visual language

- **Theme**: dark-only marketing site. Near-black warm background (#191817), cards one step lighter (~#1F1E1C) with 1px hairline borders (white at ~8% opacity) and 16–20px radii.
- **Typography**: Lexend throughout. Headlines 600 weight, ~60px on desktop, tight tracking; a two-line hero where the second line drops to a muted grey (~#8A8784) for contrast. Body copy 16–17px, light grey, generous line height. Small uppercase labels with very wide letter spacing ("WORKS WITH", "BACKED BY"); wordmark set in spaced capitals.
- **Accent**: a restrained warm gold/amber (#E8B33A-ish) used for highlight strokes, glowing rings, pill outlines ("confidential", "You own it") and connector lines; a green status dot for "In sync".
- **Components**: pill-shaped floating nav bar with a separate pill logo chip; white solid pill CTAs with a ↗ arrow icon; dark rounded logo tiles for integrations (Claude, ChatGPT, Cursor, Gmail, Slack, Notion, GitHub…); tag chips; mini UI mock cards ("Your context", "Unabyss · MCP") built from bars and status labels rather than screenshots.
- **Layout**: centered hero, then bento grids of feature cards mixing a short heading, one-line copy and an illustrative widget; inline brand icons placed inside headlines.
- **Tone**: calm, technical, confident; short declarative headings, developer-friendly vocabulary (MCP, context, memory).

### Overall aesthetic

- **Style:** Sober, legal-document layout inside the dark brand system: no hero visual, just a narrow text column, compliance badges and clear section rhythm.

### Page composition

- **Header:** 22px/600 title, two intro paragraphs, a row with two round compliance badges and their status labels.
- **Body:** ~860px column of H2 sections, each with a paragraph and bulleted list using bold lead-ins.
- **End:** Vulnerability reporting section with an email link, footer.

### Typography

- **Scale:** Title 22px/600, section headings 17px/500, body 14px/300 at 25.2px.
- **Colors:** Headings #FAFAFA, body #FFFFFF at reduced emphasis.

### Colors & surfaces

- **Backgrounds:** #0F0F0F/#191817, no cards around the text.
- **Accent:** Blue-and-gold certification badges; #FCD34D for links and small labels.

### Components

- **Badges:** Circular GDPR and SOC 2 seals with status captions.
- **Lists:** Bullets with bold first phrases.

### Responsive

- **Mobile:** Same single column at full width; badges stay side by side.

### Adaptation guidance

- **Reuse:** For early-stage security pages, show certification status honestly up top and write commitments as bolded bullet lists rather than marketing cards.

## 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

Cloudflare

Added on

November 12, 2026

A security page written as a readable policy

Unabyss's Security & Trust page is a document-style page: a small 22px title, an intro on what is protected, and two compliance badges (EU GDPR aligned, SOC 2 Type II in progress) shown with their status before any details.

Plain-language sections with bold lead-ins

The body is a single reading column of short sections: your data stays yours, no training on your data, how connections work, the context boundary, infrastructure, compliance and data retention. Each uses bulleted lists with bold opening phrases so the key commitments (encryption, read-only access, deletion) stand out.