Business apps your team and your agents both work in
Keeper gives your records and documents one structured shape that people and AI both understand. Your team works in the web app and on the phone. Your agents work through the Claude Code and Codex plugins, with the same permissions and the same checks.
Free subscription. Pay only for the AI you use.
Built for CRM and sales, proposal writing, service operations and back-office work.


Move the work out of scattered tools
Keeper gives a small team one working system without turning the improvement into a software project.
Before Keeper
- —Hours, issues and deals split across sheets and chats
- —Status lives in someone's head
- —Every AI session product and artifact is copied by hand into the real record
With Keeper
- Apps shaped around the way your team already works
- Clear ownership, status and history
- People and agents work on the same live records and apps
Without the rollout
- —No builder console to master
- —No specification handoff or development queue
- —No per-tool subscriptions to stitch together
Real apps, you can build from a conversation
Every app below was described to an agent and built with Keeper. Use one as a starting point, or describe the process only your team has.
Your own Time tracking for free - Hours, logged the way people actually work.
Type straight into a weekly grid, or log an entry from your phone in two taps. Admins set up clients, projects and tasks once, each person sees only the projects they've been given, and the month closes with a locked period and an export of exactly what you'll bill.
- Weekly grid
- Quick add on phone
- Project access
- Month-end lock

Issues, a board, and an Agent that picks work up.
Report bugs and requests from templates, discuss them in one timeline, and plan on a board with WIP limits and milestones. When an issue needs thinking through, give it to the Agent: it asks its questions on the issue and writes the design for the team to review.
- Board
- One timeline
- Milestones
- Agent queue

Every coding-agent session reports into one project.
Agent sessions push what they achieved and what comes next, from any machine. Many sessions fold into one project, so the team sees every running piece of work on a timeline with its dependencies, and an agent writes the priority review.
- Session check-ins
- Timeline
- Dependencies
- Priority review

Website content planned from research, worked step by step.
Each keyword opportunity becomes a task with its target page, priority and due date. Steps run in order (research, draft, review, publish, measure), each held by a person or the Agent, and the outcome is recorded once the page has had time to rank.
- Playbooks
- People and Agent steps
- Calendar
- Measured outcomes

Every proposal's stage, owner and due date in one pipeline.
Drag proposals from qualifying to sent and see the value in each stage. Each one keeps its timeline of comments and changes, and the customer's documents sit one click away instead of in someone's downloads folder.
- Pipeline board
- Stage totals
- Customer folders
- Timeline

Customers, equipment and jobs, structured instead of scattered.
An air-conditioning service company described its dispatch process. The app it got: a job board from request to completion, customer and equipment records with full service history, recurring maintenance that schedules its own visits, and a phone view for technicians.
- Dispatch board
- Equipment history
- Recurring maintenance
- Technician phone view

Creative Review
An agency delivers ad creatives; the team reviews each version, comments per field, suggests wording, and accepts the plan once everything is approved.
Proposal Studio
A shared library and each opportunity's brief. Ask your own agent to draft or revise a proposal; it lands in the opportunity's folder for review.
Meeting Notes
Notes with an AI summary and suggested action items that wait for someone to accept them before they become tasks.
Describe it. Review it. Run on it.
Start with what you track, who does what, and where work gets stuck. Your agent builds the complete app, checks it, and shows you the change before anything goes live.
Conversation first
Start with the work, not a software specification
Talk through the process in the words your team already uses. The agent turns that brief into connected records, views, navigation, workflows and access rules instead of stopping at a starter screen.
- Refine the app in the same conversation
- Keep it beside your workspace files, chats and agents
- Describe the change when the process changes

Hand work to an agent. Review it where the work lives.
Keeper apps aren't just somewhere to store answers. Work can be given to a connected agent, and what it produces comes back into the same records, comments and documents your team already uses.
Issues
Give an issue to the Agent
The Agent asks its questions on the issue, writes a solution design once they're answered, and revises it from the team's comments. Everything stays in the issue's timeline.
- Questions and answers stay in the conversation
- Designs are documents the team can comment on
- Hand it back to the Agent with one note

Content Roadmap
People and agents share one plan
Each content task runs as a list of steps. The Agent takes research and drafting, people take review and publishing, and every step shows who holds it and where it stands.
- Agents pick up their next step from a queue
- Handovers land in the task's discussion
- One step is ready at a time, so nothing starts early

Agent Projects
Manage your Claude and Codex/ChatGPT sessions
Ask the agent to push the session to your projects. Keeper records what it achieved and what comes next, so tomorrow's session (or a teammate) picks up where it stopped.
- History of every session and human edit
- Copy a ready prompt to pick a project back up
- Comments the next agent session reads

