Why Sennoric moved
Fresco started on a shared Hugging Face Space: easy to deploy, and good enough to get the model into people's hands quickly. But shared hosting has hard limits that started creating problems.
Hugging Face Spaces run on shared infrastructure. When demand spikes — because someone else's model goes viral or multiple apps share the same GPU allocation — Fresco's response times climb and requests get throttled. Hardware, scheduling, and networking are outside Sennoric's control.
For a lab building its own models, that's a ceiling with no workaround. Dedicated infrastructure was needed: dedicated GPUs, no noisy neighbors, and the ability to scale independently.
Faster responses. Fresco now runs on dedicated hardware with no contention from other workloads. Prompts that took around 220 seconds on the shared Space now complete in 2–3 seconds.
More reliable. No more intermittent slowdowns when HF infrastructure is under load. Sennoric owns the uptime end to end.
Same endpoint. The API hasn't changed. api.sennoric.com still serves the same OpenAI-compatible /v1/chat/completions endpoint. No SDK changes, no config changes.
The migration timeline
Moving off shared hosting while keeping the model available wasn't possible overnight. Here's how it unfolded.
This migration is step one. Dedicated servers give Sennoric the foundation to run more experiments, serve more users, and iterate faster on Fresco 1.3. With full control over the infrastructure, Sennoric can now benchmark under realistic conditions, test scaling strategies, and push the model harder without hitting shared limits.