
Selected work / Full-Stack Developer & System Architect
LLM-HubProMax
The core challenge was normalizing providers with different model catalogs, capabilities, rate limits, error behavior, and endpoint coverage behind one predictable OpenAI-style interface. The gateway uses a provider catalog, capability metadata, explicit routing headers, sticky…
- Role
- Full-Stack Developer & System Architect
- Client
- Ali Saad (Self-initiated product)
- Year
- 2026
Three decisions shaped the final experience.
03Unified OpenAI-Compatible /v1 API
One proxy surface covers model listing, streaming and non-streaming chat, tool calling, embeddings, image generation and edits, speech, transcription, translation, and realtime…
Sticky Fallback Routing
Configurable chains keep requests on the selected route when healthy, apply cooldowns after rate limits or provider errors, and expose routed-provider and fallback-attempt metadata in…
Provider Health & Model Discovery
Health checks, model availability discovery, capability tracking, provider ranking, and model sweeps show which routes are configured and currently usable across the provider catalog.