Borz
Borz
borz.ai
By the Agents · Through the Agents · For the Agents

Run agents like infrastructure.

Uptime, approvals, recovery and a full audit trail. Not a chat window.

Clan Control is the fleet manager for Borz agents and actors — it dispatches work, watches every tool call, enforces policy, and keeps the fleet running unattended, so you are not the babysitter between every call. Built on Borz: agents are pure-LLM personas, actors are deterministic and compiled — typed, auditable building blocks from the ground up.

agent — pure LLM persona Claude · ollama · gemma4
agent AnomalyNarrator:
    model:  local:ollama:gemma4:12b
    memory: rolling(turns: 5)

    system: """
        Financial anomaly analyst.
        Two-sentence narrative + action:
        block | hold | approve.
    """

    tools:   [ MerchantDB.Lookup ]
    accepts: [ NarrateAnomaly ]
    emits:   [ AnomalyReport ]
actor — deterministic, 4 targets DENSE · DEMIX · native · Ephernity
actor RiskActor:
    @persistent var flagged: i64 = 0

    on msg ScoredTransaction:
        if msg.risk_score > 0.85:
            flagged = flagged + 1
            # typed send → the agent above
            send AnomalyNarrator <- NarrateAnomaly(
                tx_id:      msg.tx_id
                merchant:   msg.merchant
                risk_score: msg.risk_score
            )
20+
agents unattended, daily
our own fleet, on Clan Control
Twice
autonomous recovery
proven in production, unattended
Two building blocks

One language. Two kinds.

agent and actor are distinct first-class constructs in the same .borz source file. The compiler checks both sides of every handoff between them.

agent
pure LLM agent
Claude · ollama · gemma4

A first-class Borz construct defining a pure LLM persona: persona prose, a mandated model and host, a declared toolset, memory, and a typed message interface. The whole agent is inference — it does not call an LLM, it runs as one.

  • Model-portable: pin to claude:opus, local:ollama:gemma4:12b, or any compliant host
  • Typed interface: declares which message types it handles; compiler rejects wrong-shape callers
  • Memory: rolling-window or persistent conversation — declared in source, managed by Clan Control
  • Tools: declared capabilities the Clan enforces as policy caps at dispatch time
Never DENSE

Agents have no handler bodies and no state variables. The compiled artifact is a validated JSON manifest. DENSE constraints do not apply.

actor
deterministic compiled code
DENSE · DEMIX · native · Ephernity

Isolated compiled Borz code with typed messages, sequential handlers, and persistent state. The compiler enforces isolation — no shared variables, no global state. May call infer for one typed LLM step (agentic actor) — still an actor, still deterministic core.

  • Write once: same source compiles to all four targets — change the flag, not the program
  • @persistent state: survives restarts and hot-reloads; DENSE snapshot on each dispatch
  • DENSE target: flat ELF, ~50 µs p50 dispatch (single no-op handler benchmark), 2 MiB cap, Ed25519 receipt per call
  • Ephernity target: deterministic smart contract on the Epher Compute Chain
Agentic actor ≠ agent

An actor that calls infer is an agentic actor. Its control logic is still Borz source code. It is not a pure LLM agent.

One typed message bus

Agents and actors communicate over the same typed message system. An actor sends a typed message to an agent — the agent processes it as an LLM call and sends a typed reply back. The compiler checks both sides of every contract at build time.

RiskActor (DENSE) → NarrateAnomaly → AnomalyNarrator (gemma4) → AnomalyReport → AuditActor (DENSE)
Try Borz
Click Run to execute

This is a Borz actor. The same source compiles to native, DEMIX, DENSE, or Ephernity without changes. Try the full playground →

Actor compile targets

Write once. Run four ways.

The same actor source compiles to a standalone binary, a supervised microservice, a sub-millisecond nanoservice on bare KVM, or a smart contract on the Epher Compute Chain — without changing the program.

The runtime underneath
DELIGHT — Decent Edge Lightweight Application Server

