Product · Release History

What's new in OVRIX.

Every significant release, hotfix, and improvement — documented in chronological order. Subscribe to the release feed to get notified the moment something ships.

Semantic versioning RSS available
May 2026 · v4.6.0
Cinematic landing page & design refresh

Rebuilt the marketing site with Three.js WebGL backdrop, GSAP scroll animations, Lenis smooth scrolling, and the new Gem-Glass design language. Fraunces editorial serif replaces Inter across all display headings.

Feature Design
April 2026 · v4.5.0
BullMQ event-driven architecture

Decoupled billing updates, KPI aggregation, and notification dispatching into isolated BullMQ queues. Eliminated blocking synchronous chains in the subscription renewal flow. Queue health now visible in the SuperAdmin dashboard.

Feature Architecture
April 2026 · v4.4.0
Stripe billing integration

Full Stripe integration for subscription management. Webhook handler validates signatures, updates tenant status, and fires BullMQ events for downstream consumers. Supports monthly, yearly, 2-year, and 3-year cycles.

Feature Billing
April 2026 · v4.3.2
Sidebar autohide + tenant email notifications

Dashboard sidebar now supports autohide mode with hover-reveal. Tenant admins receive email notifications on successful subscription renewal via the new notification queue.

Fix Feature
April 2026 · v4.3.0
Employee KPI glassmorphism redesign

HR KPI dashboard summary cards migrated to the Gem-Glass design system. Consistent branding with the Employees module, including responsive card layouts and gradient accents.

Design Feature
April 2026 · v4.2.0
Dashboard navigation overhaul

Rebuilt sidebar navigation with role-aware rendering, collapsed states, active section detection, and mobile overlay mode. Fixed 403 Forbidden regression on route guard evaluation order.

Fix Feature
March 2026 · v4.0.0
Schema-per-tenant PostgreSQL isolation

Core architectural milestone. Every tenant now receives a dedicated tenant_<slug> Postgres schema, completely eliminating any possibility of cross-tenant data leakage at the database level.

Feature Architecture Breaking