reDesign
Start a project
Start a project

Keep. We designed Keep, a project workspace for teams and their AI agents.

Product
Keep, a Reveriext product
Platform
Responsive web application
Services
UI/UX design, design system, implementation
Team
reDesign, with reLabs
The product film follows an idea into planned work, connected records, and review. It illustrates the interface using sample project content.

The challenge

Keep brings requirements, tasks, feedback, decisions, and time into a workspace used by teams and AI agents. The design needed to make those relationships visible and distinguish ongoing work from proposals awaiting review.

We designed the navigation, record layouts, review controls, visual system, and phone interactions. Shared interface patterns connect a project's overview with its individual records and show the actions available in each context.

Visit hykeep.app

The written summary establishes the project's state first. Delivery figures, risks, and team information provide the detail behind it.
Contrast on amber
6.04:1
The documented light-theme button pair: Keep amber with its dark foreground. This measures one color pairing, not the whole interface.
Rules for the phone
10
The mobile design plan defines ten guidelines for navigation, reading, editing, and touch interactions.
Audit findings
764
The copy audit records 764 finding rows across labels and messages. Rows can cover more than one string; this is audit scope, not a usability result.
Record codes, status labels, and shared controls connect Home, Insights, Queue, tasks, Time, and the journal.

We connected incoming work to requirements and delivery.

People and agents

New work needs a clear entry point and a visible connection to its purpose. We designed the ask field, feedback inbox, requirement links, and board around that progression. Consistent record names and status labels carry the context from capture into delivery.

  • The ask field gives people a place to ask about project work or request a draft, before choosing a specific record view.
  • Feedback uses an inbox: the selected item sits beside the list, keeping its source and surrounding work in view.
  • The requirement band keeps a task's purpose close to its execution. Its code, title, and link lead back to the requirement being delivered.
  • Lane counts distinguish the total workload from the cards currently shown. Show more reveals further work within the same status group.

We made relationships, changes, and review visible.

  • Threads makes the links between project records visible, grouped by cycle. Opening a record keeps that relationship view available as context.
  • The activity rail places recorded changes beside the task. A reviewer can inspect its history while keeping the work itself in view.
  • Queue separates proposed decisions, published updates, and public shares from committed work. Approval requires manager permissions; the in-app assistant cannot approve. Other agent actions can write directly.
  • The journal gives updates and decisions a dated reading order. Serif headings distinguish entries from the controls and supporting metadata.

We gave planning, execution, and reporting their own views.

Requirements define the work, the board organizes its current status, and the report summarizes delivery. Each view uses the same record vocabulary at a different level of detail.

We paired amber actions with cool surfaces and serif titles.

Color

  • Keep amber

    Primary actions and focus, with separate light and dark accent values.

    1. Light theme#DA7E07
    2. Dark theme#FE9D39
    3. Text on it#11171D

  • Humanely blue

    A secondary accent shared with the Humanely family.

    1. Light theme#0071D0
    2. Dark theme#2B97EE

  • Cool ink

    Cool neutral roles separate surfaces, boundaries, and text.

    1. Page#F1F4F7
    2. Field#E5E8EB
    3. Line#D2D4D7
    4. Strong line#BBBEC1
    5. Quiet text#7E8083
    6. Muted text#5B5E61
    7. Text#191B1D

  • Status

    Semantic color roles distinguish status and feedback.

    1. Done#519962
    2. Waiting#D79628
    3. Info#248FCC
    4. Blocked#D73431

Type

  • Geist

    400 · 500 · 600

    Show the per-person cost before checkout

    Interface labels and body text

  • Source Serif 4

    Customer onboarding

    Page and record titles

  • Geist Mono

    400 · 500

    ONB-301 · 21h 10m

    Record codes and figures

  1. Display30px / 33px
  2. Stat22px / 25px
  3. Body14px / 22px
  4. Label13px / 18px
  5. Meta12px / 17px
  6. Footnote11px / 15px

Lucide

  • Plus
  • Check
  • Arrow Right
  • Clock
  • Trash 2
  • Arrow Up Right
  • Calendar Range
  • Search
  • Sparkles
  • Pin
  • Pencil
  • Lock
  • Users
  • File Text
  • External Link
  • Download
  • Alert Triangle
  • Check Circle 2
  • Ban
  • Layers
  • More Horizontal
  • Link 2
  • Calendar Days
  • Activity
  • Paperclip
  • Inbox
  • Eye
  • Scroll Text
  • Message Square Text
  • Refresh Cw
Geist carries labels and body text, Source Serif 4 distinguishes titles, and Geist Mono identifies codes and figures. Color roles keep actions distinct from status.
These static renders of Keep's components show how cards, thread nodes, charts, and journal entries share spacing, type, and surface conventions.
Drag the divider to compare the same requirement in light and dark themes. The content hierarchy and control positions stay consistent.

We adapted board navigation and editing for touch.

On a phone

The phone board presents one lane at a time, with counts on its tabs and a Move action on each card. Property editing uses bottom sheets. These choices keep the work available on a narrow screen without relying on desktop dragging or hover.

Lane tabs and Move controls make task movement explicit. The journal and project overview adapt their reading layouts to the available width.

Credits

Team

  • reDesign UI/UX design, design system, interface implementation
  • reLabs Product engineering

Next project: Ive

Ive. A workspace for brand, knowledge, and marketing