The platform Borz programs run on in production, with two execution lanes: DEMIX for full microservice VMs and DENSE for bare-metal nanoservices. The compiler emits artefacts DELIGHT knows how to schedule, supervise, and hot-reload.

--target native

Native binary

Single static binary · zero runtime dependencies

  • Compiles to one self-contained Go binary today; MLIR/LLVM lowering planned
  • Built-in CLI and HTTP server — no external runtime needed
  • State auto-persisted as JSON; infer calls any LLM provider
  • Ideal for local tools, CI workers, and serverless functions
--target demix

Microservice — DEMIX

Full Linux VM · supervised lifecycle · hardware isolation

  • DEMIX is Decent Edge's microservice VMM — each actor runs in its own Linux micro-VM
  • Millisecond cold starts; full network stack; hardware-isolated; supervised restart on failure
  • Rolling hot-reload via `borz deploy` without dropping connections
  • Choose when you need a full runtime, POSIX APIs, or unbounded in-memory state
--target dense

Nanoservice — DENSE

No OS · no runtime · KVM directly · sub-millisecond

  • DENSE is Decent Edge's nanoservice layer — each handler is a flat binary on bare KVM
  • ~50 µs p50 dispatch (single no-op handler benchmark); 16 KB binary size; 2 MiB memory cap enforced at compile time
  • Comparable to Microsoft Hyperlight — with a high-level actor language on top
  • Distributed state replication built in; primary/follower failover with zero downtime
--target ephernity
roadmap

Smart contract — Ephernity

Deterministic actor on Epher Compute Chain · attested · auditable

  • Actors with @deterministic and @canonical decorators compile to Epher Compute Chain contracts
  • Every execution is attested via HATP (Hardware Attestation Trust Protocol) signing — tamper-evident, append-only audit trail
  • Actor state is an immutable append-only ledger — write logic once, the chain enforces invariants
  • BLAKE3 + Falcon-1024 signing; spans T0 (seconds) to T7 (eternal) timed-ledger tiers
Applications

What you can build

native + HTMX

Real-time dashboard

System metrics from N actors, auto-refreshing via HTMX

@http@persistentMap[str,i64]f-strings
native + wasm

Full-stack notes app

Server-side actors + WASM client, one language for both

@http@dom@persistentList[str]
DENSE cluster

Distributed counter

@replicated(factor=3) counter across nodes

@replicated@persistent@http
DENSE cluster

Sharded tenant cache

@partition(key=tenant) Map-of-Maps cache

@partition@shardMap[str,str]
Open the showcase →
Clan Control

Command it from one place.

Clan Control is the fleet manager for Borz agents and actors. It dispatches work, watches activity, enforces policy, and keeps the fleet running unattended — so you are not the babysitter between every call.

We run 20+ agents on it ourselves. Credit runs short? Clan Control automatically falls back to local gemma4 via ollama — the fleet keeps moving without interruption.

Live activity view

Every agent and actor in the fleet — dispatch count, last call, model in use, stall state. Refreshes in real time.

Model-aware dispatch

Dispatch targets the correct model host per agent. Schedule, retry, and route without touching code.

Local-gemma fallback

When cloud credit runs low, Clan Control re-routes eligible agents to a local ollama instance automatically.

Copy onto another model

Clone an agent and re-provision it on a different model — conversation history and tool grants included.

Per-tool policy caps

Grant tools per agent at dispatch time. The Clan enforces every tool call against the declared grant — no scope creep.

DORA-grade audit

Every dispatch produces a signed audit entry. Stalls are detected and surfaced. Nothing runs without a receipt.

Clan Control →
Mesh Manager — roadmap

Federate many Clans.

Mesh Manager will route typed messages across multiple Clans in arbitrary N:M combinations — one fleet view across every node. On the design roadmap; planned to ship after Clan Control matures. Read the vision →

The Decent Edge family

Borz is the language. DELIGHT is the runtime.

Borz programs deploy onto DELIGHT — Decent Edge's Lightweight Application Server. DELIGHT is the umbrella runtime. Underneath it sit two execution lanes: DEMIX for microservice VMs running full Linux guests, and DENSE for bare-metal KVM nanoservices. Borz is the surface language that targets both.

