Jazzmine logoOpen-source chat infrastructure

The Jazzmine ecosystem

Production agent infrastructure built around one constraint: consume the minimum resources needed. Fewer tokens, less energy, smaller hardware, full capability.

Why we built this

Most agent frameworks treat tokens as unlimited and hardware as cheap. We don't.

Flow-based routing, structured memory, and tight token management let smaller models punch above their weight on hardware you already own. Token usage, energy consumption, and hardware requirements are first-class design constraints, not afterthoughts.

Efficiency

Reduced token consumption

Less sent, same outcome. Lower cost on every request.

Low energy footprint

Smaller compute footprint across your entire fleet.

Minimal hardware requirements

No dedicated AI hardware. Runs on what you already have.

Fast on low-grade hardware

Conversational latency even when the machine is cheap.

Capability

Full reasoning on smaller models

Lighter LLMs, same agent capability. No tradeoff.

Natural process modeling

Flows that mirror real workflows, not prompt engineering.

Fast, accurate memory recall

Structured retrieval that finds the right context quickly.

Built-in logging and telemetry

Every decision, tool call, and session is traceable by default.

Start here: Plug & Play

A single self-contained Python file with tools, flows, sandbox setup, and an interactive chat loop. Clone it and run.

  • Real tool execution inside sandboxed environments.
  • Flow-based routing with conversational explanations.
  • Works with Mistral, OpenAI, or any compatible provider.
quickstart.sh
export MISTRAL_API_KEY="your-key"
export MISTRAL_BASE_URL="https://api.mistral.ai"
export MISTRAL_MODEL="mistral-medium-latest"

python quickstart_market_full.py

How the ecosystem fits together

The SDK is the only bridge between React and Python. Transport, session state, and event routing live entirely in the SDK — neither side knows about the other.

Jazzmine ecosystem communication diagramReact UI calls the SDK which bridges over HTTP/WebSocket to jazzmine core. Core uses jazzmine-security and jazzmine-logging.FrontendTransportBackend@jazzmine-ui/reactChat UI componentsUser / browser@jazzmine-ui/sdkSession · events · transportHTTP · WSjazzmineFlows · memory · toolsusesjazzmine-securityjazzmine-loggingin-processnetwork boundary

Frontend layer

@jazzmine-ui/react renders the interface and calls the SDK exclusively.

SDK transport

@jazzmine-ui/sdk owns the session, WebSocket lifecycle, and typed message contracts.

Backend layer

Core handles flows and memory. Security gates every request. Logging records every decision.

@jazzmine-ui/react

TypeScript / React

UI component library for chat interfaces

@jazzmine-ui/sdk

JavaScript / TypeScript

Core SDK for connecting to the Jazzmine backend

jazzmine

Python

Backend engine with sessions, routing, and AI integration

jazzmine-logging

Python

Structured logging runtime for backend services

jazzmine-security

Python

Authentication, token validation, and rate limiting

security
View docs ->

Production readiness checklist

Recurring concerns from Core, Security, Logging, and Plug and Play docs.

Sandbox rules and host allowlists are defined before enabling tools.

Flow routing is explicit so tool invocation behavior is predictable.

Structured logging and security moderation are part of baseline setup.

Frontend and backend contracts are tested through SDK or HTTP mode.

Open source · Apache 2.0 License

Ready to build?