Reliability on Arivu

Processing Failures Have a Recovery Path

Wed, 15 Jul 2026 00:00:00 +0000

A background failure should not leave a self-hoster choosing between guessing, editing the database, and pretending the work never happened.

Arivu Administration now makes processing failures visible and recoverable. The API Usage view lists durable failed jobs and failed summaries with the context needed to decide what to do next: the owner, affected bookmark, attempts, timestamps, provider and model context where relevant, safe error information, and recorded failure details.

Failures Stay Attached to the Work

Failed jobs and failed summaries are shown separately because they answer different operational questions. A background job may have exhausted all of its attempts. A summary may have failed evidence or validation checks without exhausting the surrounding job.

Safer Self-Hosting, Less Guesswork

Wed, 08 Jul 2026 00:00:00 +0000

Context, 2026-07-13: Upgrades are additive-safe, preserve executable permissions under restrictive defaults, and provide useful activation diagnostics when a replacement cannot start. Existing data and configuration remain in place.

Update, July 11, 2026: The installer no longer requires GitHub CLI. Piped bootstrap keeps interactive prompts TTY-safe, DNS mismatches produce actionable warnings, and newer Ubuntu releases are tolerated rather than rejected only for being newer. Upgrades now verify and transactionally activate the matching app and installer binaries, roll both back if activation fails, and prompt browsers to revalidate embedded frontend assets. Tagged releases report the exact release version; development builds may report development metadata. Public HTTPS can still require correct DNS, firewall, or shared-proxy configuration.

Quieter Admin, Stronger Guarantees

Thu, 02 Jul 2026 00:00:00 +0000

Before we ship a wave of new features, we wanted the operating layer underneath them to be solid. This update rebuilds the admin experience on the app’s own storage, makes provider configuration a runtime concern instead of a restart concern, and adds a clear audit trail for sensitive actions.

None of this changes what Arivu looks like day to day. It changes how confidently you can run it.

A Native Admin Dashboard

The admin dashboard now runs entirely on the app’s own SQLite storage. Admins listed in ADMIN_EMAILS get an /admin area with sections for overview, API usage, users, system status, recent activity, collections, and an audit log.

Deep Modularization, Reliability Engineering, and Admin Tools

Sun, 08 Feb 2026 00:00:00 +0000

Our earlier hardening pass laid the groundwork - security, speed, and an initial split into smaller modules. This update goes deeper. We’ve broken the backend into fully independent domains, added retry and conflict handling for reliability, built a testing infrastructure that catches problems before you see them, and shipped an admin dashboard for controlled early access.

Full Domain Separation

The initial hardening split out a few core services. This time, we went further - every major feature area now lives in its own domain with clear boundaries. Authentication has its own dedicated layer, including lockout and email handling. Bookmarks, collections, analytics, import/export, knowledge graph, search, and AI processing are all independent.