Laya inside · Powered by Laya

The brain that answers before you blink.

One API key. Every model. Served from your own LXC container with a local dataset cache. 12 ms to first token, not 850.

layan.aibluprise.comblubeds.compostify.socialfillai.postify.social

lumina live demo loading…

Baseline demo loading…

standard harness AI, for comparison

Why lumina

Freedom from one model. Freedom from a slow box under a desk.

Most "AI infrastructure" quietly ties a company to two things at once: one model's weights, and whatever harness happens to be wired to them. Change the model and the harness breaks. Outgrow the harness and you are stuck with the model it was built around. lumina exists to cut both leashes at once — any model, on a harness fast enough that the choice of model stops being a compromise.

That is not a dockerized, stripped-down Hermes sitting in a jail cell. Both Hermes and the harness were rebuilt around a decision engine. Before a language model ever sees a request, and alongside it while it streams, Jev — or its Laya-compatible sibling — runs a typed decision: a real, scored choice among concrete options, answered in tens of milliseconds, not a paragraph of prose to be parsed and hoped for. The fast lane hedges providers instead of calling them one at a time, so whichever one answers first wins. Speculative intents read the assistant's own delta stream and start acting mid-response, before the sentence finishes. And policy sits outside the model entirely: a request the policy engine has not cleared never reaches the model, so nothing has to be talked out of a bad idea after the fact.

The consequence is what makes the container cheap to run. Because no model weights ever run locally — only the call to the language model leaves the box, out to the cloud — a company's lumina container does not need a VPS's worth of GPU and memory to exist. A micro VM is enough to hold Hermes, the harness and the decision engine; the model itself stays exactly where it already lived.

And the deal gets better the longer it runs: after 3 months of continuous subscription, every rate on the account drops 10 percent, automatically, for as long as the subscription continues.

Typed decisions before and alongside the model, not just after it
Policy outside the model — a request it hasn't cleared never reaches it
No model runs locally, so a micro VM is enough — no VPS required
3 months of continuous subscription → every rate drops 10%

Live from this workspace

lumina status.

Built last, on purpose. lumina is Layan's execution layer — the per-company container, the fast lane and this panel — and the blueprint builds it after identity, the policy engine and the shared gateway exist to give it something to enforce. Everything below is read from /api/health and, once you sign in, from your company's own runtime; nothing here is guessed.

Platform

lumina
checking…
Voice
checking…
Provider chain
checking…

Your company runtime

Live speed sandbox

Same prompt. Two brains.

Standard cloud model850 ms TTFT

        
lumina + Laya Harness · LXC12 ms TTFT

        

Request

POST https://api.lumina.ai/v1/complete
{ "model": "laya/core", "input": "Best check-in time for room 204?" }

Response · served from local cache

{ "answer": "15:00, early check-in free after 13:00",
  "ttft_ms": 12, "cache": "hit", "credits": 0 }

Illustrative benchmark: a scripted side-by-side, not a live measurement of this workspace.

Pricing

Free brain. Ten-dollar harness.

Free models stay free on every plan. Frontier models come with Jev.

layan.ai exclusive · 50% off

Harness at $20 → $10/mo for layan.ai users.

Enter your company website. If it's registered with layan.ai we integrate end to end and email you, usually within one hour.

We check the domain against layan.ai and confirm by email.

lumina Free

$0/mo
Laya badge on · free
  • Integrated Laya Engine (free Google tier)
  • All free models, API key + MCP endpoint
  • Rate-limited, no credit card
Jev Engine integrationFrontier models, monthly · +$4.20/mo
Start free

MCP subscription

$5/mo

Hosted MCP server for Claude, Cursor, Hermes and OpenClaw. Free models included, paid models from credits.

  • One URL, one bearer token
  • Credits from $10, never expire
  • Cancel any time
Subscribe

Technology blueprint

One container per company.

Each customer gets a jailed LXC/LXD system container on the VPS host: Hermes CLI, the Laya or Jev harness, and a local dataset cache. No heavy VMs, no shared state.

The moat is the coupling: system containers plus cached datasets is how 12 ms happens. Powered by Laya, Hermes and Jev, credited openly.

VPS host · Linux kernel
blubeds.com
LXC/LXD environment ├── Hermes CLI engine ├── Laya harness └── Local dataset cache
postify.social
LXC/LXD environment ├── Hermes CLI engine ├── Jev harness └── Local dataset cache

Example containers, for illustration — not a live list of running tenants.