Opsiforce

What does Opsiforce do?

Opsiforce's README calls it a "self-hosted, multi-tenant web platform for building and running AI-generated apps inside your own infrastructure". You deploy it once to a Kubernetes cluster and your team uses it from the browser. Each user can create multiple projects; every project is its own chat with an agent backed by an isolated Linux pod where the agent can write code, run commands, install packages, edit files, inspect data, and serve the resulting app through the platform.

The README positions it as an open alternative to Lovable, Base44 and AI coworker-style app builders, with two different assumptions: the platform should host and run the app, not just generate code to deploy later; and the generated app should not be locked to one frontend framework, one backend runtime, or one database. Each app runs in a generic container with a persistent filesystem, project-level credentials, environment-specific configuration, and HTTPS routes managed by the platform.

Key facts

• Licence: AGPL-3.0 on the code.
• Runtime: Kubernetes-native. The README says the backend, runtime proxies, LLM gateway and per-project agent pods all run inside a cluster.
• Agent: OpenCode, embedded into the Opsiforce frontend rather than iframed as a separate product.
• Per-project pod: an app server, OpenCode agent, VS Code web IDE, database viewer and a persistent workspace volume.
• Persistent workspace: source code, git history, OpenCode session data, app SQLite databases, generated files, IDE settings and uploaded files survive pod replacement.
• Reverse proxy: Traefik ingress with OAuth2 Proxy and OIDC per-environment app auth.
• Environments: every project has a Development environment and can publish into Production or custom environments. Each has its own pod, files, URLs, auth mode, schedules and environment variables.
• LLM gateway: Bifrost gives each project virtual LLM keys with usage tracking and budget enforcement. Agent pods never see real provider keys.
• Service gateway: agent-built apps call centrally managed services, such as email, through per-project gateway tokens.
• Default LLM options: a ChatGPT or Codex subscription you already pay for, or your own OpenAI API key. Bifrost also supports Anthropic, Google, Azure OpenAI, AWS Bedrock, OpenRouter, local and self-hosted models.
• Local development: a single yarn && yarn dev runs the orchestrator on minikube; browser entrypoints are exposed under *.opsiforce.localtest.me.
• Prerequisites: Docker, kubectl, Helm, Go, Tilt, minikube, mkcert, Node 24 and Yarn. On macOS Quickstart installs them via Homebrew; on Linux you install them yourself.

What does it replace, and where does it fall short?

Opsiforce replaces Lovable, v0 and Bolt for a team that wants the chat-to-app loop plus hosting on infrastructure it owns. See the open-source alternatives to Lovable page.

Where it falls short: it is a Kubernetes-native platform rather than a desktop app, so running it needs cluster operations, Traefik, Postgres, Redis, Bifrost and a reverse proxy on top of the agent and the UI. For a single developer wanting Lovable's workflow on a laptop, Dyad is a lighter fit. The maintainers do not run a hosted service, so trying Opsiforce means standing it up yourself. The project is young and the README does not state a stable release.

How does Opsiforce run?

Local development: yarn && yarn dev installs dependencies, starts a minikube cluster, generates a locally trusted TLS certificate, brings up Postgres, Redis, ingress and the LLM gateway, builds the images, migrates the databases, connects an LLM, and opens the app signed in as a local dev user. The quickstart is idempotent and resumable; yarn dev --reset tears everything down for a clean start.

Production is a Kubernetes deployment. The README says Opsiforce is designed to be branded, embedded into another product, and used as infrastructure for teams that let their users create dashboards, reports and tools without leaving the product boundary.

Who is Opsiforce for?

A team that wants to embed an AI app builder into its own product, run user-generated apps on infrastructure it operates, and keep each app's workspace and agent session across pod restarts. For a solo builder on a laptop without a Kubernetes cluster, see Dyad, Chef or Onlook on the open-source alternatives to Lovable page.

What limits does the README state?

Opsiforce is Kubernetes-native and local development mirrors that: minikube or a cluster is required. The platform's edge proxy, HTTPS wiring and per-environment app auth are part of the design, not optional, so a hobbyist deploy still needs the reverse proxy and the LLM gateway. On Linux the cluster uses the Docker driver and minikube tunnel binds ports 80 and 443, so the quickstart needs one sudo prompt to grant those privileged ports.

Questions people ask

Is Opsiforce open source?

Yes, under AGPL-3.0, which is an OSI-approved licence. The README states the licence and links to the LICENSE file. The AGPL means that if you run a modified Opsiforce as a network service, you must offer the source of your modifications to users of that service.

Does Opsiforce need Kubernetes?

Yes. The README calls it a Kubernetes-native platform and says the backend, runtime proxies, LLM gateway and per-project agent pods all run inside a cluster. Local development uses minikube; production is a real cluster. There is no non-Kubernetes mode documented.

Can I use my own ChatGPT or OpenAI plan?

Yes. The README says the default local proxy lets you drive a ChatGPT or Codex subscription with a one-time browser sign-in and no API credits, or your own OpenAI API key. The Bifrost LLM gateway also supports Anthropic, Google, Azure OpenAI, AWS Bedrock, OpenRouter and local or self-hosted models. The agent pod never sees real provider keys.

How does Opsiforce compare with Lovable?

Lovable is a hosted product that generates and runs apps on its own cloud. Opsiforce is a self-hosted platform that does the same inside your own Kubernetes cluster, with per-project pods, persistent workspaces, HTTPS routes and multiple environments. The README's own framing is that building the app is only half the job; the platform should also host and run it. See the open-source alternatives to Lovable page.

What survives a pod restart?

The README says the pod is replaceable and the workspace is durable. The persistent workspace stores app source and git history, OpenCode session data and chat history, app SQLite databases and generated output, uploaded files, agent config and skills, and VS Code settings and extensions. If a pod is suspended, evicted or recreated, the same workspace is mounted back into the next pod.

Sources

• Opsiforce README and LICENSE: github.com/SimaDevelopment/opsiforce, read 2026-10-12. The README states the AGPL-3.0 licence and names OpenCode as the embedded agent and Bifrost as the LLM gateway.