Skip to content
FOR DEVELOPERS

Your product.
Our runtime.

Build the experience that makes you different. Opengeni handles the durable sessions, tools, and execution underneath.

Your applicationAPI · SDK · React

Durable state. Governed execution.

ModelsToolsCompute

A clear boundary.
A durable foundation.

Your product talks to the API. The runtime coordinates the work, and the durable record stays in infrastructure you operate.

One public surface.

Create sessions, send input, and stream events through the API. Use the TypeScript SDK or build directly on HTTP.

Work that continues.

Temporal coordinates session lifecycle and long-running work. Separate control and turn workers keep orchestration and execution distinct.

State you can own.

Postgres stores durable history. NATS distributes live events, while object storage retains files and sandbox archives.

From your laptop.
To your infrastructure.

The same open stack, with a deployment path that fits your environment.

The whole stack. One launcher.

Install Bun, start Docker, and configure your model credentials. The launcher installs dependencies, starts infrastructure, runs migrations, and brings up the API, workers, and web app.

Follow the local setup
LOCAL DEVELOPMENT
git clone https://github.com/Cloudgeni-ai/opengeni.git
cd opengeni
cp .env.example .env

# Configure model credentials in .env
bun run dev

Open the app at the URL printed by the launcher. Ports are selected per checkout.

Run where the
work belongs.

Choose managed sandbox execution or a Connected Machine you own. The compute target is an explicit part of the session.

Read it. Run it.
Make it better.

Apache 2.0, from the runtime to the deployment tooling. Inspect the source and contribute to the stack you depend on.

Contributing guide

Build something yours.

Get a feel for the runtime in the app. Then bring it into your own product.