Umbrella runtime · the application server

DELIGHT — Decent Edge Lightweight Application Server

KVM-isolated nanoservice / microservice / VM platform. DELIGHT is what Borz programs actually run on in production. Two execution lanes underneath: DEMIX for full microservice VMs, DENSE for bare-metal nanoservices. Comparable in ambition to Microsoft Hyperlight, designed for agent-scale fan-out and millisecond cold starts.

Hosts
DEMIX · DENSE
DELIGHT microservice lane

DEMIX

A lightweight VMM that boots full Linux guests with millisecond cold starts. Use DEMIX when you need a real runtime, full networking, and state that doesn't fit in a fixed buffer. Each guest is a hardware-isolated micro-VM with a shared-memory ring buffer to the host.

borz compile app.borz --target demix
DELIGHT nanoservice lane

DENSE

Bare-metal KVM nanoservices: no OS, no runtime, no GC. One handler per 2 MiB micro-VM. Sub-100 µs warm dispatch (single no-op handler), < 2 MB memory per actor, single-threaded by design. The lane where Borz wins on latency.

borz compile app.borz --target dense --backend cpp
Native pipeline · roadmap

Borz IR → MLIR → LLVM

The native target today emits Go source; the planned evolution lowers Borz IR through MLIR dialects to LLVM, unlocking aggressive inlining and link-time optimisation.

Surface language

Borz

The language that authors write — humans and agents alike. Borz is the front door to DELIGHT: agents, actors, messages, traits, decorators. Closed source; hosted compile API, or signed offline CLI under license.

Flagship project · written in Borz

Ephernity — a timed-ledger protocol

Ephernity is Borz's first flagship project: an open, two-pillar protocol — an attested append-only ledger spanning ephemeral (T0) to eternal (T7), and a deterministic contract dialect that reads and writes it. The hot path runs on DENSE, per-tenant isolation runs on DEMIX, the coordinator runs native — one Borz program, three targets. Token-free, EU-sovereign, hardware-attested.

Where Borz sits

The actor model is older than the web. What's new is the audience.

Borz competes with Erlang/OTP and Akka on the language side, and with Microsoft Hyperlight and Firecracker on the nanoservice runtime side. We are the only stack that targets both layers from the same Borz program — with a grammar designed for the autonomous agents that will write most of the code.

Dimension Borz Erlang / OTP Akka MS Hyperlight
Surface size ≈30 keywords; one obvious form per construct Functional + processes; ~50 keywords + OTP idioms JVM library; 100+ APIs; Scala-flavoured C/Rust SDK; system-level only
Agent (LLM) friendliness Primary design constraint; /llms.txt + structured docs Sparse training data; tail recursion idioms Verbose, multi-paradigm Low-level; no high-level surface
Cold-start latency ~50 µs (nanoservice, single no-op handler benchmark) ms-scale process spawn ms-scale actor creation on JVM sub-ms (compiled microVM)
Deploy footprint kBs per handler (nanoservice) MBs per node (BEAM VM) tens of MBs (JVM + libs) kBs per workload
Embedded LLM step First-class `infer:` statement External calls only External calls only Out of scope
Backend targets per program Native · Microservice (DEMIX) · Nanoservice (DENSE) · Smart contract (Ephernity) BEAM only (NIFs for natives) JVM only Hosts; not a language

Where Borz fits

Agent fleets
Thousands of supervised pure-LLM agents and deterministic actors — Clan Control dispatches agents to model hosts; actors run in isolated nanoservices. No shared state.
Edge AI services
Latency-critical inference fronts, sub-100 µs routing decisions, classifier sidecars. Nanoservice micro-VMs run them directly on the hypervisor.
Replicated control planes
Booking systems, ledgers, queues — supervised, restart-on-failure, snapshot-replicated. The microservice cluster is where they live.
AI-assisted devops
Coding assistants emit, edit, and deploy Borz programs from natural-language intents. The grammar is small enough to fit the LLM context window.
Smart-contract logic
Actors with @deterministic compile to Ephernity smart contracts — same source, append-only ledger, HATP-attested execution on the Epher Compute Chain.
Formal-verification workloads
Explicit semantics, no hidden state, machine-readable IR. Future TLA+ export for safety-critical actors.
Examples

