-
Notifications
You must be signed in to change notification settings - Fork 0
Evaluate one OSS or self-hosted provider alternative #2
Copy link
Copy link
Open
Labels
enterprise-hardeningSecurity, reliability, observability, governance, or production readinessSecurity, reliability, observability, governance, or production readinesshelp wantedMaintainer-approved help is welcome.Maintainer-approved help is welcome.oss-alternativeOpen-source or self-hosted replacement research or implementationOpen-source or self-hosted replacement research or implementation
Description
Metadata
Metadata
Assignees
Labels
enterprise-hardeningSecurity, reliability, observability, governance, or production readinessSecurity, reliability, observability, governance, or production readinesshelp wantedMaintainer-approved help is welcome.Maintainer-approved help is welcome.oss-alternativeOpen-source or self-hosted replacement research or implementationOpen-source or self-hosted replacement research or implementation
This product foundation intentionally keeps paid-provider coupling visible instead of hiding it.
For this repo, the current paid or hosted risk areas include:
LLM APIs, hosted realtime backends, hosted auth, hosted deployment
Candidate OSS/self-hosted directions already identified:
OpenHands/SWE-agent style runner evaluation, PostgreSQL event store, Docker or Firecracker-style sandbox direction, Ollama/vLLM adapters
What would help
Pick one provider risk and produce a focused evaluation:
Good outcome
A short markdown note, small adapter spike, or issue comment with verified evidence is valuable. The goal is practical contributor learning, not a broad rewrite.