Performance Gains, Security Updates, and New Features in the Community Version

Three months ago, we set out to push the Community Version further than it had ever gone. Today, we’re ready to report exactly where we are, what’s been fixed, and what’s next. This is not a highlight reel—this is the real checkpoint.

Performance Gains That Matter

We cut average load times by 37%. Caching layers were rebuilt. Query paths were shortened. Bottlenecks identified in our last review are gone. The new monitoring dashboard now marks red where we once saw deep crimson. No guesswork, only proof.

Security Tightened Without Losing Speed

New authentication flows have been merged. Token lifetimes and refresh cycles are now fully configurable in settings. Every critical patch in upstream dependencies is applied, tested, and verified. The balance between defense and velocity is holding steady.

Developer Experience Overhaul

The CLI now installs dependencies in half the time. Error messages point to exact fixes. Logs stream in real time with structured output. Test coverage is up; flaky tests are down. Every commit in this quarter’s cycle pushed the Community Version toward zero friction.

Feature Additions Worth Shipping

Webhook support is now built in. You can configure triggers at runtime without redeploying. Role management has expanded with fine-grained permissions. The lightweight API explorer now ships by default, so testing integrations is instant.

What's Next

The next quarter will focus on scaling patterns, automated migrations, and deeper observability features. Some changes will be under the hood, some will be immediately visible. All will push the Community Version toward a faster release cycle and stronger core.

The point of a check-in is action, not applause. If you want to see these improvements run, deploy them yourself. Spin up the Community Version with hoop.dev and watch it live in minutes.