Too many logins
Each marketplace needs another login. That is why an overview of your own products is missing.
alveos
The metrics of your markets.
Many marketplaces stop at 90 days. Alveos keeps history according to the plan. Every channel, one place.
- Open VSX
- GitHub
- VS Code
- Downloads
- 895.9K
- Active instances
- —
- Updates
- 725.7K
Many marketplaces: 90 days. Alveos: span by plan.
The problem
Download statistics that are too short. Too many logins — an overview of your own products is missing.
A timeline that is too short
Marketplaces often store download statistics for only 30, 60, or 90 days. After that the trend is gone.
One place
Alveos gathers your markets. How far the history goes follows the plan, not a blanket year.
Your markets
Extensions, packages, apps, plugins — one view of every channel you ship to.
ExtensionsAppsPlugins
Longer than 90 days
Many marketplaces keep only 30, 60, or 90 days. Here you keep a year.
1 yearHistory
Your serving plate
That is what we call the one place for your numbers. Not five marketplace logins, not a dozen dashboards.
One placeYour numbers
Measure cause and effect
Numbers are useful. Putting the day next to them is better. Did the download line bend after the YouTube video? Did the market react to the version change? Alveos puts releases and stored figures on the same timeline — you check cause and effect without inventing the number.
Traceable data
Every number needs a provenance
Alveos stores provider values as timestamped snapshots and states what each metric means — and what it does not.
Public provider APIs and listings instead of paid scrapers or estimated values.
Controller in Luxembourg, hosting in Germany. Alveos does not sell the metrics and does not use Beacon for cross-site tracking.
Approved corrections do not overwrite the provider snapshot. They sit as a versioned read overlay in an audit-visible hash chain — after sign-in, when a correction is accepted.
VS Code Marketplace
Public Gallery counters. Meaning is in Methodology.
Public provider sourceOpen VSX
Public downloadCount. Meaning is in Methodology.
Public provider sourceGitHub Releases
Public download_count per release asset. Meaning is in Methodology.
Public provider sourceNo invented numbers. Alveos does not fill outages with estimates. A missed fetch stays visible as a gap. Methodology · Sources
Sample card
Invented numbers for illustration. Not a workspace, not live listings, no links.
Sample Extension
produkt_01
| Channel | Id | Gallery installs | From VS Code | Total install | Updates | Rating | Version | As of |
|---|---|---|---|---|---|---|---|---|
| VS Code | example.extension | 54 | 120 | 174 | 12 | — | 1.2.0 | 2026-09-21 |
| Open VSX | example.extension | — | 88 | — | 9 | — | 1.2.0 | 2026-09-21 |
| Video | Clicks | Likes | Comments |
|---|---|---|---|
| Add Video 01 | 22 | 1 | 0 |
| Add Video 02 | 18 | 1 | 0 |
- Open VSX
- GitHub
- VS Code
- Downloads
- 895.9K
- Active instances
- —
- Updates
- 725.7K
Many marketplaces: 90 days. Alveos: span by plan.
Mock, 30 days, produkt_01. Dashed lines: versions. Red dot: YouTube.
Ready to unify your metrics?
Sign in. One place for your markets. History span is on Pricing.