What's New

A running summary of how Aelo has evolved. We ship frequently; this page highlights the customer-visible changes — new capabilities, meaningful improvements, and the occasional important fix. For a full role-by-role guide to everything the platform does today, see the User Guide.

Dates reflect when each change reached production. Internal-only work (infrastructure, tests, refactors) is omitted.

August 2026

What the analysis knows, and what it only guessed · 2.28

An analysis that fails its automatic check now says so. The report e-mail carries a note, and the delivery webhook a verification block with the status and the reasons. CRM automation was already held back in that case; now the other channels tell you the same thing instead of delivering the report as if nothing happened.
The data retention window is editable by the organization owner. 1 to 365 days, with a preview of how many records a shorter window would remove and an explicit confirmation before it does.
A phone number that arrives in a contact’s name is masked like a phone number. CRMs create a contact from an inbound call with the number itself in the name field; those now show the last three digits in e-mail and personal webhooks, as everywhere else.
A disconnected CRM can be reconnected, and you are warned first. If your organization has two sources connected, both stay visible after a disconnection and each comes back on its own button. The warning that the portal tile goes dark now appears in the confirmation dialog, before the disconnection rather than after it.
A chat that failed before it was analyzed can be re-analyzed. The button now replays from the recording itself rather than expecting an analysis that was never saved.
Voice metrics say “not enough data” instead of showing zeros. When pitch or pause detection degrades on a recording, the card and the PDF report both say so, rather than presenting the zeroed values as a measurement.

Three languages instead of one, chats on equal footing with calls, and every analysis double-checked · 2.27

Report language and recognition language are now two separate settings — and both default to Auto. The report is written in the language of the conversation, and the recognizer detects the spoken language on each recording, so a project no longer inherits a language from the screen you happened to be using. Set a fixed report language per project from the Analysis Setup hub when you need one; pick the recognition language from 90+ supported languages with search. Quotes from the conversation are never translated.
Chats are analyzed on the same footing as calls. A chat used to land in the catch-all category with no scores and no alerts. It is now categorized into the same ten categories as a call — from the whole conversation, not the first few messages — and scored with chat-appropriate criteria, so analysis profiles, script rules, scores and alerts apply to chats too.
Your own list of forbidden words. Each project can name the words an agent must not say; every hit shows who said it, in what form, with the quote — and there is an alert rule for it. The metric formerly labelled “Stop words” is now called Agent uncertainty, which is what it always measured: hedging about price, deadlines and promises.
Every analysis is independently checked before it reaches you. Statements about safety, agreements and CRM fields must be backed by the transcript; anything that cannot be is withheld and the record is marked for review, and CRM automation acts only on a verified analysis. Organizations that want a human in the loop can ask us to enable the Review Queue (beta), where withheld actions are approved or rejected. Re-analysis no longer overwrites the previous version, so history is kept.
Metrics stopped grading what they cannot measure. CRM completeness stays silent when there is no CRM to compare against; qualification no longer expects a private buyer to name a budget and a decision-maker; a promising sale is no longer an “attention” reason next to threats and data leaks; and voice metrics — pitch variability, speaking ratio, pauses — are real measurements again, kept on re-analysis. A zero result is shown as zero, not hidden.
Free plan: 100 analyzed minutes a month instead of 30 — for every free organization at once, no action needed.
Data retention is yours to set — from 1 to 365 days. Shorten the window and Aelo shows how many records that would remove before it changes anything.
Notification settings in one place. Rules, recipients and channels are now one section, in the order they apply, with a summary of what you actually receive today; digests can be switched off for the whole organization. Save works the same way on every settings screen — bottom left — and leaving with unsaved edits asks first, including when you switch organization.
Privacy in alerts. Telegram alerts — team channels and personal ones alike — no longer include the other party’s name, number or quotes: only the rule, the severity, the category and a link to Aelo. Where a contact is still shown, in the app, in e-mail and in webhooks, it is masked to a first name and a surname initial, or to the last digits of the number. Marketing e-mail is sent only to people who separately opted in.
CRM connections you can switch off — and back on. Disconnecting a Bitrix24 or Uspacy installation now really stops the flow, and a Reconnect button brings it back without reinstalling. Signing in from Bitrix24 no longer needs an e-mail address: you are recognized by your CRM identity.
The Analysis Setup hub explains each step — what it decides, what happens if you skip it, and where the result shows up — and no longer scrolls the editor out of view. Renamed for clarity: “Script” is now Script rules, “prompt profile” is analysis profile. The “Competitions” page has been removed, and the team quality table lists people without ranks or medals.
Smaller fixes you may notice: the projects list filters correctly and “All” includes paused projects; the quality figure on project cards is a 30-day window; “Open in CRM” leads to the record’s own portal; call statistics respect the selected project; a dashboard alert link opens that alert; counts and rule-builder labels read naturally in every language.

