AISBF Logo AISBF

AI Service Broker Framework — AI Should Be Free

AISBF · built in public · open source
Privacy and self-host landing page

Self-Host, Route Locally, and Keep Control of Your AI Traffic

AISBF is built for operators who do not want their whole AI stack trapped behind one vendor or one hosted black box. Use it to route requests across local and cloud providers, keep sensitive workloads closer to home, and choose deployment patterns that fit your own privacy boundaries.

View Source Code Try the Hosted Demo

AISBF is currently a demo-stage service maintained by one human with limited resources. Subscribing to the €6/month or €60/year testing plan helps fund continued development and infrastructure.

Why privacy-conscious teams care about AISBF

Self-host the control plane

Run AISBF in your own environment instead of surrendering the routing layer to someone else’s defaults.

Mix local and cloud models

Keep some traffic on Ollama or other local backends while still bursting into cloud providers when it actually makes sense.

Reduce vendor lock-in

Put one operational layer in front of multiple providers so your architecture is not welded to a single API contract forever.

Use privacy-aware exposure patterns

Support local-first operation and TOR-friendly exposure models when your deployment requirements call for them.

CoderAI for local/private model work

Keep sensitive workloads on your hardware

Run prompts, media generation, speech, image and video work on a local CoderAI box while AISBF stays the routing and policy layer.

No public inbound port required

With broker mode, CoderAI can connect outward to AISBF over WSS, which is useful for home GPUs, workstations, labs and private networks.

Hybrid routing

Use AISBF policy to send private jobs to CoderAI and less-sensitive or overflow jobs to cloud providers.

See the CoderAI local worker path →

The operating model

What AISBF lets you do

  • route requests between local and remote providers
  • keep sensitive or cheap workloads closer to your own infrastructure
  • centralize quotas, failover, and routing logic
  • choose a hosted path or a self-hosted path per your needs

Why that matters

  • more control over data paths
  • more architectural freedom
  • less dependence on one provider’s business or policy decisions
  • a cleaner way to evolve your AI stack over time

Hosted if you want speed, self-hosted if you want maximum control

AISBF does not force a false choice. You can use the hosted service to evaluate it quickly, then self-host when you want tighter ownership over the whole stack.

If you want to explore the product without deploying first, the testing-period hosted offer is still a strong bridge:

Unlimited Pro for €6/month or €60/year during testing — a support-priced plan that helps fund continued one-human development and infrastructure.

Support the €6 / €60 Pro test plan Developer landing page

Best fit for

Privacy-conscious operators

You care where requests go and want deployment options that respect that.

Teams mixing local and remote AI

You want one operational layer over hybrid workloads instead of ad hoc glue.

OSS-first adopters

You want the freedom to audit, self-host, and migrate without being trapped.

Use AISBF when privacy and control are product requirements, not afterthoughts

If you want local-first flexibility, self-hostability, and less vendor lock-in, AISBF is built for that reality.

View Source Code Back to AISBF homepage

Also available on TOR: aisbfity4ud6nsht53tsh2iauaur2e4dah2gplcprnikyjpkg72vfjad.onion