are you for real with this critique? out of a proxy/router packed full of functionalities that is also open source and self-hostable what you are looking at is the html of the demo service website that, by the way, has been written by gpt-5.5 ( so yes, an frontier llm did it )
You know when they say "when i point the moon you are looking at the finger"?
The output of the model is human responsibility, this isn't the model's webpage design, it's yours (it also show that proper UI/UX guidelines have not been given in the instructions). And this is important because you offer a commercial service.
In this era, people don't blindly trust "open-source", so the frontpage/identity does matter, a lot.
still, you are commenting about a web page of a demo of an open source project instead to look at the project, you lame :)
and you are confusing a demo with a "commercial project". Look at the moon, not at the finger. Have a good life and if and when you will have any relevant comment or real critique, i will listen to you. PLONK.
AISBF is now in BETA. It provides a single API endpoint that can route requests to OpenAI, Anthropic, Google, Ollama, and many other providers, with features like request splitting, semantic response caching, adaptive rate limiting, provider‑native caching, and OAuth2 integrations (Claude, Kilo, Codex, Qwen).
fix a LOT of bug
full support without installing the cli and complete with Oauth2 initialization:
claude subscriptions with oauth2 or api token
codex cli subscription with oauth2 or api token
qwen-code cli subscription with oauth2 or api token
kilo is supported both with oauth2 or token
kiro-cli full support
any anthropic, gemini, openai, ollama compatible endpoints
AIsbf ( AI Should Be Frtee ) is a API proxy/router with intelligent ai driven router which exposes an openai compatible api to the clients making available to them in a unified interface different protocols and AI endpoint/services, offering various optimization aiming to make the costs of using LLMs more accessible to everyone.
It is multiuser, and can run from small setup or scale to big infrastructure.
In this last release:
- support for cache on redis, sqlite, mysql, file
- more context condensation method
- native prompt caching and request caching support
- faster and better semantic prompt based routing for autoselections
- full support for Claude.ai subscribers with OAUTH2
- full support for Amazon Kiro-cli subscribers with OAUTH2
- full support for OpenAI codex subscribers OAUTH2
- full support for Kilo.ai subscribers using token or OAUTH2
- many bugfixes and new minor features
AISBF - a personal AI proxy! Tired of API limits? Free accounts eating your tokens? OpenClaw needs snacks? This Python proxy handles OpenAI, Anthropic, Gemini, Ollama, and compatible endpoints with smart load balancing, rate limiting, and context-aware model selection with context condensation. Install with pip install aisbf - check it out at https://pypi.org/project/aisbf/
The name "devuan" has been selected cause it's a merge of "debian" and "VUA" where "VUA" stand for "Veteran Unix Admins", the name of the group that started the fork.
The first release has been named "jessie" cause it's a 1:1 replacement of debian jessie, and for our luck jessie is also a name of a minor planet, so, it match our nomenclature and reflect that is a very close path to switch from debian jessie, as Devuan consider itself the "real" continuation of debian after wheezy.
Wayland have some advantages but also some disadvantages, and it isn't yet really mature.
Also, wayland, on the sandbox side, doesn't do anything special. As it's just a lot simple than X and does pretty anything except copy a buffer on the screen, it just delegate all IPC and rendering to the compositor, then, in the wayland world, the security issues of X11 are moved on the compositor instead to stay on the X server, but the issue are the same and the compositor must consider them.
( anyway, for sure fix those issues in a compositor is easier and consume less resources than on X11, and then the wayland world is better from this point of view. But i don't think it's yet enough mature, and many WM/DE doesn't yet support it or support it only partially )
I know it is very immature (basically unusable in most cases), but my understanding was that it would be easier to fix these issues moving forward because of the design decisions taken in Wayland. You response seems like a tentative affirmation of that, which is encouraging to me (for whenever I can actually used it).
You know when they say "when i point the moon you are looking at the finger"?