Beta Testers
Knecht is in a closed beta. This page covers what happens after you've applied: getting an instance, setting it up, and redeeming your OpenCode credit.
Managed or Self-Hosted
Before anything else, decide where your instance runs. Both options are the same software with the same setup flow, GitHub App, and updates. The difference is who operates the server and where your data lives.
Pick managed if you want to test Knecht without touching a server. Pick self-hosted if your projects' data must not leave your infrastructure, or if you want to evaluate the install and update experience as well. Installation lists the server requirements, Maintenance what running it involves. Tell us which one you want in the mail after your application.
How Onboarding Works
Get an Instance
With managed hosting, you receive the URL of your instance from us and skip ahead. For a self-hosted instance, follow Installation on a fresh server. Both end at the same point: the dashboard is reachable under its domain.
Set up the Instance
The first visit creates the GitHub App and signs you in. Setup walks through it, including inviting your team.
Add the First Project
Connect a repository, paste its env, upload a database dump, and boot it. Projects covers the guided setup and what the project page offers afterward.
Getting Your OpenCode Credit
The credit lives in an OpenCode workspace we manage. You do not need an OpenCode account of your own:
Receive the Key
We create a key for you in our workspace and send it to you. It starts with oc_sk_ and is capped at your credit.
Enter the Key in Knecht
In your instance, open Settings > Agent. Pick "OpenCode Zen" as the provider, paste the key, and choose a default model from the list.
sk-, no longer work. If your instance still uses one, write to hallo@knecht.works and we send you a new key.