Agents connect from Claude Code or Codex. Keeper decides what an agent may read, checks what it sends back, and saves it through the app's own workflows. Results that need a person wait for review.
Scheduled follow-ups and weekly reports can run on app data too. See Agent Orchestration →
Each app decides what people hear about
Notifications come in topics the app defines. They reach each person in the Keeper inbox, by phone push and by email, and an app admin can send a topic to a team Discord channel. Messages lists what reached you across all your apps.
Topics
Asks and updates
An app groups its notifications into topics, such as an issue tracker's The Agent's questions or Shipped. Every app also has an App news topic its admins post to.
- Asks need someone to act: answer a question, review a plan
- An ask has a button that says what to do, and stays in Waiting on you until its record moves on
- Updates are for information; an agent posts one when you ask it to, for example to announce a fix

Asks by email, and a daily digest
Keeper emails each new ask with a button that opens the record. Once a day, a digest lists the asks still open and the day's updates.
- One email per ask, with its button
- A daily digest of open asks and updates
- Turn either off, or mute single topics

Discord
Post a topic to a team channel
An app admin connects a topic to a Discord channel by pasting the channel's webhook. Keeper sends a test message first.
- Each new item posts its topic and a link to the record
- Opening the link still needs access to the app
- When an ask is answered, its message changes to Resolved
- Update topics can include the agent's own text

Documents
Documents live next to the work they belong to
A proposal, a solution design or a draft blog post sits on its record, not in a separate drive. Review it where it was written, and keep every file as plain Markdown in your workspace.
- Select a passage and comment on it
- Status and revision on every document
- Agents draft and revise into the same folder

Reports
Pivot tables and charts over your records
A summary page adds up all of an app's records on the server, not only the rows a list has loaded. Each person's totals count only the records they are allowed to see.
- Pick a month, quarter or year and page back and forth
- Tables with subtotals, exported to CSV
- Bar and line charts, and top-10 rankings
- Click a number or a bar to open the records behind it

One brief becomes a complete service system
A small air-conditioning maintenance company needed to coordinate customers, equipment, technicians, visits, parts and recurring service without stitching together more spreadsheets.
The brief
Dispatch new work, keep service history per unit, schedule recurring maintenance, and give technicians a useful phone view.
The records
Connected customers, equipment, work orders, technicians, service plans, parts and activity.
The daily workspace
A dispatch board, today's jobs, equipment and maintenance views, and forms for each step.
The follow-through
Completing a job advances the maintenance schedule and books the next visit; the AI drafts the customer's service report.

The phone view is part of the app, not a second project
Technicians open assigned work, check the equipment's history and update the job from the same records the office sees.
The details that make people actually use it
Every Keeper app gets the same everyday features, so a new app feels finished from day one.

A home screen on the phone
Install Keeper like an app. Quick add, the apps you used last, and each app's own phone layout.
My work
Everyone sees what's assigned to them, what they opened, and what nobody owns yet.
Notifications
Assignments, replies and asks reach your inbox, your phone and your email.
Links to the live record
Share a link to a view or a record with an access level and expiry, not another exported copy.
Access by role and project
Admins see setup, members see their work, and project grants decide who sees which records.
Search and export
Filter and search lists, then export the complete result to CSV.
Change the app without risking the data in it
Every change is checked and shown to you before it goes live. Changing how the app works never touches the records your team has already entered.
Check the whole app
The complete new version is validated before anything is staged.
See exactly what changes
A file-by-file comparison of what will be added, changed or removed, before you approve it.
Keep live records
Changing the app leaves existing records in place. Replacing data takes an explicit request and the right permissions.
Build apps and work in them from your coding agent
Two plugins from MechaBee's public Git marketplace. Sign in once with your MechaBee account, then build and work from the agent you already use.
Keeper App Author: build
Describe how your team works and get a real app: records, boards, dashboards and workflows. The agent validates the app and shows you the diff, and nothing goes live until you approve it.
Keeper Workspace Content: work
Save, report and look up work in your apps: carry out an app's procedures, read the views it shares with agents, and read and revise documents in your workspace.
Exact commands, permissions, updates and troubleshooting.
Plugin support
For installation, sign-in, authoring, or deployment help, visit the support guide or email info@mechabee.com.
Free to run. Pay only for the AI you use.
Keeper comes with a free subscription. You pay only for the AI your apps use inside MechaBee. Building from Claude Code or Codex runs on your own plan.
Start free- Free subscription, no credit card to start
- AI used inside MechaBee is paid as you go
- Building from your coding agent uses your own plan
- Every app runs on desktop and phone
Describe the work. Review the app. Put it to work.
Start with one real process your team needs to run more clearly.
Free subscription. Pay only for the AI you use.