Knecht

Your Agency's Maintenance Robot.

A ticket starts a workflow. Knecht boots the project, does the task inside it, and opens a pull request with a preview. Self-hosted, for agencies that maintain many projects.

Become a Beta TesterExplore the Docs
Knecht, the robot helper with a CRT screen head
AnwesoftJustin HoltSamuel ReichörMore Things DigialAngelo KeirsebilckFredmansky

Knecht Connects to the Tools You Already Use.

A ticket comes in, a result goes out. Knecht boots your project and does the work in a real dev environment.

Trigger
GitHub
Jira
Plane
Linear
Let the Knecht Work

For every ticket, Knecht boots the project and runs the workflow inside it.

  1. Project Boots with Database
  2. Workflow Steps Run in Order
  3. AI Agent Where Needed
Result
Pull Request
Branch, commits, and description.
Preview Environment
Clickable, with a real database.
Comment in the Ticket
Links to the preview and the PR.

Use Cases for Agency Life.

Knecht does every task that you can describe as a workflow. These three show what such a run looks like, from the trigger to the pull request.

  1. Craft Update Workflow
    1. 1
      Schedule Fires
      Monday 06:00, project craft-shop
    2. 2
      Project Boots with Database
      ddev composer install, DB dump imported
    3. 3
      ddev craft update all
      craftcms/cms 5.10.1 → 5.10.2, 3 migrations applied
    4. 4
      Link Check on the Preview
      142 pages checked, 0 broken

Many Projects. One Knecht.

Projects, workflows, and runs in one place on your server. A workflow is written once and runs on as many projects as you connect, and every run keeps its log, preview, and result.

/projekte
Knecht Projects preview

Knecht Now Has a Discord Server.

Questions about the setup, feedback on workflows, show your first runs. We build in the open and answer ourselves.

Join the Discord
  1. Samueltoday 09:12

    v0.7.0 is out. Jira triggers can now filter by label.

  2. Matthiastoday 09:40

    First security update run across 6 Craft projects is done. All PRs green 🎉

  3. Brunotoday 10:03

    Question: can the estimate workflow also run on GitHub issues?

Where Knecht Stands.

What Knecht can do today, what we are working on, and what comes next.

Progress to the public release0%

The beta is running. Next up are the Jira integration and more beta testers.

Done

Idea Validation

We tested the concept in a reduced scope. It works.

Done

Branding and Organization

The name, the logo, the website, and the social media presence are complete.

Done

Tech Stack and Architecture

We made the basic technology decisions and validated them.

Done

Dashboard Design

The design for the dashboard is complete. In the dashboard, you make projects and workflows.

Done

Build the Prototype

A prototype exists. In it, you can make projects and workflows with an AI agent.

Done

Installer

You can install the dashboard on each Linux server.

Done

Update Service

You can install updates from the control panel.

Done

GitHub Trigger

You can set GitHub triggers that start workflows.

Done

Knecht Is Alive

You can install the Knecht dashboard on a Linux server with low effort, and it gets updates.

Done

Jira Trigger

Jira tickets can start workflows.

Done

SSH and IDE

You can make changes in the live preview containers through SSH and an IDE.

Done

Feedback Loop

After a workflow run, different feedback functions are necessary to make the output better.

Done

Langdock Support

The agent also runs through Langdock. One API key covers GPT and Claude models, and every request stays in the EU.

Done

Agent History

Every issue gets its own session. The agent keeps its environment and conversation across multiple runs.

Done

Managed Hosting

Beta testers do not have to install Knecht themselves. We host the instance for them and take care of updates and operations.

Done

Documentation and Onboarding

The docs cover the setup, workflows, and troubleshooting.

Done

Projects Without DDEV

Knecht boots projects that do not use DDEV as well.

Done

Improve Jira Integration

The Jira trigger gets more options and better comments back in the ticket.

Done

Plane Integration

Plane work items can start workflows.

Done

Linear Integration

Linear issues can start workflows.

In progress

Find Beta Testers

We look for a sufficient number of beta testers to find problems early and build the final product.

Planned

Test Actions

Workflows can run tests for projects. A fix is complete only when the tests are green.

Planned

Browser Validation

The agent examines the bug in the preview and supplies screenshots as proof.

Planned

Notifications

Slack or email sends a message when a run is complete or when it fails.

Planned

Price Model and Licenses

You can officially buy Knecht. The price model, the license, and the payment are complete.

Building in Public.

We build Knecht in the open. Each milestone is published here.

  1. October 28, 2026Security

    PHP2Shell, Node2Shell and Knecht

    What the PHP2Shell and Node2Shell vulnerabilities mean for Knecht, where an attacker could reach them, and how version 0.14 patches PHP and Node.

    Read More
  2. October 27, 2026Architecture

    One interface for AI in the dashboard

    How AI features in Knecht work through one shared tool registry and one shared loop, and why the same tools should later be reachable through MCP too.

    Read More
  3. October 11, 2026Architecture

    A Live Dashboard Without Polling

    How we moved every database query into one store per table, and how that made the dashboard update live over a single SSE stream.

    Read More
  4. October 5, 2026Dashboard

    Mailpit, Adminer and Other Tools in Each Run

    Mailpit, Adminer and other web tools from the DDEV environment now open directly from the run.

    Read More
See All Updates

Build Knecht with Us from the Start.

Knecht is in beta. Become a beta tester and shape it with your feedback.