Open source · self-hosted

AISplinter

Middleware between your app and LLM providers. Provision scoped keys, enforce budgets, proxy chat — your users never touch OpenRouter.

What it is

Neutral AI infrastructure

AISplinter is open-source middleware that sits between your application and LLM providers. It provisions scoped upstream keys, enforces budgets, proxies requests, and emits webhooks — so your users get AI under your brand without creating provider accounts.

Features

Built for builders

Budget Enforcement

Reserve → Stream → Reconcile ledger flow prevents budget overshoot on every request.

Scoped Keys

Each user gets their own upstream key with fine-grained rate and spend limits.

Provider Neutral

Switch between OpenRouter (cloud) and LiteLLM (on-prem) without touching client code.

Embeddable

Mount inside Next.js, Express, or any host via createAisplinterApp().

Setup Wizard

First-time database connection walks through provider, key, and app linking.

Stateless Sessions

Short-lived JWTs keep the server stateless — no session store needed.

Screenshots

See it in action

Dashboard, setup wizard, and admin views. Replace these placeholders with real captures when ready.

Setup Wizard
Database → Provider → Key → Verify
Onboarding wizard — first-run project setup
Admin Panel
Users · Keys · Upstream Status · Ledger
Admin panel at /admin — manage users and budgets
Chat Proxy
Scoped key → Reserve → Stream → Reconcile
Transparent chat completion proxy with budget tracking

Architecture

How it works

Step 01

Reserve

Before streaming a response, AISplinter reserves estimated tokens against the user's budget.

Step 02

Stream

The request is proxied to OpenRouter or LiteLLM with the user's scoped upstream key.

Step 03

Reconcile

Actual usage is recorded in the ledger. Leftover reserve is released; overages are charged.

Ready to self-host?

One deployment per codebase. Postgres + Node.js + your provider key. Up and running in minutes.