Organization repository on GitHub
A self-hosted API and web interface for Laya’s structured decision models, compatible with the TypeSafe Jev API format.
- Forks
- 57
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Demos & Experiments
Laya Server — 1Panel-dev
Self-hosted Docker service and web UI that packages Laya structured-decision inference behind a compatible System One endpoint.
- Stars
- 98
- Language
- Python
- License
- APACHE-2.0
- Published by
- Community
- Author
- 1Panel-dev
- Last verified
- Oct 2026
About this project
LAYA SERVER is a self-hosted API and web interface for Laya's structured decision models, compatible with the TypeSafe Jev API format. It packages the System One inference capabilities of upstream Laya as a standalone service, making them easier to deploy and use in your applications. Once the image is published, install Docker and run the following command. Replace latest with a version tag to pin a release.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- Deploys with one docker run and a data volume, then sign in, create an API key, and check model files on the readiness endpoint.
- Answers POST /v1/systemone with answers, model, and token usage, defaulting to automatic model selection with a multilingual option.
- Includes a playground and in-console docs with request examples, plus reverse-proxy guidance for domain and HTTPS setups.
- Ships the multilingual model in the published image under an Apache license, with issues tracked on the project repository.
Watch out
Replace the sample admin password, keep the one-time full API key safe, point at your own server address, and terminate HTTPS on a reverse proxy. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
Upstream Laya is the inference capability; this wraps it as a deployable server with Docker, admin login, API keys, a playground, readiness checks, and console docs for app use.
Port 8080, mapped 8080:8080 with a laya-data volume and LAYA_ADMIN_USERNAME and LAYA_ADMIN_PASSWORD on the docker run line; replace the sample password before signing in at your server address. Create the key on the API Keys page, where the full key is shown only once, check model files on /health/ready, then POST state plus questions to /v1/systemone. For a domain, terminate HTTPS on a reverse proxy.
Start with the automatic default, which the docs use for general calls, and switch to the multilingual model explicitly when your inputs need it; responses report the model and token counts.
Do not expose it as-is: put a reverse proxy with HTTPS in front, forward to the app port, and use the documented control, origin, and storage settings for public deployments.
No, and the README says so: they are best-effort, eventually consistent telemetry, not a billing or quota ledger. A background thread per process writes batches of up to 100 events and coalesces last_used_at by API key, flushing after up to a second when idle. Each process buffers up to 1,000 queued events, a full queue drops new statistics with rate-limited warnings, and failed batches are not retried because an uncertain commit could double-count usage.
No. The README states that neither a dropped statistics batch nor a SQLite failure turns successful inference into an HTTP 503; failures roll back where possible, log and drop the batch, then reconnect. API-key authentication and revocation still use the database synchronously. Graceful shutdown drains the queue for up to five seconds, so a forced kill can lose unflushed statistics, which is why /data should sit on low-latency persistent storage.
Apache License 2.0. Releases are tagged on GitHub and the Docker image is published under 1panel/laya-server, so replace latest with a version tag to pin a release rather than tracking the moving default. Issues and suggestions go to the project repository's GitHub Issues.
Other listings of this project
Forks and copies of this project in the directory. This entry is the canonical one.
2GitHub stars
A minimal local server exposing POST /v1/systemone, documented in three commands: uv sync to install dependencies, uvicorn main:app --reload to run it, and a curl payload in the System One request shape.
Jev Tools & CLIs#community#awesomejev#catalog-import
Community
pjt3591oo/laya-serverPython
pjt3591oo/laya-serverPythonMore Jev resources like this
23GitHub stars
Browser drone-fleet lab where TypeSafe Jev steers each drone as fast reflexes and an optional planner offers one-use strategy advice when confidence drops, without pausing control.
Jev Demos & Experiments#community#jevbest#catalog-import
23GitHub stars
Chrome extension that sends each X post to Jev with six typed questions in one call near the viewport, then renders a behavior chip under the post plus a session cost and latency panel.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
oso95/x-scannerTypeScript
oso95/x-scannerTypeScript14GitHub stars
Manifest V3 Chrome extension in TypeScript that sends each LinkedIn post to Jev and collapses bait, self-promo, off-topic, and sponsored posts into a one-line bar with reasons and scores.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
stefw/lkcleanTypeScript
stefw/lkcleanTypeScript7GitHub stars
Demo that turns free-text UI descriptions into real shadcn components using only Jev typed Choice, Noul, and Score answers, with no generated code on the decision path.
Jev Demos & Experiments#community#jevbest#catalog-import
8GitHub stars
Claude-driven browser automation where plain-English chat drives Brave or Chrome, Jev makes on-page decisions, and a guard freezes irreversible clicks.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
ranjan2829/AskJevTypeScript
ranjan2829/AskJevTypeScript42GitHub stars
Server-authoritative browser FPS where one queued player fights a Jev-driven opponent to five kills, with spectators, killcam replay, and heuristic fallback when the API is down.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
emrickgarrett/OneVOneJevTypeScript
emrickgarrett/OneVOneJevTypeScriptFrom the Jev guides
Original write-ups on what this entry is for.
A game tick is a state plus a legal action list. How Clash Royale, Minecraft, and the earlier Mario, Pokémon, StarCraft, and drone loops ask Jev one step at a time.
Jev Demos & Experiments#gaming#agents#control
Read article
From the Jev community
Posts from builders shipping with Jev right now.