make, and an API key for one AI provider (for example OpenAI).
Start the stack
| Service | URL | What it serves |
|---|---|---|
| Gateway | http://localhost:8180 | The OpenAI-compatible /v1 API |
| Workspace | http://localhost:8190/ui/ | The console and the admin API |
| Deployer | http://localhost:8200 | Model deployments and training jobs |
localhost:5532 and Redis on localhost:6479.Create your organization
Open http://localhost:8190/ui/ and choose Sign up. Enter an organization name, your email and a password (at least 8 characters). The organization is active immediately and you are its owner.
Connect a provider
In the console, open Providers, add a provider account (for example type
openai), paste its API key, and enable the models you want to serve, such as gpt-4o-mini.Console providers serve /v1/chat/completions, /v1/responses and /v1/messages. For embeddings, images, audio or rerank, or for Azure, Bedrock and Vertex, declare the model in gateway.yaml instead. See Providers.Create a personal access token
Open API Keys and create a personal access token for your workspace. Copy the
ml_pat_... value; it is shown only once.Explore the console
Back at http://localhost:8190/ui/ you can:
- Open the request you just made in Request Traces
- Create teams, API keys and virtual accounts
- Configure routing, rate limits, budgets and guardrails
- Use chat, knowledge bases and agents in the workspace
For the full stack with the optional backends (Kafka, Qdrant, MinIO, dstack), run
make up instead of make dev-up. make down stops everything.Next steps
AI Gateway quick start
Connect providers via the admin API or
gateway.yaml, and issue API keys.Connect a real provider
Point the gateway at any of the 20 supported provider types.
Gateway configuration
Walk through every section of the gateway YAML config.
Self-host the gateway
Run ManyLayers in production.