Skip to content
Keep
Get started

Private beta · For teams delivering software

Your team. Your agents.One shared workspace.

Requirements, tasks, documents and feedback in one project, shared by your team and the AI tools you already use.

See it in action
The Keep Home screen in Keep’s dark theme, in a sample workspace: a welcome greeting, My time and today’s work, the Queue of what waits for your decision, and the projects, activity and attention that need you.

Works with the coding agents and AI assistants your team already uses.

Explore supported connections

Home

Today’s work, on one screen.

Home shows your logged time, today’s work and the Queue of what waits for your decision, with a direct link into each project.

Plan, work, journal and artifactsin one project.

Take the full product tour

Plan

Define what to deliver and when.

Requirements define the scope. Modules group the parts of your product. Cycles set the delivery window.

See how planning works
Keep’s Plan view: requirements grouped by day with their status, priority and version.

Work

Track every task through to done.

Tasks, bugs and chores, each with an owner, a status and progress. View them as a list, a board or a timeline.

Explore the work views
Keep’s Work board: task cards in Open, In progress and In review lanes.

Journal

Record decisions next to the work.

Notes, updates, feedback, questions, risks and meeting outcomes, linked to the tasks and requirements they concern.

Explore Journal and feedback
Keep’s Journal Stream: dated notes, decisions and updates in one column.

Artifacts

Store documents and files in the project.

Documents, files, links and embeds, with versions, collections and sharing.

Explore artifacts and sharing
Keep’s Artifacts view: a collection, documents and files in a project.

Move work forward from your AI assistant.

A connected assistant can create a task, record a decision or save a document to the project, without opening Keep.

From an idea to shipped work, in one project

  1. Idea

    Describe the idea.

    Tell the assistant you already use: let customers export the per-person cost before checkout.

  2. Requirement

    A requirement is created.

    Filed in Customer onboarding as an open requirement, ready for review.

  3. Task

    A task is assigned.

    A task for Priya, linked to the requirement it delivers.

  4. Agent

    An agent does the work.

    Your agent picks up the task and records the handoff. The team sees what changed without opening Keep.

  5. Shipped

    The team is informed.

    An update is posted: the pilot is ready for review, with the requirement and the task linked.

Connect once

How it works

  1. Sign in once

    Your assistant connects to Keep over MCP.

  2. Approve the connection

    From then on, your assistant is connected.

  3. It acts as you

    Inside your own permissions.

Where things stand

Step 03, in action: Example conversation
You

Where is Customer onboarding this week, and who has been on the export?

Your assistant

Sprint 2, activation polish. Thirteen cards in view: three in review, two done, four of them blocked.

Two need someone:

  • ONB-131 Self-serve billingWaiting on the Stripe webhook, two days late
  • ONB-182 The export job queueBlocked, due Sep 30

ONB-180, render the report as PDF: eleven hours logged so far, the last two by Alex Rivera.

Read from the project’s own records, not from a summary someone wrote

Setup guides

Availability can depend on your client version and your team’s settings.

Example requests. A few owner-only actions stay in the app, like creating a project or emptying the recycle bin.

Connect your AI toolsSee the details in the product tour

Mobile

The full workspace, designed for mobile.

The same projects and records as in the browser, with a layout built for one-handed use.

See the phone view in the product tour
Keep’s Work board on a phone in a sample workspace, showing the Blocked lane of Customer onboarding: thirteen tasks in view, four blocked, and three cards (self-serve billing blocked on the Stripe webhook and two days late, an SSO handoff, and the export job queue), each with a Move button.
Keep Home on a phone in a sample workspace: a greeting and a box to ask for what you need, two suggestions (review four requests in the Queue, draft the cycle status update), then the Queue, with three decisions and a question waiting.
Keep’s Journal on a phone in a sample workspace: the stream grouped by day, with feedback sent from a website about the per-person cost, a standup note, and a published update about what lands before GA.

  1. Review your queue

    The decisions and questions waiting for you, and the hours you have logged.

  2. Update tasks

    Change a card’s status, reply or log time.

  3. Follow the journal

    Decisions, updates, questions and feedback, grouped by day.

Every record, linked to its context.

Artifacts, requirements, tasks, updates and feedback link to the records they relate to. The thread wall shows those links across the project.

  1. Artifacts
  2. Plan
  3. Work
  4. Journal
  5. Reports
See it in Keep: the thread wall
Read the walkthrough

The Customer onboarding thread wall, with curved connections between stacked requirements, tasks, feedback and artifacts.

  1. See the project’s threads together, grouped into cycles.
  2. Open the PDF export task without losing its connections.
  3. Explore the stack of artifacts behind the work.

Recorded in Keep with sample data. Silent video.

Dedicated workspace data. Access you control.

Explore Keep’s dedicated tenancy, data isolation, security controls and Cloudflare foundation.

Explore Trust & security

Frequently asked questions

Who Keep is for, how it works with your tools and how to get started.

Who is Keep for?

Teams delivering a product, a project or client work—with people, AI agents, or both. Keep gives the plan, day-to-day work and decisions a shared home.

Explore the workspace
Do I have to keep another app open?

You can plan, update work and save documents through a connected AI client. Open Keep when you want the board, the wider picture or a conversation with your team.

Connect your AI tools
Can we start with just tasks?

Yes. Start with tasks, owners and progress. Bring in requirements, modules and cycles when the project needs a more structured plan.

See your ways of working
Does Keep work on a phone?

Yes. Keep’s screens are designed for phones: the same workspace you open in a browser, laid out for one-handed use. Check your queue, move a card, read what changed, reply and log time. There is no separate app to install.

See Keep on a phone
Can I run my project from my AI assistant?

Mostly, yes. A connected assistant can read the project and write to it: file an idea or a requirement, log a bug, open a task, publish an update, check where someone’s hours went, log time, and read or share a document. It acts as you, within your permissions, and a few owner-only actions stay in the app.

See what you can ask for
Can I use Keep for documents on their own?

Yes. Artifacts can live independently in Docs or inside a project. Write documents, upload files, organize collections and share links with optional passwords and expiry.

Explore documents and sharing
Can customers give feedback without an account?

Yes. Add the Feedback Agent widget to your website. Visitors can point to an element, annotate a screenshot and send feedback without a Keep login, then revisit their submissions in the same browser.

See the feedback flow
How do we get started?

Keep is in private beta. Use Get started to sign in to an existing workspace or request access for your team. We’ll help you choose a first project and connect your tools.

Sign in or request access

Private beta · by invitation

Bring a real project.

Bring your team and your AI agents into one shared workspace. Sign in to your workspace or request access.

Get started with Keep hello@hykeep.app