ByMorning
An open source, self-hosted MCP and model gateway.
Documentation · Install · Connect agents · Download · Changelog
ByMorning gives your team's agents access to company systems, and caps what they spend.
- Company systems as Tools. People and agents reach your internal systems through Plugins and MCP servers, each
person under their own permissions.
- Spend limits. A limit per Workspace, member, or Service Account, applied to every model call.
- Models and routing. OpenAI-, Anthropic-, and Google-compatible endpoints, with routing across the providers you
enable.
- Your cloud. It runs in your own cloud account or Kubernetes cluster.
Status. ByMorning is open source under the MIT License and community maintained: fork it, open pull
requests, and run your own builds. Read SECURITY.md before reporting a vulnerability.
Install
Every release image is signed keylessly by this repository's release workflow and published to
ghcr.io/bymorning/bymorning, with signed evidence (SBOMs, scans, provenance) on the
GitHub release. Choose where to run it:
| Where | Use |
|---|
| One machine, to try it | Docker Compose evaluation. Not for production. |
| AWS or AWS GovCloud (US) | Terraform module, also on the Terraform Registry as bymorning/bymorning/aws. |
| Azure (AKS) | Azure installer: Terraform and Kubernetes manifests, with a digest-pinned image. |
| Any Kubernetes cluster | Helm chart, with your own database, object storage, and key. |
Connect coding agents
- Models. Point Claude Code, Codex, Cursor, VS Code Copilot, OpenCode, or Gemini CLI at your installation's
OpenAI-, Anthropic-, and Google-compatible endpoints with a Service Account key. Spend limits, routing, and usage
apply to every call. See Connect coding agents.
- Tools. Add
https://<your host>/mcp to the agent as a remote MCP server. The agent signs in with OAuth as a
Workspace member and gets the Tools that member may use, under the Workspace's permissions. See
Use ByMorning's Tools from an agent. server.json
describes it for the MCP Registry as io.github.bymorning/bymorning.
Develop
You need Bun 1.3 and Node 22+. From the repository root:
bun install --frozen-lockfile
bun run dev
Open http://localhost:3000; local sign-in goes straight to the workspace. Local development needs no cloud
credentials, SST, or external login provider. Docker is not required for the database; it is only needed for the Code
Interpreter and the application tests.
- The development host keeps Postgres-compatible data with PGlite under
.bymorning/local/pglite.
bun run dev runs the API watcher (port 3210) and Vite (port 3000) together, and the API runs migrations at startup.- Choose ports with
PORT=4001 WEB_PORT=4000 bun run dev: PORT is the API, and WEB_PORT is Vite and the default
login callback origin.
bun run local is the bundled, one-origin development host instead.- Build the execution image with
bun run --cwd app/host setup when you need the Code Interpreter.
Build the host bundle
One host program, app/host, serves every deployment. Its production build is what the root Dockerfile ships:
bun run --cwd app/host build
node app/host/dist/bymorning.mjs
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
