Cloudgeni · Opengeni: Open-Source, Self-Hostable Runtime for Long-Running AI Agents in Your Product
Opengeni is an open-source (Apache-2.0) runtime and control plane for long-running AI agents. It keeps each session in a replayable Postgres event log, pauses for human approval before risky tool calls, keeps credentials out of the prompt, and runs work in a managed sandbox or on a machine you enroll. It suits product and platform teams that want to embed agents in their own app, or give them to their team through its web, desktop, Slack, and Microsoft Teams apps, without building that infrastructure themselves.
Best for
Product and platform teams building agent features into their own TypeScript/React product, or running agents for their organization, who want durable sessions, approvals, credential handling, and the choice to self-host under Apache-2.0 or start on a hosted cloud with the same API
Not ideal for
Teams that want a ready-made agent rather than infrastructure, Python-only backends that want a native SDK, small teams unwilling to operate Postgres, Temporal, NATS, and Kubernetes if they self-host, and buyers who need a mature, slow-moving platform today
Who it's for
Product engineers embedding agents in a SaaS app, platform teams running a shared agent runtime for their organization, and companies that want agent session history, approvals, and audit data in their own database
Opengeni is a serious attempt at the unglamorous layer that turns a model into a dependable product feature: a replayable event log, approvals that resume the exact call, goals that keep work going, and credentials that stay out of the prompt. Connected Machines treat hardware you own as a first-class compute target alongside managed sandboxes, and because the hosted cloud runs the same Apache-2.0 code and deployment tooling you can self-host, starting hosted does not lock you in. The costs are maturity and operations. It only launched publicly in October 2026, release artifacts arrive several times a day, self-hosting means running Temporal, NATS, and Postgres, typically on Kubernetes, and the SDK is TypeScript-only. Teams with a TypeScript product and some platform capacity should try the hosted app or the local stack on one real workflow before committing.
Who should use it
TypeScript and React product teams that want agents inside their app with approvals and user-scoped tools, platform teams that want a self-hosted agent runtime whose session history and audit trail live in their own Postgres, and organizations that want agents working on their own build servers or GPU machines.
Who should skip it
Teams that need a finished agent rather than a runtime, Python-first shops expecting a native SDK, teams that want to run Claude Code or Codex as-is in hosted sandboxes, and organizations that need a long track record and slow, predictable upgrades.
Open source
$0
Pay as you go
Credit top-ups
Free
$0
Pro
$20
Billed monthly
Max
$100
Billed monthly
Enterprise
Custom
Free tier limits: Self-hosting is free apart from your own infrastructure and model costs. On Opengeni Cloud, the Free plan gives eligible verified accounts $10 of trial credit each month for models marked as free-credit in the app, for up to 5 members. There is no separate signup bonus, and unused monthly credit does not roll over.
Note: Verified November 8, 2026. Plan credit is worth five times the Pro and Max price, refills each billing month, and is for app use only; API and embedded-product usage draws on separate prepaid credit or your own API key. When plan credit is spent, agents keep running pay-as-you-go from top-ups, which never expire; without credit on a credit-billed model, you add credit before continuing. Upgrades from Pro to Max apply immediately with a prorated charge, and downgrades take effect at the end of the billing month. Opengeni says it currently adds no platform fee on your own API keys (its docs describe an own-key fee that is paused at 0%), and connected subscriptions carry no Opengeni inference fee, though paid tools and other services may still use Opengeni credit. The model-cost-plus-5% pricing used at launch is no longer published.
API pricing
Opengeni Cloud: API and embedded-product usage is paid from prepaid credit at the model rates shown in the app, or billed by your provider through your own API key (no Opengeni fee at present). Monthly plan credit and connected subscriptions cannot be used through the API. Self-hosted: no license fee
Available models
An in-product billing or support assistant
The React conversation component and session proxy put the agent in your UI, your MCP tools act as the signed-in user, and Ask first approvals stop actions such as refunds until the user confirms.
Long-running background work that has to finish
A scheduled or webhook-triggered session with a goal keeps working across turns, survives worker restarts through the event log, and notifies your backend by webhook when it completes or needs input.
Agents on hardware you already own
Connected Machines let a session run on an enrolled laptop, build server, or GPU box with its existing files and Git credentials, connecting out so no inbound ports are opened.
Opengeni vs. TrueForge
TrueForge is TrueFoundry's MIT-licensed agent harness with persistent sessions, MCP tools, approvals, schedules, and a chat UI, API, and SDK. It documents Daytona as its sandbox provider and runs locally on SQLite or hosted on Postgres and Redis, with a custom-priced managed version. Opengeni covers similar ground with a heavier Temporal, NATS, and Postgres stack, and also offers Connected Machines, goals with success criteria, a reviewable Knowledge library, and a hosted cloud with published plans (Free, $20 Pro, and $100 Max) rather than custom quotes.
Opengeni vs. DigitalOcean Managed Agents
DigitalOcean Managed Agents is a hosted service that runs existing harnesses such as Claude Code, Codex, OpenCode, Hermes, or LangGraph apps in Firecracker microVMs, with a 16,000-tool MCP gateway and usage-based compute billing, but no self-hosted option. Opengeni runs its own agent loop, is open source and self-hostable, and focuses on embedding sessions in your product with React components and user-scoped tools. DigitalOcean fits teams that want to run an agent they already use, and Opengeni fits teams building agent features they control end to end.
What is Opengeni?
Opengeni is an open-source runtime for long-running AI agents. It provides the layer around the model: durable, replayable sessions, goals, human approvals and questions, tools through MCP or OpenAPI, credential handling, a Knowledge library, and compute in a managed sandbox or on a machine you enroll. You can use it from its web app or embed it in your own product through its API, TypeScript SDK, and React components.
Is Opengeni open source?
Yes. Opengeni is licensed under Apache-2.0, including the API, web app, workers, Helm chart, and reference Terraform. Some optional curated Skills in the repository carry their own license metadata.
How much does Opengeni cost?
Self-hosting has no license fee; you pay for your own infrastructure and model providers. Opengeni Cloud has a Free plan with $10 of monthly trial credit for eligible accounts (free-credit models only), Pro at $20 a month with $100 of monthly app credit, Max at $100 a month with $500, and pay-as-you-go top-ups that never expire. Plan credit covers app use and does not roll over; API use needs separate credit or your own API key, to which Opengeni currently adds no fee. Enterprise, in Opengeni's cloud or self-hosted in your VPC with SSO and commercial support, has custom pricing.
What do I need to self-host Opengeni?
A production deployment runs the API, web app, and two Temporal workers, backed by Postgres with pgvector, Temporal, NATS, object storage (Azure Blob, S3, or GCS), and a sandbox backend such as Docker, Modal, a cloud sandbox provider, or Connected Machines. Opengeni publishes a Helm chart and reference Terraform for AWS, Azure, and GCP, and recommends managed services for the stateful pieces. For local evaluation, one command (`bun run dev`) starts the whole stack.
Which models does Opengeni support?
OpenAI and Azure OpenAI are built in, and other OpenAI-compatible endpoints can be added by configuration. The docs also cover OpenRouter, Vercel AI Gateway, Opper, Anthropic API keys, and connecting ChatGPT/Codex, Claude, or SuperGrok subscriptions; on Opengeni Cloud, subscriptions need the Pro, Max, or Enterprise plan and work in the app only, not through the API. Admins choose which models each workspace can use, and a session can switch models mid-conversation.
What is the difference between a managed sandbox and a Connected Machine?
A managed sandbox is created per session by Opengeni, clones repositories into `/workspace`, and runs inside the deployment. A Connected Machine is a computer you own and enroll once; the agent works in a folder on it with that machine's own Git and SSH setup, and the machine connects out to Opengeni, so it needs no inbound ports. Screen control is a separate consent, and you can revoke a machine from the Machines page.
How do I add Opengeni to my product?
Add one server route that proxies the session API with your organization key, mapping your users and tenants to Opengeni workspaces, and render `OpenGeniChat` from `@opengeni/react` in the browser. The agent reaches your product's data through an MCP server or OpenAPI description, called as the signed-in user. A plugin for Claude Code, Codex, and Cursor can do the wiring for you.
Opengeni vs TrueForge: what is the difference?
Both are open-source, model-neutral runtimes with persistent sessions, MCP tools, sandboxes, approvals, and embeddable UI. TrueForge is MIT-licensed, documents Daytona as its sandbox provider, and has a lighter self-hosted footprint (SQLite locally, Postgres and Redis hosted). Opengeni is Apache-2.0, runs on a Postgres event log with Temporal orchestration, also offers Connected Machines, goals with success criteria, and a reviewable Knowledge library, and has a hosted cloud with published plans (Free, $20 Pro, and $100 Max), at the cost of a heavier stack to self-host.
How is Opengeni related to Cloudgeni?
Opengeni is built by the team behind Cloudgeni, an agentic CloudOps platform, and is published under Cloudgeni's GitHub organization. The README says Opengeni grew out of two years of running agents against production cloud infrastructure at Cloudgeni.
Is Opengeni ready for production use?
The README describes it as production-ready, but the project is young: the repository was created in April 2026, the public launch was October 5, 2026, and releases ship several times a day. Before exposing a self-hosted deployment, the docs ask for a deliberate access mode, gateway TLS and authentication, rate limits, and a reviewed sandbox credential policy, and some upgrades require stopping every old API and worker first. Pilot it on one real workflow before relying on it.

