AISBF
AI Service Broker Framework — AI Should Be Free
AISBFAI Service Broker Framework — AI Should Be Free
AISBF is not just a developer integration layer. It is also the operational control plane for teams that need quotas, analytics, multi-user governance, and routing rules across a messy AI provider stack.
If your problem is no longer "how do we call a model?" but "how do we run this sanely across users, budgets, and environments?" this is the AISBF page for you.
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.
Set practical controls for TPM, TPH, TPD, user-level limits, and provider-level guardrails before usage becomes chaos.
Track consumption, usage patterns, model choice, and cost pressure across users, projects, and providers.
Support teams, customers, or internal departments with clearer separation, activity visibility, and per-user operational controls.
Decide which users, workloads, or environments are allowed to hit which models and providers instead of letting every caller improvise.
Attach workstation, home-lab, RunPod or cloud GPU CoderAI instances as AISBF providers instead of handing every team raw machine access.
Provider status can show owner, client ID, transport, last seen, advertised Studio endpoints and worker metadata.
Route CoderAI capacity through AISBF users, quotas, rotations and failover policies so local GPU power is part of the same operational model.
Keep one noisy user, app, or workflow from eating the whole budget or degrading service for everyone else.
Send some traffic to cheaper models, some to higher-quality models, and some to local/private infrastructure on purpose.
Separate experimentation, internal tooling, customer workloads, and sensitive traffic with saner operational boundaries.
Balance cost, speed, and resilience with routing and fallback logic that does not depend on every app team reinventing it.
You are building one AI layer for multiple teams and want governance before the blast radius gets bigger.
You need per-client visibility and boundaries instead of a pile of raw provider keys.
You already proved the AI feature matters and now you need production controls, not more heroic glue code.
You want governance over not just spend, but also where model traffic is allowed to go.
AISBF can be the hosted operational layer you adopt quickly, or the self-hosted control plane you run yourself when policy, infra, or privacy demands it.
And during the testing period, the hosted path is intentionally cheap for early adopters:
Unlimited Pro for €6/month or €60/year during testing — a support-priced plan that helps fund continued one-human development and infrastructure.
The pitch for teams is simple: centralize control, reduce provider sprawl, and make AI operations less chaotic.