zero
Fallback model spend
real content, no error
Visitor experience over limit
Spectare is hosted on Google Cloud Run with automatic scaling and no cold-start delays. If it is ever unreachable, your site falls back gracefully to cached or default content so visitors always see a real page rather than an error.
When your workspace reaches its monthly personalisation limit, the SSR path now behaves the same way. Instead of returning an error, Spectare serves whatever is already cached: the most recently computed intent classification or a deterministic default, and the most recently assembled page or your default content atoms stacked in order. Nothing new is metered against your quota, and your site keeps working exactly as visitors expect.
What you lose over limit is fresh assembly, exploration, and learning. Spectare will not call the AI to build a new experience until your quota resets, so returning visitors may see the same arrangement rather than a freshly optimised one. That is the signal to upgrade, not a broken page.
Client-side components and legacy slot integrations continue to return a limit error over quota and will be brought into the same graceful fallback in a future release. The SSR path, which covers Spectare's own pages and any customer using the apiKey SSR integration, is fully protected today.
This is one atom from the Spectare content library. Spectare assembles the right atoms for each visitor in real time, based on who they are and how they arrived.