Unverified

Local-first AI gateway

OmniRoute

Route coding agents and AI clients through one OpenAI-compatible endpoint.

OmniRoute is an MIT-licensed, local-first AI gateway with a dashboard, provider routing, fallbacks, usage analytics, protocol translation, and integrations for coding agents and other OpenAI-compatible clients.

AI gatewayCoding agentsLocal-firstSelf-hostedTypeScriptMIT
01

Screenshots

OmniRoute provider dashboard showing configured and available AI providers
OmniRoute analytics dashboard showing usage, token, cost, account, and provider metrics
02

How it works

  1. Step 1

    Install and start locally

    Install the package or run the documented container; the dashboard and API are served from the same local process.

  2. Step 2

    Connect providers

    Use the dashboard to connect the provider accounts or API keys that the user explicitly chooses.

  3. Step 3

    Point a client at one endpoint

    Configure a coding tool or other client to use the local OpenAI-compatible endpoint and an OmniRoute endpoint key.

  4. Step 4

    Route and observe requests

    Use routing and fallback strategies, then inspect request, quota, usage, and cost information in the dashboard.

03

Capabilities and scenarios

  • OpenAI-compatible local endpoint
  • Provider routing and automatic fallback
  • Dashboard for providers, endpoints, quotas, and analytics
  • Protocol translation and coding-agent integrations
  • Optional prompt and context compression

Good starting points

Scenario 1

Share one local gateway across coding tools

Scenario 2

Route between subscription, paid API, and free provider tiers

Scenario 3

Self-host an AI gateway with usage visibility

Scenario 4

Test provider fallback and model-selection policies

04

Fit and limitations

Fit at a glance

Project type
Local-first AI gateway
Repository set
1 repository
Runtime status
Unverified

Known limitations

  • Collected from public repository documentation; runtime behavior was not executed for this publication.
  • Provider availability, pricing, quotas, and terms can change independently of OmniRoute.
  • Some providers require user-supplied credentials or account authorization.
  • Compression, proxy, and fallback behavior must be tested against the target client and data policy.

Confirm before starting

  • Node.js >=22.22.2 <23 or >=24 <27 for the captured source, or a supported Docker runtime.
  • A local port, documented as 20128 by default, and permission to run a local service.
  • User-approved provider accounts, credentials, budgets, and data-handling rules.
  • Never publish provider keys, endpoint keys, request contents, or local usage data.
05

Repository set

These repositories form the complete project workflow. Follow setup order and include optional services only when the confirmed goal needs them.

Setup 1Required

diegosouzapw/OmniRoute

Primary gateway runtime, dashboard, CLI, provider adapters, and documentation

Default branch
release/v3.8.50
Captured revision
package 3.8.50; commit ed2db6cb19ba534980c5b3e046501e8a5c40c458
Author / maintainer
Diego Souza and OmniRoute contributors
License
MIT
The latest GitHub release observed was v3.8.48; the default branch and package metadata were already at 3.8.50.

Catalog updated 2026-07-29. Reconfirm licenses, revisions, environment requirements, and runtime behavior from each repository before starting.

Project lineage

Project relationships

Every extension should preserve a clear path back to its sources.

01

Upstream projects

Where this project started

No upstream projects yet

02

Peer projects

Projects with the same upstream

No peer projects yet

03

Downstream projects

Published work derived from this project

No downstream projects yet