Hosted beta
Request access for a managed worker path. Submitting interest records a request; it does not imply immediate installation access or general availability.
Open hosted beta requestGitHub-triggered familiar delivery
Assign bounded work. Get inspectable delivery back.
OpenCoven for GitHub connects repository work to a familiar execution path with Check Runs, status evidence, draft pull requests when commits exist, and Cave oversight. Hosted access is gated; the self-hosting path is documented publicly.
The work stays legible in GitHub.
The current evidence-backed loop is issue → Check Run → familiar status → draft pull request when commits exist → human oversight. It is not presented as an unrestricted autonomous teammate.
-
Assign bounded work.
Start from a GitHub issue or the repository trigger configured by the worker.
-
Watch the Check Run.
Status and execution evidence remain attached to the repository instead of disappearing into a private dashboard.
-
Receive familiar status.
The familiar reports progress while remaining bounded by worker and repository policy.
-
Review the draft pull request.
When commits exist, delivery returns as a reviewable draft pull request rather than an invisible mutation.
-
Keep Cave oversight.
Cave remains the human-legible oversight surface for the broader OpenCoven workflow.
Choose the deployment path you can verify.
Both destinations are first-party and registry-backed. Hosted beta interest uses a prefilled GitHub issue rather than an opaque third-party form.
Self-hosted worker
Run the worker under infrastructure and provider configuration you control, following the canonical repository documentation.
Read self-hosting docsInspect the implementation evidence.
This route is subordinate to the repository, worker documentation, and checked-in public product registry. Those sources—not landing-page copy—own implementation truth.