Lightport – a maintained fork of Portkey AI gateway

Uh oh!

There was an error while loading. Please reload this page.

Notifications You must be signed in to change notification settings

Fork 0

Star 12

BranchesTags

Open more actions menu

Folders and files

NameName

Last commit message

Last commit date

Latest commit

History

9 Commits

9 Commits

.github/workflows

.github/workflows

src

src

.dockerignore

.dockerignore

.env.example

.env.example

.gitignore

.gitignore

.oxfmtrc.json

.oxfmtrc.json

.oxlintrc.json

.oxlintrc.json

CLAUDE.md

CLAUDE.md

CONTRIBUTING.md

CONTRIBUTING.md

Dockerfile

Dockerfile

LICENSE

LICENSE

README.md

README.md

knip.config.ts

knip.config.ts

package.json

package.json

pnpm-lock.yaml

pnpm-lock.yaml

tsconfig.json

tsconfig.json

tsdown.config.ts

tsdown.config.ts

vitest.config.ts

vitest.config.ts

Repository files navigation

A lightweight AI gateway that makes LLM providers OpenAI-compatible.

Goal

Lightport does one thing: it accepts OpenAI-compatible requests, transforms them for the target provider, and returns the response. That's it.

Retries, secret management, caching, rate limiting, and other operational concerns are explicitly non-goals. Those are better handled either at a service layer above Lightport or as custom middleware.

Supported endpoints:

POST /v1/chat/completions

POST /v1/completions

POST /v1/responses (+ GET, DELETE, input_items)

Supported providers: OpenAI, Anthropic, Azure OpenAI, Google Gemini, Vertex AI, Bedrock, Cohere, Mistral, Groq, Deepseek, Together AI, Fireworks, Ollama, and more (77 total).

Background

Lightport started as a fork of Portkey AI Gateway. Our sole use case for the gateway has always been making AI providers OpenAI-compatible – we only needed the request/response transformation layer.

Since then, Portkey has evolved into a full-featured AI gateway with guardrails, fallbacks, automatic retries, load balancing, request timeouts, smart caching, usage analytics, cost management, and more. We believe those capabilities belong at a higher abstraction level – which is what Glama provides – rather than in the gateway itself.

Since forking, we have fixed numerous bugs, added integration tests for every provider, and continue to actively maintain the gateway as it directly powers Glama.

If you need a lightweight proxy that makes LLM providers OpenAI-compatible, Lightport is for you. If you need an enterprise gateway with all the bells and whistles, consider Portkey Gateway.

Quickstart

pnpx lightport

The gateway runs on http://localhost:8787.

From source

pnpm install pnpm dev

Make a request

curl http://localhost:8787/v1/chat/completions \ -H "Content-Type: application/json" \ -H "x-lightport-provider: openai" \ -H "Authorization: Bearer sk-YOUR-KEY" \ -d '{ "model": "gpt-4o-mini", "messages": [{"role": "user", "content": "Hello!"}] }'

Set the provider via x-lightport-provider header and pass credentials via Authorization (or provider-specific headers like x-api-key for Anthropic).

Provider-specific headers

Some providers require additional headers:

Provider Headers

Azure OpenAI x-lightport-azure-resource-name, x-lightport-azure-deployment-id, x-lightport-azure-api-version

Bedrock x-lightport-aws-access-key-id, x-lightport-aws-secret-access-key, x-lightport-aws-region

Vertex AI x-lightport-vertex-project-id, x-lightport-vertex-region

Custom host x-lightport-custom-host

HTTP proxy

Route provider requests through an HTTP proxy by setting the x-lightport-proxy-url header:

curl http://localhost:8787/v1/chat/completions \ -H "Content-Type: application/json" \ -H "x-lightport-provider: openai" \ -H "x-lightport-proxy-url: http://user:[email protected]:8080" \ -H "Authorization: Bearer sk-YOUR-KEY" \ -d '{ "model": "gpt-4o-mini", "messages": [{"role": "user", "content": "Hello!"}] }'

Scripts

pnpm dev # Development server with hot reload pnpm build # Production build pnpm start:node # Start production server pnpm test # Run tests pnpm lint # Lint code pnpm format # Format and auto-fix pnpm knip # Find unused code/dependencies

Testing with provider credentials

Copy .env.example to .env and fill in API keys for the providers you want to test. Tests automatically load .env and skip providers without credentials.

cp .env.example .env

fill in your keys

pnpm test

Architecture

Request -> bodyParser middleware (parse JSON/FormData) -> requestValidator (require provider header) -> handler (chatCompletions / completions / modelResponses) -> constructConfigFromRequestHeaders() -> tryPost() -> adapter transform (if needed for responses/messages API) -> provider lookup + transformToProviderRequest() -> fetch to provider -> responseHandler() (transform response back) -> Response

The provider system (src/providers/) contains 77 provider implementations. Each defines:

API config (base URL, endpoints, headers)

Request parameter transforms

Response transforms (streaming + non-streaming)

About

A lightweight AI gateway that makes LLM providers OpenAI-compatible.

lightport.dev

Topics

ai

gateway

Resources

Readme

License

View license

Contributing

Contributing

Uh oh!

There was an error while loading. Please reload this page.

Activity

Custom properties

Stars

12 stars

Watchers

1 watching

Forks

0 forks

Report repository

Releases 8

v2.3.3

Latest

Jul 17, 2026

+ 7 releases

Contributors

Uh oh!

There was an error while loading. Please reload this page.

Languages

TypeScript 99.7%

Other 0.3%