Compliance settings that fit your jurisdiction, and Aelo speaks your language from the first screen · 2.26

Set up recording compliance the way your organization actually works. The approach and the legal basis are no longer limited to consent and to GDPR article numbers: if your organization does not rely on the consent of call participants, choose Other lawful basis and then select the basis that applies — including Other basis under applicable law for one defined outside the listed categories. Every option now explains in a line what it means in practice.
The compliance screen is available in your language. A language switcher sits on the screen itself, so the declaration you sign is one you can read. Nothing is preselected for you either — the approach, the jurisdiction and the legal basis are yours to state, and the form waits until you have.
Installing from Bitrix24 sets up Aelo in your portal’s language. The organization, its project and the sample data on the first dashboard now all follow the language of the portal you installed from, instead of starting in English and waiting to be corrected by hand.
Times and durations read naturally in all four languages. Minutes, hours and seconds are now written the way each language writes them — “1 хв”, “8 год 30 хв”, “hace 5 min” — across dashboards, widgets and record cards.

Filter by several projects at once, and a paused project stops taking calls · 2.25

Dashboard filters accept more than one project now. Select two or more and every number reflects exactly that set — previously only the first project you picked was applied, silently narrowing the results to one.
The selection carries through when you drill into the records list, so the records you land on match the projects you just filtered by, not just one of them.
Archived projects no longer show up in the project filter. Only active and paused projects are listed, so closed-out projects don’t clutter the dropdown.
A paused project stops accepting new records everywhere — CRM sync, the public API, and file upload now all decline new calls and chats for a paused project, the same way an archived project already did. Records already in the project are unaffected.

The report you send onward says everything the panel does · 2.24

The printed report now carries every section of the analysis panel. Agreements reached, voice metrics, script adherence, business intelligence, the analysis profile and the deal’s stage all travel with the document — so a report forwarded to a manager or handed to a client shows the same picture you see on screen, not a shorter one.
It reads as a document, not a screenshot. The report is laid out in Aelo’s own paper design, the one this site and our emails use, so it prints cleanly and looks like something worth attaching to an email.
Headings and metric names are in your language, in all four we support.
A check that did not run says so. “Passed”, “failed” and “not applicable” are now three different answers instead of two, so a blank line no longer has to be guessed at.

Analysis starts when you decide · 2.23

A new organization no longer starts analysing on its own. Calls flow in and appear in the list from the first minute, so you can see the integration is working, but nothing is transcribed and no minutes are spent until you press Start analysis. You get the time to set up projects, criteria and prompts first.
What arrived while you were setting up is offered separately, with the price shown up front — how many conversations, how many minutes, and how much of it goes beyond your plan. You decide whether to process all of it or only today’s.
An empty balance now reads as “top up”, not as an error. Conversations wait in an “Awaiting top-up” state and resume once the balance is topped up, instead of appearing as failed.
Compliance is confirmed right after installation, before the setup questions — so calls stop being turned away during those first minutes.

Aelo comes to Uspacy, and your org chart keeps everyone · 2.20

Aelo now works inside Uspacy. Install it from the Uspacy Marketplace and your calls flow into Aelo the same way they do from Bitrix24 — analysed, scored and delivered back to the CRM card. Bitrix24 is no longer the only way in.
Importing your department tree keeps every employee, not only the ones already using Aelo. People without an account are listed as pending and become full members automatically once they sign in — you no longer have to re-import after onboarding your team.
Large org charts stay workable. Filter by name, collapse branches, or switch to a “problems only” view to see just the departments that need attention.
Set your compliance settings without leaving the CRM. The organization owner chooses consent mode, jurisdiction and legal basis right inside the embedded app.

July 2026

Department heads see their team’s calls · 2.19