Real programs, real short.

Each tab compiles to all targets without changes. examples/ contains the full corpus and forms the test suite.

counter.borz The hello-world of actors: state + handler.
msg Increment:
    by: i64

actor Counter:
    @persistent var count: i64 = 0

    on msg Increment:
        count = count + msg.by
        response(count)
Getting started

60 seconds from intent to artefact.

Borz is a closed-source product of Decent Edge. There is no public source repository, no toolchain to install. The first-touch path is the remote compilation API: submit your Borz program, receive an artefact in seconds. The same API powers the in-browser playground.

1

Try the playground (no signup)

# Open in your browser:
https://play.borz.ai

# Or hit the public anonymous endpoint:
curl -F target=native \
     -F source=@hello.borz \
     https://api.borz.ai/v1/compile
2

Write a Borz program

msg Hello:
    name: str

actor Greeter:
    on msg Hello:
        response(reply="hi, " + msg.name)
3

Request an API key for production

# Sign up at decentedge.com/borz
# You receive a per-tenant key.
export BORZ_API_KEY=de_live_…
4

Compile to your target backend

curl -H "Authorization: Bearer $BORZ_API_KEY" \
     -F target=dense \
     -F source=@hello.borz \
     -o hello.tar.gz \
     https://api.borz.ai/v1/compile

# The tarball ships ELF nanobinaries
# ready to deploy on a DEMIX or DENSE host.
Enterprise option

For air-gapped or latency-sensitive workflows we ship an offline CLI as a signed, hardware-bound binary under a Decent Edge commercial license. The CLI compiles locally without phoning home. Contact decentedge.com to request access.

How to get Borz

Three flavours. Pick the one that fits.

Online for trying it out. Community for developers + small teams. Enterprise for sealed data centres. Upgrade later if you outgrow your tier.

Online API

For trying it out

Sign up with an email. Get an API key in 5 seconds. POST your .borz source, download the compiled binary.

  • ✓ No install
  • ✓ 100 compiles/day free
  • ✓ Early access — pay-as-you-go pricing on request after that
  • ⚠ Every compile is visible to us
Try the API →
Community Offline

For developers + small teams

Run the compiler on your own laptop or build server. Same compiler, no network round-trip, no per-compile fee.

  • ✓ Free, 1 machine per account, 1-year cert
  • ✓ Hardware-locked to your machine
  • ⚠ Requires KYC: name, org, country, use case
  • ⚠ Telemetry on: compile counts + source corpus
Apply for Community access →
Enterprise Offline

For production, regulated, air-gapped

Bring Borz inside your data centre, on your sealed images, on your customer hardware. Source code never leaves your perimeter.

  • ✓ Telemetry contractually disablable
  • ✓ Air-gapped delivery option
  • ✓ Custom seat counts + TPM allowlist
  • ✓ NDA + DPA + signed order form
Contact enterprise →

Why three tiers? Read the rationale. KYC is real: we're a small EU startup and we want to know who's using our compiler for what.

Manifesto

A language belongs to the people who use it. Soon, most of them will be agents.

The vast majority of code written in the next decade will be generated by, edited by, and read by autonomous agents and coding assistants. The languages and tools we ship today need to be designed with that audience in mind — not as an afterthought, not as a retrofit.

Borz takes that seriously. The surface syntax is small and orthogonal. State is local. Side effects are explicit. Compilation is deterministic. Examples ship as the test corpus, so every program in this site provably runs.

The motto sits on every generated file: By the Agents · Through the Agents · For the Agents. It is not a slogan — it is the design constraint.

Borz is built and maintained by Decent Edge as a commercial product. The language surface is openly documented for humans and agents to learn from; the compiler itself is offered as a hosted service and, on request, as a signed offline binary under a commercial license.

A Decent Edge project · license: TBD