KeelenFor people building software at work
Build the tools your company needs while you focus on your main work.
Updated 29 September 2026
Keelen builds internal tools while you stay focused on your main job. Describe the tool your team needs. Connect a GitHub repository and your AI provider credentials. Keelen plans the work and turns it into pull requests. You review the results, answer questions, and decide when changes merge.
You have three common options for a small request tracker. A tracker or form that your company already uses needs no new code. An AI app builder can generate and host a simple app. Keelen fits when you want the code in your GitHub repository, reviewed pull requests and later changes while you do your main job. You choose where it runs.
From a request to a tool your team can use. This example shows software you could build. Your project owns deployment and colleague access.
Business request
Define a reporting dashboard and who needs it.
GitHub work
Keelen plans tasks and opens pull requests in your repository.
Human review
Review changes, answer questions and choose what merges.
Deployment
Use your project's deployment process and access rules.
Colleague use
Your colleagues use the tool where you deploy it.
One useful project can help a whole team
An internal tool often starts with a daily problem. A useful artifact is hard to find. A report gets rebuilt each week. Information gets copied between systems. Give that project a place to grow while you do your main work.
How colleague requests work
Give your colleagues Keelen workspace access. Then they can send ordinary change Requests. They do not need to connect their own GitHub account. You still own access and priorities, and accepting the result is still your job.
Workspace access covers more than one produced tool. Plan seats decide who is a Keelen member. The tool you build has its own sign in and access rules once you deploy it.
Example project: a shared skills and artifact hub
Build a company library for reusable Claude skills and artifacts. Colleagues upload them there. The hub makes them searchable and offers its own MCP service. A colleague can ask Claude for a resource and get it back in the chat. Add storage, sign in, and access rules to the hub's requirements.
Keelen's MCP lets you steer development. You can submit requests, read progress, and answer questions. The hub's MCP is a feature of the software the project builds. It runs through your chosen deployment. Once the hub is deployed, colleagues can use it like this.
A colleague uploads a reusable skill or artifact to the hub.
Another colleague asks Claude to find a resource for their task.
Claude retrieves it through the hub's MCP, subject to the access rules the hub enforces.
More useful projects to hand over
Start with a clear request for one of these projects.
A reporting dashboard that replaces a recurring manual report.
An integration that moves information between the systems your team uses.
A request portal that gives a recurring process a shared place to live.
An MCP service that lets an AI chat use an internal tool.
Steer the work from the tools you already use
Keelen's MCP works with a compatible AI assistant. It can submit requests and read progress. It can also help resolve decisions. Steer development from your chat. Or work from the Keelen dashboard. The first account and GitHub connection steps can still need email or a browser.
Keep control of the changes
Two settings decide how much each project may do on its own. Plan review can require a non technical sign off, a developer sign off, or both, before any code is written. The merge policy is auto merge, a pull request left open for you to merge, or a branch with no pull request. You can pause work when priorities change. Your project's checks and acceptance criteria guide the work.
Keep the tool improving after the first version
Queue small fixes and upgrades beside your team's other work. Keelen can run eligible tasks outside working hours. It uses the project's approval and merge settings. As the software changes, run the Security, Legal and Controls scans again. Your own agent or scheduler sets the timing. It sends repeat scans through MCP.
How a Request becomes the next change
A Request can become a roadmap item. It can also come back as a question for you. Keelen expands the top roadmap item into tasks. Each task has acceptance criteria. Keelen picks the next eligible task. With manual merge, you can compare a pull request with those criteria. Then you decide whether to merge. Capacity and provider limits can delay work. A missing dependency can also stop a task. A failed check can stop a task. Needs you holds decisions that need your answer.
How it works
Choose a useful project
Describe the problem and who will use the tool. Say what a useful first version should do.
Connect the project
Connect a GitHub repo in Keelen. Add credentials for a supported AI provider. Send your first request.
Keep your main work moving
Keelen works through the project. Review changes and answer questions when a decision needs you.
Put the tool to work
Use the project's deployment process to share the tool with colleagues. Apply the access rules that project needs.
Not for you if
- Your company's rules may block a GitHub repo. They may block a supported AI provider. Keelen needs repo access to run development. It also needs AI credentials.
- You want a ready made hub with hosting and colleague access already set up. Keelen builds the software in your repo. You decide where it runs and who can use it.
Start with one useful tool for your team.
Start with one small project. Choose manual merge if you want to review and merge each pull request yourself.
Flat tiers from $29 a month plus your own coding model usage, no markup on tokens. Keelen pays for chat. 14 day trial, no card.