← Previous13 / 15Next →

Unabyss AI 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 AI 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 874 words

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

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:** Enterprise-leaning AI page inside the dark brand system, with a 3D glowing golden orb and bokeh spheres as the only illustrative imagery.
- **Diagrams:** Structure is shown with org-chart trees and flowcharts drawn in thin lines and small cards rather than screenshots.

### Page composition

- **Hero:** Eyebrow, 67px two-line H1, intro, "Book a demo" pill, 3D orb scene, three check chips, award badges.
- **Anatomy:** Tree diagram from a top pill to three cards, then two amber-outlined cards (One MCP, Agents doing real work), then a founder prompt row with a button.
- **How it works:** Source icons → signal card → branching flow of labeled steps with avatar rows and inline approval buttons → "Brain updated" chip and CTA.
- **Setup:** Five-column timeline strip in an amber-outlined box, three numbered rows, CTA.
- **Control:** Four icon cards in one row; demo card with avatars and a "Live in 48h" chip.

### Typography

- **Scale:** H1 67.5px/600 (-0.81px), H2 40px/600, card titles 17.5px/500, body 16.5px/300.
- **Labels:** Uppercase micro-labels on diagram branches and mono step numbers.

### Colors & surfaces

- **Backgrounds:** #0F0F0F, #191817, black orb scene.
- **Accent:** Warm gold #FEDE9B for the orb glow, outlines and icon strokes; #FEF3C7 for small highlights.

### Components

- **Diagram cards:** Small 16–22px radius cards joined by 1px connector lines and pill labels.
- **Buttons:** White pill CTAs; "Yes/No" mini approval buttons inside the flow.
- **Icon cards:** Large thin-stroke gold icons centered on dark tiles.

### Responsive

- **Mobile:** Trees and flows become vertical sequences; the four control cards stack; the orb scene shrinks behind the headline.

### Adaptation guidance

- **Reuse:** Explain an AI system as an anatomy diagram plus a branching flow; one luminous hero object is enough imagery.

## 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 glowing orb hero for the Company Brain

The Company Brain page sells Unabyss to teams as a "Company Nervous System": a centered headline over a 3D scene of a golden orb surrounded by floating light spheres and a network mesh, a "Book a demo" pill, three checkmark trust chips and Product Hunt and ElevenLabs badges.

Org-chart anatomy and an agent flow

"Anatomy of the nervous system" draws the product as a tree: Brain, Memory and Muscles cards feed into "One MCP" and "Agents doing real work" cards with amber outlines, followed by an inline founder prompt to book a demo. "How the nervous system works" then turns into a flowchart with tagged branches (signal detection, it finds the owner, it sends an agent, it asks before it writes) ending on a "Brain updated" chip.

Onboarding steps, control pillars and a demo call

A horizontal five-stage progress strip and three numbered steps explain the white-glove setup, four icon cards cover permissions, ownership, no training and compliance, and a wide card with founder avatars and a "Book a demo" button closes the page.