Import your company’s department tree from Bitrix24 under Settings → Team → Org Structure. Aelo matches employees to their Aelo accounts by email address and shows you by name anyone it could not match.
A department head sees the calls of everyone below them in the tree — their own department and every department under it — without needing a project assignment. This works alongside project supervision, not instead of it: whoever oversees a project keeps seeing that project.
Assign a head by hand for any department, including ones where Bitrix24 names nobody. A manual assignment takes precedence over the portal and survives later imports; when the portal names someone else, the row says so.
The same boundary applies everywhere — the call list, the record card, transcripts, analyses and search all agree on what a person may open.

Supervision, staffing and alerts that follow your projects · 2.18

Projects are staffed from either side. Assign projects to a person under Settings → Team, or open a project’s own Team tab and choose who supervises it. Inviting a supervisor now asks which projects they will oversee, and the team list shows at a glance who is waiting for an assignment.
A supervisor sees the calls in the projects they oversee — transcripts, recordings and analyses — and the alerts and daily digest cover the same projects, so what they are told matches what they are responsible for. (Since 2.19 a supervisor can also see calls through the department tree — see above.)
Agents reach their own calls directly, without needing a project assignment, and only their own.
Rating an analysis is open to everyone who can see it, agents included — the quickest way to tell us where the AI read a conversation wrong.
Alert rules can require a specific phrase and report which mandatory phrases a conversation missed, so a script commitment becomes something you can measure.
Alerts reach your team chat, with sensible per-role defaults out of the box and one-click Telegram — no setup needed before the first alert arrives.
A rule tells you on its card when its metric is no longer available, so a rule that has stopped matching is visible instead of quiet.
The support chat knows who it is talking to inside the Bitrix24 app, so you can ask a question without introducing yourself first.

Telephony records carry the numbers behind the call · 2.17

Call direction is read from the call’s own numbers. Phone systems vary in how reliably they state direction, so Aelo determines it from the record itself — which keeps the client’s number and the agent’s on the right side of every call.
An inbound call says which line it came in on, so you can see which of your numbers the customer dialled.
The customer’s number is always on the card, even when no contact name is known — on an inbound call it is the one fact that identifies the caller.
A number where there is no name. Some phone systems do not attach an operator to a call at all. Aelo shows the extension that handled it, so calls from different seats are told apart even when no names are available. This is separate from the line: that is the public number the call went through, this is the seat that answered it.

Alerts now show their evidence — and let you act on it · 2.15

Every priority alert carries the line that triggered it. The card shows the quote from the conversation and where it was said, with the most serious alerts first — an older critical one stays above a newer minor one. You can tell at a glance whether a card deserves your morning, instead of opening five records to find out.
Opening a record from an alert plays the relevant moment. Instead of starting at the beginning, playback jumps to a twenty-second window around the quote, with one control to keep listening to the rest. It works the same inside Bitrix24.
Two actions moved into the alert itself. When someone promised to call a client back, the alert can create a Bitrix24 task or a planned call without leaving the page — and repeating the request will not create a second one. When a client’s tone dropped during a conversation, the alert can schedule a coaching session for that agent, tied to that recording.
Aelo can check whether promised callbacks were actually logged. If a conversation contains a commitment to call back and there is no matching open call in the CRM, you get an alert. This is off until you switch it on for a project — turning it on also enables extracting agreements from conversations, and the app says so before you confirm.
Client accounts see the same team picture as supervisors. Team overview, quality trends, calls to review and coaching now live on the client dashboard too, computed from the same data rather than a parallel version of it.
Recordings show which line the call came in on, for telephony that distinguishes several numbers.
Billing follows the conversation. The balance check and the charge are based on how much was actually spoken.

Personal data leaves your transcripts before they are saved · 2.14

For conversations processed through the new write paths, phone numbers, emails, payment cards and valid IBANs are removed from a transcript on write. For those paths, only the redacted text is kept; this was not retroactive and original audio remains unchanged. What gets removed is confirmed rather than guessed: card numbers by their checksum, IBANs by their country’s format, phone numbers by whether the number exists in a real numbering plan. Business figures stay intact — a sum, a date, an order number is not a phone number.
A new page explains exactly what happens to your data. Personal Data in Transcripts lists what is removed, what is kept, and — just as plainly — what the redaction cannot catch: your call recordings are stored unchanged, records created before this release are not rewritten, and a number dictated in words is not detectable.
CRM auto-fill note. Fields whose value is itself a phone number or an email can no longer be filled from what was said in the call. The contact’s own number is unaffected — it comes from the record, not from the transcript.

