laya-server
Self-hosted Docker service and web console that serves Laya's multilingual model on Jev's /v1/systemone format behind API keys.
Overview
LAYA SERVER, from the 1Panel team, packages upstream Laya's System One inference as a standalone, self-hosted service with a web interface, compatible with TypeSafe's Jev API format. You run one Docker container with an admin username and password, sign in to the console, and create API keys that are shown once. Applications then call POST /v1/systemone with a bearer key and receive answers, the model name and actual token usage.
The published image includes the multilingual model, selectable with model set to auto or multilingual. A readiness endpoint checks model files and data persists in a volume. Usage statistics are written asynchronously in batches to SQLite without delaying responses; the README describes them as best-effort, eventually consistent telemetry rather than a billing or quota ledger. Documentation is available in English and Chinese. It suits teams that want a managed-feeling local decision API with key management.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Does the customer ask for a refund? | — |
| Choice | Any choice question via the Jev-format API | — |
How it works
- docker run the image with admin credentials
- Sign in and create an API key
- Call /v1/systemone with the key
- View usage statistics in the console
Strengths
- One-container deployment
- API key management and console
- Jev-compatible request format
Caveats
- Statistics are not a billing ledger
- Only the multilingual model is in the published image
- HTTPS must be set up via a reverse proxy
Getting started
docker run -d --name laya-server -p 8080:8080 -v laya-data:/data -e LAYA_ADMIN_USERNAME=admin -e LAYA_ADMIN_PASSWORD=... 1panel/laya-server:latestAt a glance
- Type
- Service
- Status
- beta
- Language
- Python
- Runtime
- Docker service with web console
- Has code
- yes
Use cases and integrations
How curated lists describe it
A self-hosted API and web interface for Laya.
wh000wh000/awesome-jev-liveA self-hosted API and web interface for Laya’s structured decision models, compatible with the TypeSafe Jev API format.
hellogumbo/awesome-jevSelf-hosted API and web interface for Laya's checkpoints, speaking `/v1/systemone` behind its own API keys.
MrJev/awesome-jev
Frequently asked questions
Is it compatible with Jev clients?
Yes, it accepts the Jev /v1/systemone format with bearer keys.
Which model is included?
The multilingual Laya model.
Can I bill users from its statistics?
The README says statistics are best-effort telemetry, not a billing ledger.
Related projects
Docker service exposing local Laya, Von, a CLM head or hosted Jev through one TypeSafe-compatible HTTP and MCP endpoint.
MCP serverbetaPythonConverts open Jev reproductions (Laya, Kev, NanoJev, PlayJev) to INT8 ONNX for offline CPU decisions at about 15.6 ms per question.
ServicebetaPythonNative Go runtime serving Gemma 4 12B as a Jev-like decision model with hand-tuned PTX kernels and no CGo or CUDA toolkit.
ProjectbetaGoGo harness for System One models: hosted Jev, open Kev in-process via llama.cpp, and Cloudflare Clef, with typed helpers and a CLI.
ServicebetaGoGo gateway exposing the Jev /v1/systemone contract over ordinary LLM backends by reading single-token label logprobs.
ServicebetaGoRuns Intern-Decision-0.8B on Apple Silicon behind a local /v1/systemone endpoint that accepts screenshots for agent decisions.
ServicebetaPython