braess / router

Intelligence,
in motion.

Every request has somewhere to go.
Make the decision count.

Braess is a Rust semantic router.
Jev selects. Poise distributes.
Bounded, by design.

Explore the repository
Recorded outcomes / synthetic trafficBR / FLOW STUDY 001
RequestsUnstructured in
BRAESSJEV SELECTS
POISE DISTRIBUTES
GeneralEndpoint pool
CodingEndpoint pool
ReasoningEndpoint pool
Local fallbackUncertain decisions
Rejected locallyNo upstream dispatch

Requests move into Braess. Jev chooses general, coding or reasoning; Poise chooses an endpoint in that pool. Uncertain decisions return locally. Requests rejected at admission never reach Jev. Motion is illustrative; recorded counts appear below.

8.01s captured

Room to move. Accepted requests find their route; uncertain decisions return locally.

1,660 dispatched553 fallback552 rejected

Historical synthetic outcomes. Sampled particles; illustrative timing. Read the evidence

One model. Deliberate decisions.Independent open source / Single-server alpha

Choose with intelligence.
Dispatch with discipline.

A semantic decision is only the beginning.
What happens around it matters.

Jev selects.

A typed decision chooses a handler from your catalog. Uncertain decisions take the local fallback path.

Meet Jev

Poise distributes.

Within the chosen pool, least-loaded selection finds an endpoint. Admission stays bounded as demand grows.

Explore Poise

Braess holds the line.

Explicit limits. Durable reservations. No automatic upstream retries. A timeout never pretends the work is done.

Read the guarantees

Discovery in motion.
Follow the decisions.

A collection of documents.
A review workflow.
A router deciding where work goes.

In discovery, reviewers look for material that matters. Different documents can call for different review effort. This showcase follows four synthetic tasks through Braess: from a proposed route to the result that actually came back.

Recorded local execution. Scripted Jev and reviewer responses.
No private documents, paid inference or legal accuracy claim.

  1. Choose the review.

    See standard review, deeper review and local fallback in the route catalog.

  2. Follow the branch.

    Compare the proposed route with the outcome, including uncertainty and budget deferral.

  3. Inspect the record.

    Move through time, select a task and examine the events behind its result.

Watch the walkthrough.

74 seconds. Four tasks. Every outcome explained.

Synthetic discovery replay · Narrated with ElevenLabs George

Read the transcriptDownload video

Now follow a task yourself.

Explore the discovery replay

A beautiful flow.
A traceable story.

This visualization starts with a recorded local experiment: normal traffic, increased concurrency, then recovery. Every displayed count comes from the saved outcomes.

Synthetic Jev and handler fixtures. Historical implementation. These results describe this experiment—not live Jev latency or current production capacity.

Download the replay data
Recorded experiment29,767 requests
Historical synthetic request outcomes by load phase
PhaseConcurrencyRequests
Normal42,765
Pressure1624,236
Recovery42,766

Counts preserved. Motion interpreted.
Source hashes included in the download.

Give every request
a considered direction.

Build with Braess

Open source. Rust. MIT / Apache-2.0.