Cancel or downgrade with a clear conversation, and find integrations faster · 2.13

Canceling or downgrading now asks why, and confirms the change. When you start a cancellation, Aelo asks what prompted it and offers a fitting option before anything takes effect; downgrading a plan asks you to confirm first, so neither happens on an accidental click.
Connecting a data source is easier to navigate. Integrations are grouped by type — telephony and CRM — in a clean two-column layout, so the one you need is easier to spot as the list grows.
The business overview shows what you have left. A new card puts your remaining balance and included minutes alongside the existing metrics.
Your Bitrix24 portal language carries into Aelo. The interface language set in the portal now follows through to the app and your project.

Plans and billing, stated plainly · 2.12

What separates the plans is included minutes, the per-minute rate beyond those minutes, and access to the public API. Everything else — Bitrix24 and smart process, CRM import, routing rules, annotations and reviews, direct telephony, email digests — is part of every plan, Free included.
Changing plan shows what you will be charged. The confirmation names the amount that comes off your card at that moment, calculated from the same proration as the charge itself.
Your balance is always visible — including on plans where we credit the account under an agreement rather than you topping it up by card.
Emails from Aelo keep their layout in every major mail client, Outlook included.

The API is easy to find, and plan cards say what you get · 2.11

The public API now appears where you connect your calls. Adding a data source shows it as a fourth option alongside Bitrix24 and the telephony providers, and takes you to Settings → API Keys, where the plan requirement is explained in place. That section is visible on every plan now — including Free — so you can see what the API does before deciding to upgrade.
Plan cards read the same source that bills you. Each plan shows its price, included minutes and the rate beyond them, and — for paid plans — what becomes available for the first time at that level, so the card cannot drift from your invoice.
Unitalk joins the source settings, and Ringostat is listed with the cloud PBX providers rather than call analytics.
The data-sources guide covers connecting via the API, in all four languages.

Upload calls to Aelo from your own systems · 2.10

A public upload API. You can now send calls and chats into Aelo straight from your own code — no Bitrix24 app required. Create a secret key under Settings → API Keys, then post recordings to the API and they flow into the same analysis pipeline as everything else. Available on Starter and above.
Built for integrations. Each key is scoped to what it may do, requests are rate-limited and idempotent, and the API tells you up front — before anything is stored — when a record can’t be processed on your current balance. Full details are in the API reference and upload guide.

A faster start, with everything included · 2.9

Installing from Bitrix24 takes seconds. Demo data is written in bulk, so you land in a ready dashboard almost immediately.
Every capability is on from day one. Alert rules, call scripts and data export are now included on every plan, and upcoming features appear as previews you can explore — no hidden switches to hunt for.
The app speaks your portal’s language. Installing from Bitrix24 picks up the language of your portal profile everywhere: the interface, organization emails and the default analysis language of your project.
A supervisor view for owners. The dashboard gains Quality and Agents tabs, so owners get the same per-agent quality breakdown supervisors use.
Progress at a glance. The agent dashboard shows the score trend as daily bars, and agent names in “Needs Attention” and “Top Improvers” now link straight to that agent’s dashboard.
Budget got its own tab in Plan & Billing, so spending controls no longer hide behind the plan details.

Analysis setup in one place, scores in the records list · 2.8

A guided “Analysis Setup” hub. Everything that shapes how calls are analyzed — evaluation criteria, scripts, category assignment, project overrides and delivery to the CRM — now lives in one place, laid out as a pipeline with a live readiness status on every step. The new “Configuration” section in the sidebar takes you straight there.
One records list instead of two. The “Analyses” page merged into “Records”: analysis quality and sentiment are now columns in the records table, with filters to match (including a QA-score range) and column visibility that remembers your choice. Old links redirect automatically.
A tidier records list. In the narrow layout the deal outcome shows as a colored dot with a tooltip, long call series group sensibly in the depth funnel (1–5, 6–10, 11–50, 51+), and short-call detection respects each project’s own threshold.

Steadier categorization · 2.7.5

Analysis runs on our AI provider’s newer recommended interface, which measured as more reliable end to end. Your transcripts are still not retained by the provider.

