For people building software at work

Build the tools your company needs while you focus on your main work.

Updated 6 September 2026

Keelen builds internal software while you get on with your main job. Describe the tool your colleagues need, connect a GitHub repository and your AI provider credentials, and Keelen plans the work and implements it as pull requests. You review the results, answer its questions, and decide when changes merge.

Start a work project

One useful project can help a whole team

An internal tool can start with a problem you encounter every day: a useful artifact nobody can find, a report someone rebuilds each week, or information that has to be copied between systems. Give that project a place to progress while you concentrate on your main responsibilities.

Example project: a shared skills and artifact hub

Build a company library where colleagues upload reusable Claude skills and artifacts. The hub makes them searchable and exposes its own MCP service, so a colleague can ask Claude for a resource and retrieve it in the chat. Include storage, sign in, and access rules in the requirements for the hub.

Keelen's MCP lets you steer development: submit requests, read progress, and answer questions. The hub's MCP is a feature of the software the project builds, served through your chosen deployment. Once the hub is deployed, colleagues can use it like this.

  1. A colleague uploads a reusable skill or artifact to the hub.

  2. Another colleague asks Claude to find a resource for their task.

  3. 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.

  1. A reporting dashboard that replaces a recurring manual report.

  2. An integration that moves information between the systems your team uses.

  3. A request portal that gives a recurring process a shared place to live.

  4. An MCP service that makes an internal tool available from an AI chat.

Steer the work from the tools you already use

Keelen's MCP lets a compatible AI assistant submit requests, read progress, and help resolve decisions. You can use it to steer development from your usual chat, or work from the Keelen dashboard. Initial account and GitHub connection steps can still require email or a browser.

See how Keelen's MCP works

Keep control of the changes

Set plan approval and merge controls for your project. Keelen can open pull requests for you to review and merge, and you can pause work when priorities change. Your project's checks and acceptance criteria guide the work.

How changes are checked

How it works

  1. Choose a useful project

    Describe the problem, who will use the tool, and what a useful first version should do.

  2. Connect the project

    Create or connect a GitHub repository in Keelen, connect credentials for a supported AI provider, and submit your first request.

  3. Keep your main work moving

    Keelen works through the project. Review changes and answer questions when a decision needs you.

  4. Put the tool to work

    Use the project's deployment process to make it available to colleagues, with the access rules that project needs.

Not for you if

  • You cannot connect a GitHub repository and a supported AI provider within your company's policies. Keelen needs repository access and AI credentials to run development.
  • You want a ready made hub with hosting and colleague access already set up. Keelen builds the software in your repository; you configure 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 model usage, no markup on tokens. 14 day trial, no card.