TrueFoundry
Platform and application teams that want a model-neutral, self-hosted runtime for reusable production agents
Free
DigitalOcean
Developers and small teams who already use Claude Code, Codex, OpenCode, OpenHands, Hermes, LangGraph, or CrewAI and want those agents running durably in the cloud, with pause, resume, and fork, governed tool access, and usage-based billing in one place
PaidOmnara
Product and platform teams that want hosted, long-running agents behind an API, in Slack, or on GitHub, with the freedom to pick any model, run tools on their own machines or third-party sandboxes, and self-host under Apache 2.0 or keep agent history in their own Postgres
Freemium
Trigger.dev
TypeScript teams putting AI agents and long-running background jobs into production who want retries, queues, human-approval waits, webhook triggers and tracing without running their own workers, and who may want to self-host later
FreemiumOpengeni describes itself as not the agent but everything the agent needs around it. You give it work from its web app, or your product calls the same session API through the TypeScript SDK, the React components (`OpenGeniChat`, `SessionConversation`), or plain HTTP, with your backend holding the API key and proxying the session routes. Every session event is stored in Postgres with a sequence number, so a reload, a second client, or an audit replays the same history, and a turn whose worker dies is retried as a new attempt rather than a repeated prompt. Sessions can be given a goal with success criteria and keep working across turns until they finish with evidence or pause with a reason. Tool calls can be set to Allow, Ask first, or Block per connected account, and agents can ask structured questions; both waits survive restarts and resume the exact turn. Each session runs in a managed sandbox (Docker, Modal, or cloud sandbox providers such as E2B and Daytona), with no compute at all, or on a Connected Machine: a laptop, build server, or GPU box you enroll that connects out and uses its own Git and SSH setup. Your product's data reaches the agent through an MCP server or an OpenAPI description, authorized as the signed-in user with short-lived tokens, and a credential provider endpoint can hand each run short-lived secrets that reach the sandbox but not the conversation or logs. A Knowledge library stores findings, sources, instructions, and Skills, with optional review before agent changes are published. Models are chosen per workspace and per session: OpenAI and Azure OpenAI are built in, and the docs also cover OpenRouter, Vercel AI Gateway, Opper, Anthropic API keys, ChatGPT/Codex, Claude, and SuperGrok subscriptions, and other OpenAI-compatible endpoints. Since launch the team-facing side has grown: a desktop app for macOS, Windows, and Linux (October 14, 2026) that can let agents use the computer you are on, @Opengeni mentions in Slack, a Microsoft Teams app, an Excel add-in that works in the open workbook, Published Sites with their own database, meeting and dictation recording, and connected password vaults such as 1Password and Bitwarden. The project grew out of two years of running agents against production cloud infrastructure at Cloudgeni, the team's agentic CloudOps platform. Self-hosting is free. The hosted, EU-hosted Opengeni Cloud moved to plans in early November 2026: Free with $10 of monthly trial credit for eligible accounts, Pro at $20 a month with $100 of monthly app credit, Max at $100 a month with $500, and pay-as-you-go top-ups, with no Opengeni fee currently added to your own API keys. The tradeoffs: self-hosting means operating Postgres with pgvector, Temporal, NATS, object storage, and a sandbox backend, usually on Kubernetes; the SDK is TypeScript-only; and the project only launched publicly on October 5, 2026, with very frequent releases and upgrade steps that sometimes require stopping every old API and worker first.
By early November 2026, Opengeni Cloud replaced its model-cost-plus-5% pricing with plans: Free with $10 of monthly trial credit for eligible accounts, Pro at $20 a month with $100 of monthly app credit, and Max at $100 a month with $500. Plan credit is for app use only and does not roll over, top-ups never expire, and connected AI subscriptions require Pro or above. Opengeni says it currently adds no platform fee to your own API keys.
Opengeni released a desktop app with sessions, chat, and inbox in a native window, notifications, and one click to let agents use the computer you are on. It installs through Homebrew on macOS, an install script for macOS and Linux (deb, rpm, or AppImage), or a Windows installer, and updates itself.
Opengeni launched publicly on October 5, 2026 with a Product Hunt launch, where it was listed third on that day's leaderboard. The launch post positions it as an open, Apache-2.0 alternative to the managed agent platforms from cloud providers and model labs, with self-hosting free and the hosted cloud priced at model cost plus 5%.
Are you the founder? Claim this listing →