Akira platform version 1.99.18 has been released (tagged at 1.99.18.20260811011001.eb61a0edf0). This is in a series of releases made from the 1.99 development branch.

Akira 1.99.18 includes substantial improvements to the web interface, object management workflows, real-time updates, performance, and reliability.

Object management and navigation

Object pages have been expanded with dedicated views for individual objects, including breadcrumbs, related-object information, reference links, and actions for adding, editing, cloning, deleting, and refreshing objects. Object references and many-to-many relationships can now be viewed and edited more naturally.

Object lists have been substantially improved. Lists now support server-side pagination, configurable rows per page, sorting, persistent URL state, row selection, and bulk deletion. Selection is retained while navigating through list pages, and table controls have been refined for smaller screens and empty result sets. Long table values are truncated where appropriate, and empty values are displayed more clearly.

Deleting an object from its detail view now returns to the corresponding object list. Delete operations also provide clearer feedback when an object cannot be removed because it is referenced elsewhere.

Dashboard improvements

The Dashboard now supports manual refresh and automatically refreshes object counts when data changes elsewhere in Akira. Refresh activity is indicated within the Refresh button without unnecessarily hiding or redrawing existing information.

Real-time updates

Akira now maintains a WebSocket connection between the browser and server for real-time application events.

Object lists and individual object views can subscribe to relevant changes and refresh themselves when those objects are modified. Dashboard counts likewise update when any object's collection changes. Subscriptions are restored automatically after a WebSocket reconnect.

Notifications are rate-limited and coalesced to prevent bursts of database activity from causing excessive browser refreshes.

Akira also uses the WebSocket connection to detect application-version changes and can notify users when the web application should be reloaded.

Forms and object data

Object comments now support Markdown formatting.

Schema-driven forms have gained support for non-editable fields, configurable field visibility, email and URL fields, improved Boolean controls, and more consistent monospace presentation for values such as slugs, DNS names, and UUIDs.

Select controls can handle larger result sets, and reference data can be reloaded while an edit dialog is open.

String and text fields now enforce configured maximum lengths, and several validation and error-reporting cases have been improved.

User interface improvements

The interface has received extensive visual and usability refinements, including:

• Improved responsive navigation and wide menus.
• Better dark-mode compatibility.
• More consistent page layouts, alerts, buttons, tables, and card spacing.
• Reduced visual flicker during Dashboard and object-view updates.
• Loading indicators integrated into Refresh controls.
• More stable action layouts while object data is loading.
• Improved login-page layout and messaging.
• Tooltips and clearer labels on a number of controls.
• Improved modal behavior when opening large selection lists.
• Better handling of overflowing table content.

Performance and efficiency

Object-list retrieval now uses server-side pagination, reducing the amount of data transferred and processed for large collections.

Database handling has been optimized for bulk deletions while retaining partial-success behavior: objects that can be deleted are removed even when other selected objects cannot be.

Persistent databases now use SQLite write-ahead logging with full synchronization, improving transaction performance while retaining strong durability guarantees.

DNS-name sorting now uses indexed sort keys to improve ordering performance for larger datasets.

Unused browser-side JavaScript has also been removed, reducing the size of the JavaScript delivered to the browser.

Realms and runtime configuration

Akira now supports realms, allowing object data and configuration to be separated into distinct administrative environments.

Runtime configuration handling has also been improved, including more reliable application configuration loading and protection against stale cached copies of the main application page.

Reliability and compatibility

This release contains numerous fixes for authentication errors, reference-cycle reporting, deletion errors, application reload behavior, table state, object loading, toast notifications, WebSocket protocol handling, and schema generation.

The generated backend schema is now compatible with C90 toolchains, and compatibility with Enterprise Linux 9-era Python environments has also been improved.

Dependency packages have been updated throughout the 1.99.18 development cycle.

Changes

• Added dedicated object views with breadcrumbs, related-object information, reference links, and Add, Edit, Clone, Delete, and Refresh actions. [RT2070, RT2071, RT2073, RT2077, RT2092, RT2094, RT2098, RT2107, RT2181, RT2204, RT2206, RT2207]
• Added server-side pagination, sorting, configurable page sizes, persistent list state, row selection, and bulk deletion to object lists. [RT2146, RT2147, RT2148, RT2149, RT2150, RT2151, RT2155, RT2156, RT2157, RT2158, RT2161, RT2162, RT2166, RT2172, RT2184, RT2186]
• Added Markdown rendering for object comments. [RT2179]
• Added editable many-to-many references and improved display and navigation of related objects. [RT2075, RT2076, RT2078, RT2113, RT2144]
• Added WebSocket-based real-time updates for object lists, individual objects, Dashboard counts, and application-version changes. [RT2116, RT2117, RT2121, RT2128, RT2191, RT2194, RT2196]
• Added automatic restoration of WebSocket subscriptions after reconnects and rate limiting of update notifications. [RT2195, RT2194]
• Added realms for separating administrative environments. [RT2086]
• Added email and URL schema fields, non-editable fields, field visibility controls, maximum string lengths, and improved Boolean, slug, DNS-name, and UUID presentation. [RT2049, RT2050, RT2052, RT2124, RT2125, RT2130, RT2133, RT2134, RT2154, RT2176, RT2197]
• Added Dashboard, object-list, and object-view Refresh controls with integrated progress indicators and reduced visual flicker during refresh operations. [RT2097, RT2198, RT2200, RT2202, RT2203, RT2204, RR2205, RT2207, RT2211]
• Improved responsive navigation, dark-mode styling, and numerous table, form, dialog, alert, login, and page-layout details. [RT2083, RT2085, RT2104, RT2105, RT2138, RT2140, RT2141, RT2164, RT2170, RT2174, RT2175, RT2178, RT2180, RT2188, RT2199, RT2212]
• Improved object-list performance with server-side pagination and indexed DNS-name sorting. [RT2184, RT2192]
• Improved database write performance with write-ahead logging and batched bulk-deletion transactions while preserving partial-success deletion behavior. [RT2208, RT2209]
• Improved error reporting for authentication, invalid references, reference cycles, deletion of referenced objects, and bulk-delete feedback. [RT2041, RT2044, RT2045, RT2163]
• Improved handling of application reloads, runtime configuration, and stale cached application pages. [RT2080, RT2081, RT2126, RT2127, RT2128, RT2142]
• Reduced browser JavaScript size by removing unused JavaScript. [RT2210]
• Added and expanded automated UI, API, persistence, WebSocket, schema, cloning, and compatibility testing. [RT2058, RT2060, RT2061, RT2063, RT2064, RT2132, RT2135, RT2136, RT2137, RT2139, RT2165, RT2169, RT2182, RT2213]
• Improved generated-schema portability and compatibility with C90 toolchains and Enterprise Linux 9-era Python environments. [RT2065, RT2167]
• Updated browser-side dependency packages during the development cycle. [RT2057, RT2108, RT2214]

Some more development releases will be made from this branch until Akira 2.0 is ready to be branched.

A demo instance of Akira can be viewed at: https://show.akira.org/

Login with username admin@example.com, password admin.