Cross-instance consistency
Everything in v2 still holds. Our backend runs across multiple instances for availability — this round of work made sure that scaling out doesn't come at the cost of correctness for the things that matter: who you are, whether your key is still valid, and how much you've used.
Sign-up is rate-limited per real visitor, not per proxy hop
Account creation is rate-limited by the originating client's IP address, correctly resolved through our load balancer rather than collapsed to one shared address — so the limit actually distinguishes between different visitors, consistently, no matter which backend instance handles the request.
Key rotation takes effect platform-wide, in seconds
OpticsOps' backend runs across several instances for availability. When you rotate your API key, that change now propagates to every instance within seconds — not just the one that handled your rotation request — so an old key stops working everywhere, quickly.
Usage limits hold at the boundary, not just on average
Daily usage allowances are checked consistently across every backend instance, with extra verification specifically as a project approaches its limit — the moment it matters most for keeping the platform fair for everyone sharing it.
The rest of the honest limitations — no compliance certification, single ClickHouse VM, no SSO or RBAC — haven't changed this round. See v2 for the full list. This page will get a v4 the next time something material does.