v0.9.0 · March 10, 2026
Dashboard API + audit log
Management endpoints for accounts, API keys, usage, sessions, domains, and audit records.
Product changelog
Product improvements, documented as they ship.
Follow meaningful changes to LiyaEngine's runtime, dashboard, management APIs, knowledge system, and operating controls.
Release streamChanges connected to the operating model
01 / BUILDDashboard
02 / RUNTIMEExecution
03 / CONTROLGovernance
04 / EVIDENCEObservability
POST /v1/rundomainintentinputSpecificEntries describe the product surface and behavior that changed.
OperationalImprovements are framed around how teams build and run capabilities.
TraceableVersions and dates make the evolution of the platform easier to follow.
Recent releases
The latest platform changes.
Release notes focus on material capabilities, operating changes, and fixes rather than every internal implementation detail.
v0.8.0 · February 24, 2026
Custom domains
Tenant-owned domains with custom intents, prompt behavior, output schemas, and knowledge links.
v0.7.2 · February 12, 2026
Quota and metering fixes
More reliable monthly resets, domain attribution, precision, and usage notifications.
v0.7.0 · February 3, 2026
Model configuration
Tenant-owned provider connections, routing preferences, limits, and model attribution.
v0.6.0 · January 20, 2026
RAG pipeline + knowledge
Managed retrieval, configurable ranking, semantic chunking, and domain-scoped grounding.
v0.4.0 · December 19, 2025
Sessions and retention
Persistent context, configurable data lifecycle, consent flags, and agent execution settings.
Release discipline
Changes should improve an owned production path.
LiyaEngine evolves around the same lifecycle customers use to build, ground, govern, observe, and ship capabilities.
01
Define
Clarify the product surface and customer behavior being changed.
02
Validate
Exercise contracts, migration paths, tenant boundaries, and failure states.
03
Document
Update the relevant guides and describe the externally meaningful change.
04
Observe
Use runtime and customer evidence to guide the next iteration.
Operating principles
Make the production boundary understandable.
Strong platform UX makes ownership, behavior, controls, and evidence visible to the people responsible for the capability.
01
Stable contracts
Runtime and management interfaces should evolve deliberately and preserve clear migration paths.
02
Tenant ownership
New features should reinforce customer-owned domains, configuration, knowledge, and credentials.
03
Operational clarity
Release notes should explain impact, not only announce that code changed.
Questions
Useful context before you build.
Where are breaking changes documented?+
Material contract or migration changes are called out in release notes and the relevant documentation.
Does every internal change appear here?+
No. The changelog focuses on customer-visible capabilities, behavior, fixes, and operating changes.
Where can I ask about a release?+
Use the documentation for implementation details or contact the LiyaEngine team for account-specific guidance.
Build on the current LiyaEngine operating model.
Use the documentation for implementation details and the changelog to track how the platform evolves.