Sharper voice metrics and interface polish · 2.7.1

Speaking pace measured against the transcript. Pace is counted from the words actually said rather than estimated from the audio signal alone, so the words-per-minute figure and its slow/normal/fast verdict describe the conversation. When the measurement cannot be made reliably, Aelo says so instead of showing a confident number.
Polish across the interface. Empty states name the next step, speaker colours follow the speaker’s role, and Ukrainian, Russian and Spanish wording is more consistent throughout.

Analysis that fits the call · 2.7

Different scripts for different calls. Bind a script to a call category and pin the analysis config a project uses, so a support call is no longer graded against a sales script.
A fairer quality score. The score now averages six skills instead of seven. CRM completeness left the rating: it applies to a minority of calls, so averaging it in penalized agents for data collection that was never their job on that call. It stays as its own compliance indicator. Expect scores to shift slightly upward for teams that were carrying that penalty.
CRM completeness knows when it does not apply. If the customer is already in your CRM — a linked deal, contact or company — the metric reports “not applicable” and drops out of the rating, instead of scoring low for a task the call never had.
Scorecards that follow the deal stage (beta). Aelo can read a deal’s stage from Bitrix24 and grade the call against the scorecard bound to that stage, so a first call on a fresh lead and a contract-signing call are no longer judged by the same criteria. Opt-in per organization — ask us to switch it on.
Deal outcomes on the call. Calls now carry the outcome of the deal they belong to and how that deal moved between stages, with a conversion funnel on the Conversion tab.
Dashboards that explain their numbers. Quality trends mark the day you changed the AI configuration, KPI tooltips say where each number comes from, and supervisors get “objections the team drops”, “skipped script steps”, and a real compliance pass rate.
A coaching plan that writes itself. Each agent’s plan is built from the improvements their own calls suggested.
How it sounded, not just what was said. The analysis panel now shows pace, pauses and loudness measured from the call audio.
Every quote comes from the transcript, checked against it word for word, and categorization moved to a newer model picked by a head-to-head evaluation.
Tell the AI about your business. Organizations and projects can describe what they do and what they want out of analysis; that context goes into every call we analyze.
Recover calls that lost their recording. Admins can spot calls whose audio never arrived and re-fetch it from the CRM in batches.

Dashboards you can trust · 2.6

Real trends on every metric. Every KPI on every role dashboard shows its change against the previous period, including per-agent trends in the leaderboard.
Conversion funnel for call series. The owner dashboard shows how call series progress stage by stage, filterable by project, plus a breakdown of calls by direction, project, and hour of day.
Call category mix everywhere. Every dashboard now includes a breakdown of analyzed calls by category — for the whole team, per organization, and personally for each agent.
A real toolkit for supervisors. Hourly load and per-agent workload charts, a “calls to review” queue that surfaces flagged or low-scoring calls with one-click drill-down, script adherence by agent, and a working coaching tab.
Agent growth view. Agents can jump straight from a weak focus area to the exact calls that lowered it, and track their weekly streak and personal bests across their full history.
Owner finances at a glance. A revenue chart, cost breakdown by type, and balance with estimated runway — all computed from your actual usage charges.
Operations for admins. Integration health at a glance, processing errors grouped by source, and one-click retry right from the errors list.
Clear empty states. When a period simply has no data, dashboards say so in words.
Dashboards speak your language. Relative times, chart labels, categories, and coaching insights are now fully localized in all interface languages.

Sharper analysis & guided Bitrix24 onboarding · 2.3

More accurate call categorization. Internal and personal conversations are told apart from customer ones, and a call that mixes small talk with a real business request — prices, availability, an order — is routed to the customer category it belongs to.
“Other” is a described call, not a scored one. Personal and internal calls get a summary, topic, sentiment and key moments, and the analysis card explains why a sales score would mean nothing for them.
Call category at a glance. The record card header now shows the call’s category tag — the same one as in the records list — so you always know what kind of call you’re looking at without going back to the list.
Smarter re-analysis. Re-running an analysis now defaults to “Auto — category profile”: Aelo picks the evaluation profile bound to the call’s category, exactly like the normal pipeline. Selecting a specific profile remains available as an explicit override when you want particular criteria.
Speaker-level flags rest on evidence. Profanity and attention flags name a speaker only when the transcript shows it, and critical moments — churn risk, competitor mentions, sharp sentiment drops — are flagged more reliably.
Guided start inside Bitrix24. New embedded users get a welcome narrative with sample data for their industry, and a “Full portal” button opens the complete Aelo workspace in one click — no separate sign-in.
Category filters on the analysis card make it easier to jump to the score, script, speech, or insights sections.
Fuller owner dashboard. Organization owners now see the complete administrative picture — team leaderboard, sources, alerts, and delivery management included.

