Skip to content

LLMIngress v0.1.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

@IamNotShady IamNotShady released this 18 Jul 15:13
· 300 commits to main since this release
2e6e294

First public beta of LLMIngress — a self-hosted LLM gateway and console.

Highlights

  • Gateway: OpenAI Chat Completions / Responses and Anthropic Messages protocols with streaming, safe fallback chains, and request logging
  • Virtual Model routing: atomic Virtual Models with fixed, cost-first, and load-balance ordering plus fallback chains
  • Provider management: API key and OAuth credentials (encrypted at rest with ENCRYPTION_KEY), model catalog sync, exact connection health probes; model lists refresh automatically once credentials are ready
  • API Key access control: API keys, Virtual Model grants, and budget / rate / token / concurrency limits
  • Usage & activity: tokens, latency, failures, fallbacks, and actual or estimated cost
  • Console: eight pages — Overview, API Keys, Virtual Models, Providers, Activity, Usage, Limits, Playground
  • Worker: durable model_refresh, provider_connection_probe, and price_sync jobs with a self-healing poll loop and timeout-bounded network calls

Deployment

Two-container Docker Compose delivery (one app container + PostgreSQL 18.4):

git clone https://github.com/IamNotShady/LLMIngress.git
cd LLMIngress
git checkout v0.1.0-beta.1
./scripts/deploy.sh

deploy.sh generates a random ENCRYPTION_KEY into .env when missing, then starts Compose. The Console listens on http://127.0.0.1:3000 and the Gateway on http://127.0.0.1:4000; all ports bind to loopback only by default.

⚠️ Back up the ENCRYPTION_KEY in .env — stored provider credentials can only be decrypted with the same key.

Known limitations (beta)

  • PostgreSQL uses the Compose-bundled password and its port is published to 127.0.0.1 only; adjust the Compose file if you need external access
  • /v1/embeddings is not supported in this release

Note: this tag was re-cut on 2026-07-18 and now points at a newer commit than it did on 2026-07-16. If you cloned or fetched v0.1.0-beta.1 before that date, git will not update the tag on a plain git fetch — run git fetch --tags --force to pick up the current code. The rebuilt beta renames the Agent entity to API Key, renames MASTER_KEY to ENCRYPTION_KEY, and renames the random route policy to load_balance.