Inference provided

Texas-first AI inference. American-operated.

FunkyRouter is building OpenAI-compatible access to Qwen3.8-27B on company-controlled Apple silicon in Texas. Join the private beta.

Join the Texas beta Preview the API

Planned private beta · Shared capacity · Final limits pending measurement

Your request in · model response out

Your appOpenAI SDK

FunkyRouterGateway target

Qwen3.8 27BApple silicon

Company controlledPlanned Texas fleet

Launch path in verification

01 — What you get

A direct route to useful local infrastructure.

One focused model, a familiar developer interface, and a beta sized around real Texas customers—not an anonymous compute marketplace.

Interface

Keep the OpenAI SDK

Change the base URL and model ID. Streaming and non-streaming Chat Completions are the first contract we are shipping.

Launch model

One stable route

Start with qwen/qwen3.8-27b, a conservative 32K service context, and limits measured on the exact deployed hardware.

Operator

A team you can reach

YEETUM LLC is developing FunkyRouter for a Texas private beta, with business-hours support planned for the first customers.

Capacity

Truthful beta limits

Shared capacity, explicit token and concurrency limits, early overload responses, and no high-availability promise from one node.

02 — Why Texas

Built close to the people it serves.

FunkyRouter starts with company-controlled Apple silicon and a direct Texas inference path. That keeps the first product small, inspectable, and accountable.

The marketing site can live globally at the edge. Customer inference will not be described as Texas-hosted until the public API gateway, broker, metadata store, backups, and model execution path are physically verified in Texas.

Texas first

Local hardware. American operation. Clear limits.

Home base: Fort Worth, Texas
Launch fleet: Company-controlled Macs
Availability: Paid beta, no HA SLA

03 — Data handling

Zero content retention is the launch target.

ZDR does not mean no records exist. The launch policy separates transient inference content from the metadata needed to meter, secure, and support the service.

Inference content

The launch policy is zero persistent retention for prompts and completions. Content is processed transiently to answer the request.

Usage metadata

Request IDs, model revision, token counts, timing, status, and billing records remain so the service can operate and reconcile usage.

Training

FunkyRouter does not plan to use customer prompts or completions to train, fine-tune, evaluate, or improve models.

Verification gate: These are launch controls under implementation. Public ZDR claims become final only after storage, log, trace, crash, and backup canary scans pass.

04 — Developer experience

OpenAI-compatible by design.

Keep the SDK and streaming loop you already use. The exact quickstart below is the contract FunkyRouter is testing before hosted beta access opens.

python · contract preview

from openai import OpenAI

client = OpenAI(
    base_url="https://api.funkyrouter.ai/v1",
    api_key="your-api-key",
)

response = client.chat.completions.create(
    model="qwen/qwen3.8-27b",
    messages=[{"role": "user", "content": "Hello!"}],
    stream=True,
)

for chunk in response:
    content = chunk.choices[0].delta.content
    if content:
        print(content, end="")

Streaming SSE in the OpenAI format

Model qwen/qwen3.8-27b

Status Local verification in progress

05 — Texas beta

Start with one customer, one model, and honest capacity.

The first commercial offer is designed for a Texas team that wants a reachable operator and predictable access—not a vague promise of unlimited infrastructure.

Planned launch offer

$499 / month

FunkyRouter Texas Beta

Qwen3.8-27B through an OpenAI-compatible API
Defined monthly token and concurrency limits
Shared capacity with early overload responses
Business-hours support planned from Texas
No high-availability SLA until a second node is proven

Request beta access

Final allowance, pricing, and availability follow measured capacity on the deployed artifact.

06 — Early access

Put your team on the first route.

Join the private beta list. We’ll send launch access and the first measured capacity update when the Texas path is ready.