June 2026

Deeper Bitrix24 integration · 2.1

Smarter follow-up routing. Commitments that Aelo detects in a call now turn into the right Bitrix24 action automatically — an open promise becomes a record comment, while a “call you back” becomes a scheduled call activity. Each one carries a concrete due date and links back to the parent deal.
Call-chain tracking. Calls tied to the same CRM entity are grouped into a series, with each call numbered in sequence — so you can see how a deal progressed conversation by conversation.
Analytics into Smart Processes. Every analyzed call writes its full metric set (quality score, sale probability, sentiment, component scores, and more) into a dedicated Bitrix24 Smart Process item, kept up to date automatically.
Auto-fill empty fields. Delivery can populate blank CRM fields from the analysis without overwriting values your team already entered.
Demo analyses are clearly marked. Analyses generated from sample data now show an explicit notice, with a nudge to connect a real source.
Clearer short and missed calls. Very short calls (under the ingest minimum) and missed calls are now labelled everywhere, so it’s obvious why they don’t carry a quality score.

Prepaid billing, compliance, and a new look · 2.0

Transparent prepaid billing. Aelo moved to a prepaid model with live Stripe payments and minutes-based pricing. Top up your balance, see what each analysis costs, and track spend from the dashboard.
EU AI Act and GDPR documentation pass. A full review of how data is handled, with refreshed Privacy Policy, Terms, DPA, and sub-processor documentation.
Redesigned website and pricing, plus a platform-wide pass on usability, accessibility, and translations.

Category-aware analysis · 1.18

Category-bound prompt profiles. Analysis now adapts to the type of conversation (sales, support, and more), so each call is evaluated against the criteria that actually matter for it.

More telephony, email digests · 1.17

New telephony connectors: Unitalk, Binotel, and StreamTelcom join the supported integrations.
Email digest reports — recurring summaries delivered straight to your inbox.
Faster, more reliable transcription with an upgraded speech-to-text pipeline.

May 2026

Alerts you can act on in bulk · 1.16

Bulk-resolve for alerts — clear all matching alerts in one action, with an accurate live count shown in the sidebar.

Aelo arrives · 1.13–1.15

The platform is now Aelo (rebranded from AICA), with a refreshed design system across the app and website.
Demo Data v2 — explore the full product with realistic sample calls before connecting your own.
Public documentation site — the guides you’re reading now.

See where points are won and lost · 1.12

Component-level scores in the Analyses grid — drill into the individual criteria behind each conversation’s overall score.

April 2026

Coaching feedback and faster screens · 1.9–1.11

Agent rating & feedback — rate analyses and leave coaching comments, with a dedicated stars column in the records view.
Filter bars on Analyses and Alerts, plus a faster, smoother dashboard.

March 2026

Billing, search, and guided onboarding · 1.4

Stripe billing for subscriptions and usage.
Semantic search across your conversations — find calls by meaning, not just keywords.
In-app product tours that walk new users through each area.
Consent gate to support compliant recording.

Bitrix24 embedded mode · 1.2–1.3

Embedded Bitrix24 app — run Aelo directly inside your CRM, with controls over how results are delivered back to deals.
Guided onboarding and demo data for a faster first-run experience.
GDPR groundwork across data handling and consent.

1.0 — General Availability · 1.0–1.1

Aelo reaches 1.0: a redesigned interface, public website, documentation, and feature flags for controlled rollouts.
Category-aware analysis and lower AI costs.

January – March 2026 · the foundation

The early releases established the core platform:

AI Script Parser — turn your sales script into automatic adherence checks.
Call categorization powered by multiple AI providers.
Embedded mode and a rebuilt, role-based permissions model.
Multi-language interface with full localization.
A major performance and UX overhaul of the analytics experience.

Looking for the technical, version-by-version history? That lives in the project’s internal changelog. This page is the curated, customer-facing view.