AI Workflows for DDEV Projects

Knecht

2 min read Original article ↗

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

These teams are testing Knecht in the beta right now.

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

From an issue, a label, or a mention.

Jira

From a ticket or a label.

Cron & Webhook

On a schedule or a security advisory.

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.

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.

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.