This website is a collaborative music database with a focus on progressive music, though not exclusively so. It is entirely non-commercial: there are no subscription fees and no advertising.
What Can I Do Here?
At its core is the music database, which you can browse to discover music: more than 25,000 artists and 85,000 releases, many rated and tagged, many linking to services like Spotify and Bandcamp.
With a free account, you can rate, tag and review music and add missing artists and releases. Through your tags, you and the other users determine each release's genre and "progressiveness".
Anyone who listens to a lot of music knows how hard it is to keep track. We provide a workflow for exactly that.
The Manifesto
These are the principles the website is built on.
01
Simple≫Complex
We keep things simple, at the expense of precision. Progressive music is an art form whose essential medium is the studio album, so we do not distinguish between versions: vinyl, re-releases, deluxe editions. There is only one Dark Side of the Moon.
02
Community≫Editors and Curators
The site is a collaborative effort of like-minded users. We do a little editing and curating, but only to give everyone a starting point; what we prefer is the organic, user-generated content. Apart from the trust rank, which counters abuse, and the weight familiarity gives a vote, all charts and lists are generated from the users' raw tag assignments.
03
Blurbs≫Reviews
We love lengthy reviews, but they take a long time to write. Blurbs are a little easier to write, particularly for releases you are not yet very familiar with, and they take less time to read. In the space of one lengthy review there could be ten concise blurbs by different users, each adding a unique insight.
04
Tag a Little Every Day≫Binge Tagging
Details are hard to remember, so assign tags while you listen, but do not overdo it. Make a habit of the basic tags and be more detailed now and then.
05
The Best Music≫Completionism
There is far more music than anyone can hear in a lifetime, so we focus on the best. Add, rate and tag your favorites first and give them the most detail; lower tier albums need only a rating and basic tags.
Joining and Signing In
How Do I Join?
Joining is free, and there is no password to choose. Sign up with your email address and a user name, and we email you a one-time code that creates your account (the same as signing in, see the next section). We simply ask you to accept our privacy policy and terms. We never share your email address with third parties.
Just want to look around first? Continue as a guest: no email, user name or password. A guest account works only in the browser it was made in, can rate and tag but cannot add to the catalogue, and can be upgraded to a full account any time.
Signing In and Staying Signed In
Signing in needs no password. Enter your email address (or user name) and we'll email you a six-digit code. Enter it on the website, or click the link in the email, and you're in. Each code is valid for 15 minutes and works once. If we don't recognise your email, we create your account on the spot. Members who have a password can use it instead and skip the code, and depending on the site's setup you may also be offered Sign in with Apple or Google.
Once you're in, your browser keeps you signed in, so there's no need to log in again on every visit. Your session refreshes itself in the background as you use the site and survives reloads and reopened tabs. If you don't return within 30 days it expires, and you simply request a fresh code. Multiple open tabs all share the same session.
For your security, the session is stored in your browser in a way that page scripts cannot read, so it can't be lifted by malicious code. When you log out, the session of that browser ends rather than lingering in the background. Other devices stay signed in; you can end their sessions one by one from your profile.
Can I Add Anything I Like?
As a rule, anything released as an album (CD, vinyl, digital, etc.) or music video (VHS, DVD, Blu-ray) can be added. Classical music is currently an exception, because the database does not yet support composer information. For now the focus is on any style of music except classical, though that may change in the future.
The Database
This part and the three after it explain the ideas the website is built around, from the shape of the database to how the charts are made. You don't need to memorise any of this – everything is explained again where you use it – but if you like to know how things fit together, this is the place.
Artists, Releases, Tracks and Videos
The database is organised the way a record shelf is. At the top are the artists – bands and solo performers. Every artist has a discography of releases: studio albums, EPs, singles, live albums, compilations, soundtracks and so on, each with its year and cover art. A release in turn consists of tracks, the individual songs or pieces on it.
Artists, releases and tracks can all have videos attached – links to performances, official clips or full-track uploads on video platforms. Videos can be rated and commented on just like the music itself, and the best of each year surface on the Videos Chart.
So when you look something up, you always land somewhere in this chain: an artist page lists their releases, a release page lists its tracks, and a track page lists its videos. Releases, tracks and videos can all be rated and tagged, which is what powers the various charts and rankings; artists are described by their releases.
Links to Other Websites
Releases, tracks and artists link out to the places where you can listen to them, read about them or buy them. On every page and in every list row, look for the links icon : the first two sites are spelled out right beside it as short abbreviations, and the icon (or the + count after them) opens a dialog listing every link the entry has, with the sites named in full.
Which Sites Do We Link To?
A release or a track can lead to:
Listening – Bandcamp, Qobuz, Tidal, SoundCloud, Apple Music, Spotify and YouTube. All the YouTube videos attached to a release or track are offered as one link, a YouTube playlist that plays them in order.
Reading – RateYourMusic, MusicBrainz, Discogs, ProgArchives, Metal Music Archives and Jazz Music Archives, plus Sputnikmusic, Metacritic and Album of the Year. Those last three arrive along with the ratings we import from them, so they cannot be added by hand.
Buying – Amazon.
An artist can lead to their pages on ProgArchives, Discogs and Bandcamp.
How Do I Add a Link?
Every signed-in member can add links to releases and tracks – there is no special role to apply for. (Guest accounts are the one exception, and you need to have picked a user name.) Open the links icon on the release or track: below the links it already has sits a field where you paste the address of the page and press Add Link. If an entry has no links at all yet, the icon still opens the dialog, so you can add the first one.
For a release, paste the release's own page on one of the sites above (Sputnikmusic, Metacritic and Album of the Year aside), or a YouTube video of it – official channels preferred. The form tells you right away when it does not recognise an address. A few rules catch most mistakes:
Discogs: link a specific release, not a master.
Bandcamp: the address must contain /album/ (or /track/ for a single).
RateYourMusic: link a release page (/release/…), not an artist page.
SoundCloud: link an album (/sets/…) or, for a single, a track page.
Underneath, the form lists the sites the release is still missing. Each name searches that site for the release, so finding the right page is one click away; MusicBrainz opens our own lookup instead, where you pick the matching release version and it is linked on the spot. When a site simply does not have the release, mark it not found, so the next member does not search again. A new link also pays off beyond the link itself: we use it to fill in missing cover art, the release date and the tracklist.
A release has one page on each site, so once a site is linked, only an admin can replace that link. If you spot a wrong one, let us know through the feedback button.
For a track, links are YouTube videos. Paste a video's address, or use the YouTube search in the form to find candidates and add one with a click. A video added to a track also shows up on its release and artist.
Artist links are looked after by our curators, so the add form only appears on artist pages for them. If an artist is missing a link, tell us.
Putting Your Favourite Sites First
Which two sites stay beside the links icon is up to you. Open Preferences at the top right of any page and go to the Links tab: drag the sites into the order you want to meet them, and switch off the ones you never use. The order applies everywhere links are shown – releases, tracks and artists alike. When you are signed in it is kept with your account; otherwise in your browser.
Genres and Phases
Progressive music has a history, and every release sits somewhere in it. Beside what a release is (its genre) and how progressive it is (its progressiveness), you can say where in its genre's life it stands. Three questions, three independent answers – and the badge words them in that order: Prog Symphonic Rock Revival is symphonic rock, progressive, in its Revival phase – a phase reading behind the genre it carries on, where an earlier one qualifies it from the front, Classic Prog Symphonic Rock. The Genres and Phases page (Alpha) plays the whole history out year by year, genre by genre, with the albums that stand for each phase – the prog genres marked, since not every genre with a history here is progressive.
The Prog Genres
Not every genre with a history here is progressive. A prog genre is one with a progressive form of its own – symphonic rock, Canterbury, krautrock, zeuhl, RIO, fusion, prog metal, Neo-Prog, post rock, djent – and is marked as one by the site. A genre that has years of its own but no such mark – hard rock, AOR, thrash, the blues strains, jazz and its schools – is a style with a history, not a prog genre. The mark says which genres the Genres and Phases page counts as progressive; it says nothing about phases, which every genre with years of its own has, on prog and non-prog releases alike. Jazz is the clearest case: its calendar is jazz's own, from the first recordings of 1917, and the jazz that is progressive is a genre of its own, jazz-fusion.
Between the two sit the prog-friendly genres: extreme metal, psychedelic rock, folk rock, blues rock and the two experimental genres. Most of what they hold is not prog, so a record of one is not taken to be progressive the way a symphonic rock record is – but they are home to a good deal of prog all the same (Opeth, Gorguts and Cynic are extreme metal), so they are shown beside the prog genres on the Genres and Phases page, the chart below and the prog spectrum, marked prog-friendly. Every other genre is non-prog: its records are taken not to be prog, though a member can still say an outlier is.
The calendar's grid is the decades. On it the charts tint the classic prog period: the years in which the original prog genres, those born with progressive rock in the late sixties, had their classic periods. It is read off those genres' own years rather than set by hand, so it moves when they do. Where a genre's phases begin and end is the genre's own business, and comes next.
Neo-Prog is a genre here, not a phase, born in the eighties. The "neo" prefix never settled anywhere else in prog as a period marker (nobody says neo-Canterbury), and Neo-Prog names a style rather than a period: Pendragon in 2011 and Marillion in 1983 are both Neo-Prog, which a phase could never say. So it has phases of its own, Classic through the eighties and nineties and the later phases since.
The Phases
Every genre passes through the same steps, but on a calendar of its own: a classic period with a first and a last year, a few proto years before it, and a retro year some way after it. From the last classic year on there are two readings of the same years: the faithful one, which takes the classic sound up again, and the transforming one, which takes the classic genre as a foundation and rebuilds it with the current means.
When
Faithful
Transforming
Up to the first classic year
Proto – not quite there yet
The classic period
Classic – founders and canon
From the last classic year
Revival – new bands take the classic sound up again
Modern – the classic genre transformed with today's influences
From the retro year
Retro – the classic sound as an accepted period style
Modern
A year on a seam belongs to both of its neighbours – the first classic year is Proto or Classic, the last one Classic or anything after – and your ear decides. A genre without proto years has no Proto; one without a retro year keeps the faithful reading at Revival, as art rock does, where nearly everything after 1983 is Modern anyway.
Continuation is the sixth phase: a founding band's own later work, whichever year it falls in, so that a 2021 album by a band from 1969 is not filed as its own tribute act. In front of the genre it read as a classification rather than a label; behind it, it reads like any other phase, so such a release is spelled out as, say, Prog Symphonic Rock Continuation – but only where the badge is spelled out in full, since it says something about the band rather than about the music. In a list row or under a cover it reads as if no phase were set.
Two things follow. Modern is a relationship, not a date: a 1997 Radiohead album is Modern art rock, a 2021 Wobbler album is Retro symphonic rock. Revival and Retro are the same faithfulness at two distances: Revival while bringing the sound back is still a cause – the eighties revival that Neo-Prog grew out of, the nineties one of Änglagård and The Flower Kings – and Retro once it is an accepted period style. Where that line falls is each genre's retro year.
Each Genre's Years
The periods as they stand, one bar per genre with years of its own, earliest first, on a grid of decades with the classic prog period behind them. The years are curated by hand and are what the phases tab goes by; hover a stretch for its years. Only genres a release is given are drawn, never a main genre; a genre that is not drawn has no years of its own and takes no phase (techno is not prog electronic, punk is not prog rock).
Assigning a Phase
Open a release's dialog, pick its genres (the musical note) and then their Genres part – it is always there, and asks you for a familiarity with the release first where you have none, since a genre is heard rather than looked up. Say how progressive the release is first, then pick its main genre, and out of that genre's own list the genre it is – one of its corners, Progressive Rock or Symphonic Rock, or Plain Rock for a rock record that is none of them. The main genre only leads you to that list: it is not assigned itself, but follows from the genre, as the family it belongs to. A genre of no family sits beside the main genres in the first list and is picked on its own, and None (Genre-Defying) – the answer that no genre fits at all – is the first genre's alone, since nothing stands beside it. The three scales decide what that list holds: a genre that contradicts them stays on it greyed out, saying why, and one you hold from before stays on show to be cleared. The familiar main genres come first, the rest by name. Each button is named the way the release will read with that genre on it – the modifiers you have ranked, the level word and the genre, Heavy Prog Hard Rock – so picking is a matter of reading rather than of imagining. The wording itself – Symphonic Prog for symphonic rock on a prog release, Prog-Adj Rock for rock on a prog-adjacent one – comes from the prog status, the genre and the phase together, the way the badge words them, and that is what the summary line over the pickers and the buttons of your genres page say. Then the phase, where the genre has one. Each genre waits behind a button – the primary one first, then a second and a third for where one does not tell the whole story – and once its phase is settled it folds to a line naming the pick, with a button to change it and one to remove it. Only the phases the release year leaves open on that genre are offered: a 1967 symphonic prog record can only be Proto, a 1969 one Proto or Classic, a 1975 one only Classic, a 1985 one Revival or Modern (or a founder's Continuation), a 2020 one Retro or Modern (or Continuation) – and a release older than a genre's first proto year takes none. The prog status has no say in it: a 1985 hard rock record is Revival hard rock whether or not it is prog, and the badge says so. A phase you set before a genre's years moved stays on show even where it is no longer offered, so you can see it and clear it.
The phase rides on your genre tag: it shows on your review, it is kept when you change the genre's strength elsewhere, and it goes when you take the genre off. What the community as a whole says is aggregated the way tags are – weighted by trust rank and familiarity – and shown beside the genre on the release.
The Main Modifiers, and What a Genre Says About Them
Three questions decide whether a record belongs on this site at all, and each is a tag of its own with a scale from 0 to 100. Together they are the main modifiers:
Progressiveness – the elaborate, through-composed approach. Read as Prog from 60, Prog-Adjacent (Prog-Adj on the badge) from 40 and Non-Prog below, which is the word the badge carries.
Avant-Garde – a tradition: the line from Zappa, Henry Cow and the RIO festival to Zorn, Mr. Bungle and Kayo Dot, music that belongs to a school of breaking form.
Experimental – a process: trying things whose outcome is uncertain, whatever tradition the record otherwise sits in, from Faust to Radiohead to Chat Pile.
They are independent of one another – a record can be any combination of the three – and they are the reason the three sit apart from the eighty-odd adjectives the vocabulary also holds. You set them in one place, on a scale each, at the top of the Genres part of a release's genres action; they are not offered in the tag table beside Melodic and Dissonant at the bottom of it, because the genre you pick just under them has a say in what they are.
Some Genres Imply a Level
Genres and the main modifiers work together rather than side by side. A genre can carry a flag on each of the three, curated per genre, saying one of three things: that a record of this genre is that by definition, that it is not, or – the usual case – nothing at all. Progressive Metal is progressive by definition and says nothing about the other two; RIO and Avant-Garde Metal are both progressive and avant-garde; the two Experimental genres are experimental and leave progressiveness to you; hard rock says nothing about anything.
The flag settles whether, and you still say how much. When you assign such a genre, each criterion it has a flag for is written on your own rows: a value you never set is filled in with a plain yes (60) or a plain no (0), and a value you did set is brought to 40 – where the two bands meet – only if it sits on the wrong side of it, and is left exactly as it is inside the band the genre allows. So picking Progressive Metal on a record you had called Non-Prog makes it Prog-Adjacent, not Prog: the genre is entitled to say the record is progressive at all, and how progressive stays yours.
The same rule read backwards is what the editor shows you before you pick anything. The side of a scale a genre you already hold leaves no room for is greyed, with that genre named as the reason, and a tap in it lands on 40. And the genres a slot lets you pick are those that do not contradict what the scales say – no prog genre on a release you have placed as Non-Prog, no RIO on one you have placed below 40 on avant-garde. A genre that does stays on the list greyed out, saying why, so you can see what moving a scale would open up. A genre you already hold can always be picked again to clear it. In other words: a genre can be picked exactly when assigning it would not move a value you have set.
The Other Modifiers
The adjectives that qualify a genre – Heavy, Symphonic, Space, Cosmic – are the other modifiers, and the same Genres part ranks them, in the tag groups under the genre slots: you pick the word that applies most as your primary modifier, then a second under it, and so on. The ranking is stored as the tag's strength, strongest first, and the badge words the primary one. The genre buttons are named the way the release will read once that genre is on it – pick Heavy, hold the release at 60 or more on progressiveness, and the Hard Rock button reads Heavy Prog Hard Rock – less any word the genre already says for itself, since Avant-Garde Avant-Garde Metal is nobody's idea of a badge. Those qualifying words are the same in front of every button, so they are drawn faintly and the genre name is not: the names are what you are choosing between, and the rest is there to be read rather than read past.
Your Collection
What you keep track of for yourself: how a release stands in relation to your collection, what you want to listen to next, and how well you know what you have heard.
Releases and Your Collection Status
Once you are signed in, every release can carry your personal collection status – a one-word verdict that says how the release stands in relation to your collection. A release has at most one collection status at a time, and you can change it whenever your opinion moves on:
Noticed – you gave it a fair chance, but it is not really for you, so it stays outside your collection.
Liked – you like it without owning it: part of your extended collection.
Wishlist – you want to buy it.
Collection (the Own button) – you own it.
Sold – you owned it once and have sold it.
Hidden (the Hide button) – it is not for you, and we'll stop suggesting it.
Every collection status but Sold doubles as a list: your wishlist, collection, liked, noticed and hidden releases are simply the releases carrying that status, so your library builds itself as you record verdicts. Two of them also tidy your recommendations: marking a pick as noticed or hidden takes it off the list and makes room for a fresh one (so does bookmarking it or logging a play). The picks themselves grow out of the releases you rated highest.
Bookmarks
Your bookmarks are your listening notepad: the releases, tracks and videos you marked as interesting and want to spend time with. Anyone who listens to a lot of music knows how hard it is to keep track of tips from friends, reviews and recommendations – your bookmarks are where they wait for you.
A bookmark is independent of a release's collection status. You can mark a release as noticed, like it or wishlist it while you are still exploring – it stays bookmarked – and when you are done with it, you remove the bookmark yourself. That way your bookmarks always reflect what you are currently exploring, not what you have already decided on.
The main way to bookmark something is the bookmark button on your recommendations, but you can also bookmark releases, tracks and videos directly from their pages. Members see how many releases they have bookmarked right in the navigation, one click away from the list, so the next thing to explore is never far away.
Plays and Familiarity
Whenever you listen to a release, a track or a video, you can log a play with the familiarity icon : it opens a dialog where Log Play records it, with nothing else to fill in. If you like, you can also note how thoroughly you played it (a skim, a partial play or a complete play), in what situation – focused at home, on your commute, at the office, out running, and so on – what you played it from (the CD or the record you own, a streaming service, YouTube) and what you listened through – headphones, studio monitors, the hi-fi, the laptop's own speaker: either right away behind add more info, or afterwards from the list of plays below it, where every play you can still delete carries a dropdown for each. A video is always a YouTube video, so a video play does not ask what it was played from – but it asks what you watched it on (a phone, a tablet, a computer screen, a TV, a projector), as does a play of a video release or of a track on one. Your plays appear on the public timelines, and the plays page shows what the most active members have been playing.
Out of your plays grows your familiarity with each item: a simple ladder from "unfamiliar" over "played once" and "played a few times" up to "10+ plays". The level follows the number of complete plays you have logged (a skim or a partial play only counts while there is nothing fuller), and you can also set it directly – useful for music you already know inside out from before you joined. Setting it adds the plays you never logged; it cannot go below what your logged plays already show. A track you have not recorded a level for shows the level you gave the whole release, until you set one for the track itself.
Familiarity is more than a statistic: you are asked to record how well you know something before you rate or tag it. That keeps the ratings honest – a verdict after ten listens carries different weight than a first impression – and it helps you remember which releases deserve another spin before you make up your mind.
Rating and Tagging
How you say what you think of the music: the ratings and their tiers, the other scales they map onto, and the blurbs, reviews and rankings that go further than a number.
Ratings and Tags
The heart of the website is what members say about the music. Everything is rated on a scale from 0 to 100, divided into seven named tiers from S – "Stellar" at the top down to F – "Awful". You can rate whole releases as well as individual tracks. The sections below break the tiers down in detail, show how your judgement of the music and your personal taste get a rating each, and explain how the individual ratings are combined into the aggregate scores you see on charts and rankings.
Tags describe what the music is, rather than how good it is: its genre and subgenres, styles, moods and – this being a website with a focus on progressive music – how "prog" it is. You don't need to be an expert: through the tags all members assign together, the community as a whole settles each release's genre and character. The tags page lists the tags we currently support.
The Rating Tiers
On this website everything is rated and tagged on a scale from 0 to 100. We divide this scale into 7 tiers. The three topmost tiers form the "high" group which has the music you rate best. The two lowest tiers form the "low" group which is for all the releases you have no time for. The two remaining tiers form the "mid" group which contains releases that land somewhere in between.
To help you calibrate, the table also shows how each tier lines up with three other scales: the 1-15 grades of the now-offline Gnosis website, the five stars of ProgArchives, and the half stars of RateYourMusic. The original meaning of the Gnosis grades and ProgArchives stars is preserved in the boxes below the table, next to the value each RateYourMusic step is imported as.
S"Stellar" ("Treasured")
Low/-90-92Mid93-96High/+97-100
Gnosis14-15ProgArchivesRateYourMusic5
The very top of the scale: music you consider outstanding by any measure, and treasure personally. You return to these again and again, and you would defend them to anyone. Reserve this tier - a scale where everything is stellar says nothing. And yes, it is the only tier that is eleven points wide: this one goes to eleven.
A"Awesome" ("Loved")
Low/-80-82Mid83-86High/+87-89
Gnosis12-13ProgArchivesRateYourMusic4.5
Excellent music, and where the bulk of your favorites live. Only a rare few sit above it; a lot of music you reach for less often sits below.
B"Great" ("Liked")
Low/-70-72Mid73-76High/+77-79
Gnosis10-11ProgArchivesRateYourMusic4
Well made and worth hearing, but not among the music you return to. You genuinely like these releases without reaching for them often - there is music you rate higher, or something about them keeps you at arm's length.
C"Good" ("Appreciated")
Low/-60-62Mid63-66High/+67-69
Gnosis8-9ProgArchivesRateYourMusic3.5
Solid music that does what it sets out to do. You enjoy it, or parts of it, but it did not make your inner circle.
D"OK" ("Indifferent")
Low/-40-46Mid47-52High/+53-59
Gnosis6-7ProgArchivesRateYourMusic2.5-3
The middle of the scale: unremarkable, or a mixed bag. You would not put it on voluntarily, but you cannot dislike it either.
E"Poor" ("Disliked")
Low/-20-26Mid27-32High/+33-39
Gnosis4-5ProgArchivesRateYourMusic1.5-2
Music you consider poor, or simply cannot enjoy. If it is the latter, use the subjective reading: a release others rate highly can sit here because it rubs you the wrong way.
F"Awful" ("Hated")
Low/-0-6Mid7-12High/+13-19
Gnosis1-3ProgArchivesRateYourMusic0.5-1
The strongest statement on the scale: the music fails or actively repels you. Reserve it for what you truly cannot sit through, not what merely bores you.
Points
Tier
Label
Low/-
Mid
High/+
Gnosis Rating
ProgArchives Stars
RateYourMusic Stars
11
S
"Stellar" ("Treasured")
90-92
93-96
97-100
14-15
5
The very top of the scale: music you consider outstanding by any measure, and treasure personally. You return to these again and again, and you would defend them to anyone. Reserve this tier - a scale where everything is stellar says nothing. And yes, it is the only tier that is eleven points wide: this one goes to eleven.
10
A
"Awesome" ("Loved")
80-82
83-86
87-89
12-13
4.5
Excellent music, and where the bulk of your favorites live. Only a rare few sit above it; a lot of music you reach for less often sits below.
10
B
"Great" ("Liked")
70-72
73-76
77-79
10-11
4
Well made and worth hearing, but not among the music you return to. You genuinely like these releases without reaching for them often - there is music you rate higher, or something about them keeps you at arm's length.
10
C
"Good" ("Appreciated")
60-62
63-66
67-69
8-9
3.5
Solid music that does what it sets out to do. You enjoy it, or parts of it, but it did not make your inner circle.
20
D
"OK" ("Indifferent")
40-46
47-52
53-59
6-7
2.5-3
The middle of the scale: unremarkable, or a mixed bag. You would not put it on voluntarily, but you cannot dislike it either.
20
E
"Poor" ("Disliked")
20-26
27-32
33-39
4-5
1.5-2
Music you consider poor, or simply cannot enjoy. If it is the latter, use the subjective reading: a release others rate highly can sit here because it rubs you the wrong way.
20
F
"Awful" ("Hated")
0-6
7-12
13-19
1-3
0.5-1
The strongest statement on the scale: the music fails or actively repels you. Reserve it for what you truly cannot sit through, not what merely bores you.
Other Scales: Gnosis, ProgArchives and RateYourMusic
The Gnosis Grades
Gnosis, whose grades the tiers table maps onto, is offline these days, so we preserve its original grade descriptions here, alongside the tier each grade maps to, the ProgArchives stars that tier is worth and the rating a ratings import saves the grade as: the middle of the grade's share of its tier - the upper or lower half where a tier takes two grades, a third of F, which takes three.
15S98One of the best ever, perfect. We suggest to raters that, at most, the top 1% of all albums receive a 15. While any rating from 12 through 15 can accurately be described with the superlatives "masterpiece" or "classic," only the 15s should appeal to the rater in as profound a manner as possible.
14S92A near perfect classic. In many ways, the difference between 15s and 14s are barely existent; 14s are fantastic albums that either have a very minor flaw or just don’t take it to the next level. We suggest to raters that, at most, the top 5% of all albums receive either a 14 or 15.
13A87A classic, but not one of the very best. 13s are exalted grades. They are used for albums that the raters consider a classic or a masterpiece, yet did not make the very peak of the hill. A 13 is still an extremely highly recommended item, one that has few flaws. This rating can also be considered an "in-between" grade between favorites and borderline classics.
12A82A borderline classic. A 12 is an album that one might instantly apply the word "classic" to, but on deeper reflection, one might not be so sure. There may be slight flaws that would have one hesitate on an intensely specific and critical level, yet a 12 is still an album that would have one mesmerized.
11B77Excellent. While not a classic, an album that is very enjoyable and an important part of one’s collection. We recommend that raters not give grades higher than 11 on the very first listen.
10B72Very good. An album that, while not great, is definitely worth keeping and is very enjoyable.
9C67Pretty good. While an album better than most, one may or may not keep an album with a rating of 9.
8C62Slightly above average. An album with noticeable flaws, although few permeate the album entirely. Perhaps half the album is superb but the other half is so-so. Or there’s a sentimental connection and little else.
7D55Completely mediocre. Neither good nor bad. In the greater scheme of things, an album rated as a 7 has been buried under a pile of much superior titles, and while one is not ready to pan it, the rating implies that, er… can you put something else on?
6D45Slightly below average. Just a tad worse than mediocre. Perhaps some parts are outright annoying or distasteful.
5E35Below average. Maybe not outright "bad", but definitely a poor effort.
4E25Pretty bad. A grade of 4 indicates a strong recommendation to avoid.
3F16Bad. An album that contains a handful of decent moments in an otherwise atrocious outing.
2F10Very bad, but there are worse. Although an incredibly poor effort, not one of the very worst. However, that’s not to say that there are any redeeming values.
1F3The worst thing ever. Intolerable. Godawful. A frisbee. A perfect example of something that one loves to hate.
The ProgArchives Stars
For completeness, this is how ProgArchives words its five star ratings, alongside the tiers each one maps to, the Gnosis grades those tiers cover and the rating a ratings import saves the stars as - which is also what the Enhance ProgArchives ratings sync saves. That is the middle of a tier, and where a star count covers two tiers, of the lower one: three stars are a C, 65.
S9514-15Essential: a masterpiece of progressive rock music
A8512-13Excellent addition to any prog rock music collection
B-C658-11Good, but non-essential
D-E304-7Collectors/fans only
F101-3Poor. Only for completionists
The RateYourMusic Stars
RateYourMusic rates in half stars, and your RateYourMusic export can be imported as it is. Each step is saved in the middle of its tier rather than on a straight line (five stars become 95, the middle of S, not 100), so an imported rating sits squarely inside its tier. The top four steps get a tier each; the three lowest tiers are twenty points wide, so two steps share each, one in the middle of either half. Unrated albums in your collection are imported without a rating.
S95the middle of S (90-100)
A85the middle of A (80-89)
B75the middle of B (70-79)
C65the middle of C (60-69)
D55the middle of the upper half of D (50-59)
D45the middle of the lower half of D (40-49)
E35the middle of the upper half of E (30-39)
E25the middle of the lower half of E (20-29)
F15the middle of the upper half of F (10-19)
F5the middle of the lower half of F (0-9)
Your Judgement and Your Taste
Your overall rating is your judgement of the music, and the tiers are worded that way: "Stellar", "OK", "Awful" describe the release. When your personal taste says something different, give a subjective rating as well – the link under the overall slider in the rating editor adds one. It has a scale of its own worded as statements about you: "Treasured", "Indifferent", "Hated". It is optional and sits beside the overall rating rather than changing it; neither is the lesser claim. A video has a single rating instead: you say above its scale whether it is your judgement or your personal taste, and it is worded accordingly.
Tier
Overall rating
Subjective rating
S
Stellar, Masterpiece, Landmark
Treasured
A
Awesome, Excellent
Loved
B
Great, Accomplished
Liked
C
Good, Solid
Appreciated
D
OK, Bland, Mixed Bag
Indifferent, Meh, Not For Me
E
Poor, Flawed
Disliked
F
Awful
Hated
Reach for the subjective rating when the two would say different things: a release you know is well made but cannot enjoy can be "Great" overall and "Disliked" to you. Where the overall rating lists several labels you can fine-tune the wording: "Mixed Bag" for a release with moments worth hearing that is otherwise flawed, "Bland" for one that is competently made but unexciting. Changing your rating to another tier resets the label, so a wording never outlives the tier it was chosen for.
Chosen labels are counted across members, so a release page can show how it is read - "seen as: Mixed Bag" - alongside how it is scored. Only wordings someone actively picked are counted: a tier's default is what every rating in that tier already says and would add nothing beyond the score itself.
Stances: What You Love and What You Can't Stand
A rating is one number, but it is rarely one reason. Some aspects of a release pull it up for you and others drag it down: maybe the drumming is worth a tier on its own, maybe the production costs it two. Those are stances, and you can record them right in the rating editor, for releases and for individual tracks.
A stance always targets one of the curated aspects we maintain - like "Dynamic Production", "Brickwalled Production" or "Cheesy Lyrics". The aspects themselves are neutral descriptions, and everyone picks from the same curated list: the loud production that earns a tier from one member costs another two, and because the words are shared, those takes add up into meaningful counts instead of a pile of free-text variants.
The editor offers your personal set of aspects: every aspect you have taken a stance on before, plus anything you add on the spot - most of us keep coming back to a relatively small, stable set of aspects, and this way they are one click away on everything you rate.
You say how much an aspect moved you in the unit your rating already uses: rating tiers. The scale runs -2 tiers / -1 tier / no change / +1 tier / +2 tiers – so "-1 tier" says the production kept the release off the tier it would otherwise have reached, and "-2 tiers" that it cost it two. "No change" is a stance as well: the aspect is there and worth naming, it just did not move your verdict. Leaving an aspect unset is the different statement that it does not apply here at all.
The rating editor shows this as a table: one row per aspect, one column per step. Alongside your own aspects it automatically lists every aspect other members have already marked on the release, so you can weigh in on what the community is discussing.
Because a stance is specific ("Brickwalled Production", not just "bad production"), other members can tell whether your reservation would even apply to them: release and track pages show what lifted the music in members' ratings and what held it back. Aspects that moved nobody stay out of those lines. Tracks carry their own stances.
Those lines are ordered by trust, the same way the aggregated tags are: a stance from someone who knows the music well and has earned trust reaches the front. The numbers stay plain head counts, so what you read is still how many members hold a take, not a score.
Blurbs and Reviews
Numbers and tags only say so much – sometimes you want to put your opinion into words. For that there are two formats. A blurb is a short text, preferably a one-liner, that we display right next to the name in lists and on the item's own page. You can write a blurb about a release, a track, a video or an artist – a quick "why this is worth your time" in a sentence or two.
A review is the long form: a lengthy, free-form text about a release, with paragraphs to structure your thoughts. Every review gets a page of its own that you can share, and reviews are also shown on the release page and in various lists. If you write a review, a blurb makes a great summary to go with it – the blurb travels with the release through the lists, and the release page shows your review in its place. The timelines – on the front page, on artist, release and member pages – carry every published text about a release, a track or a video among the rest of the activity, and each has a switch that narrows it down to just the blurbs and reviews.
Blurbs and reviews are public, and other members can react to them – a quick way to show appreciation without writing a reply. As with rating and tagging, you record your familiarity before writing about a release, a track or a video (artists have no familiarity, so an artist blurb needs none). And if you want to jot something down just for yourself, there are private notes on every release: they are never published and only you can see them.
Rankings
Rankings are the other way to say what you love – and for many people the more natural one. Instead of giving each release a number on the 0–100 scale, you put your favorites in order: your top albums of a year, a month, a decade or a single artist, and likewise your favorite tracks and videos. Not everyone thinks in scores, but almost everyone can say which album was their number one this year – ranking asks exactly that, and nothing more.
Building a list is meant to be fun: you pick your candidates and drag them into order, and your list is saved with the ranking. Each topic has room for a sensible number of entries – around ten for a month, twenty for a year or an artist, fifty for a whole decade. If you have already rated the releases, your ratings can pre-sort the list for you, so the two systems play together rather than compete.
Everyone's lists are then combined into an overall chart: the higher a release sits on your list, the more points it contributes, and the points from all lists add up to the community's standings. You can browse the combined chart, look at any member's individual list, and even wind the clock back to see how the race looked at an earlier date. Explore the current topics on the release rankings, track rankings, video rankings and epic rankings pages, or jump in from the Rankings menu in the navigation.
How the Charts Are Made
How everyone's ratings and tags add up to the aggregates, charts and rankings you see across the site.
Trust Rank
When all those individual ratings and tags are combined, not every vote weighs the same. Each member has a trust rank, and it is simply the weight their ratings, tags and stances carry in the aggregate: a member with a rank of 6 starts out with six times the weight of a member with a rank of 1. It never silences anyone, and it does not change what we count – where the site says how many members rated or tagged something, that is a plain head count of people.
The rank is calculated automatically, once a day, from exactly one thing: on how many different days you rated a release in the last 300 days. Rating twenty albums in one evening counts as one day, and so does rating one; tagging, rating tracks and subjective ratings do not add days. 47 such days reach the top of the automatic scale, which is 8; new accounts start at 1. Nobody sets a member's number by hand, and it is not a judgment of anyone's taste.
Because the window rolls along with you, a rank is not a permanent title: stop rating for a while and it drops back on its own, and it picks up again when you return. That is deliberate – in the spirit of a little every day, it rewards the habit of rating regularly rather than one weekend of binge rating.
Your rank is the starting point for a single vote. It is scaled by your familiarity with the release (a partial play counts for a fifth of it, your full rank applies from ten plays on, and a vote on a release you never set a familiarity for counts as if you had played it a few times), and low ratings count somewhat less than high ones, since a rating near the bottom usually comes from someone who did not spend much time with the music. A vote that counts at all keeps a weight of at least 1. Outright abuse is handled separately: banned accounts, spam accounts and guest accounts are skipped entirely.
How Are Ratings Aggregated?
There are many possible ways to calculate an aggregate rating from a list of individual ratings, which is what we obviously need to do for tracks and releases. The simplest is to compute an average value. But we think that this does not lead to the best results. Instead we compute the median value, or in other words, the typical value that is assigned by most users.
There are a few additional things we do. First, not every vote weighs the same: each one enters the calculation with a weight built from the member's trust rank – recalculated automatically from how regularly they rate releases – and from how well they know the music in question.
Second, every member counts once, with their overall rating where they gave one. A member who gave only a subjective rating counts with that instead, at half their weight, since taste is weaker evidence of how good a record is than a judgement of it. And a member who rated a release's tracks but not the release itself counts with the rating their track ratings add up to, also at half weight.
Third, instead of just taking an average or mean value from all the votes, we treat each calculation like a voting session in order to find the favorite value. To do that, we first determine the favorite tier group (low 0–39, mid 40–69, high 70–100). Then within the winning group, we determine the favorite tier. Then within that tier, we determine the favorite sub range. Then finally within that range we take the median value. Each round goes to whichever side carries the most weight – no outright majority needed. The same voting runs for releases, tracks, videos and tags.
This approach solves a problem that plagues larger rating websites: the more users "vote" on a release, the more the average gets dragged down to mediocrity even for masterpieces. At RYM, for instance, hardly any popular release scores above 4.0 (out of 5), because popular releases attract many users who give really low ratings out of spite or because they dislike the genre. The voting approach ignores those votes until they outweigh the others, so true masterpieces retain their high rating.
How Are Items Ranked?
When you browse the releases ordered by overall rank, the system needs to sort the releases in a way which takes into account the aggregated rating as well as the number of ratings. The simplest way to do that would be to sort by the product of these values. In practice we found that this boosts releases with a lot of ratings too much, so we chose to use a logarithmic value of the number of ratings instead, lessening the boosting effect somewhat.
So do not be surprised when in a list of ranked releases (or tracks) the aggregate rating of the releases appears to be unsorted, since items with lower aggregate ratings can outrank more highly rated items if the number of ratings is substantially higher. That number is a plain head count of the members whose vote counted; the trust weights described above shape the aggregate rating itself, not the count. For a release it counts everyone whose vote went into its rating, including those who only rated its tracks or only gave it a subjective rating, so it can be higher than the number of ratings the release page shows.
About This Website
How to reach us, and the website itself by the numbers.
Get In Touch
To get in touch, please use the feedback form or email us at info@awesomeprog.com. We especially welcome feature requests, and reports of any bug or other problem that keeps you from using the website.
Are You a Band or Artist?
If you would like your releases on this website, the easiest way is to add and tag them yourself. You are also welcome to send us links to your music through the feedback form, though we can't promise a review, as most of our time goes into maintenance and technical improvements. That said, we are always keen to discover new music and will give yours a listen when time allows.
Website Statistics
Tech Info
At its heart AwesomeProg is two programs. The website you are reading is ap-ui, written in TypeScript with React and Next.js; the server behind it is ap-api, written in Kotlin with Spring Boot, keeping everything in a PostgreSQL database. Here they are by the numbers, and after that the (free) tools and frameworks they are built with.
Frontend tests
8,767
Jest, in 675 spec files
End-to-end tests
33
Playwright, in 9 spec files
Backend tests
4,137
JUnit 6, in 394 test files
ap-ui coverage
88.82%
of statements, and 82.33% of branches, CRAP 17 at the 99th percentile and 30 at most
ap-api coverage
87.02%
of instructions, and 75.94% of branches, CRAP 14.5 at the 99th percentile and 30 at most
Pull requests
1,825
merged into main
Lines added
585,916
and 182,372 deleted since June 2026
Lines of code
304,815
174,342 ap-ui · 130,473 ap-api
Pages
168
routes in ap-ui
API endpoints
655
and 259 database migrations
Commits
7,901
since June 2022
Languages
Lines of code in both packages together, comments and blank lines not counted.
TypeScript55% · 168,984
Kotlin40% · 122,466
SQL3% · 7,763
SCSS1% · 4,463
Other<1% · 1,139
$ npx nx run ap-ui:tech-info
packages/ap-ui: 8,767 Jest tests in 675 files
------------------------------------------------
Language Files Blank Comment Code
------------------------------------------------
TypeScript 1,674 26,944 32,848 168,984
SCSS 31 847 1,287 4,463
JavaScript 13 110 269 895
------------------------------------------------
Total 1,718 27,901 34,404 174,342
------------------------------------------------
of which tests: 83,165 lines (48%)
packages/ap-ui-e2e: 33 Playwright tests in 9 files
packages/ap-api: 4,137 JUnit 6 tests in 394 files
------------------------------------------------
Language Files Blank Comment Code
------------------------------------------------
Kotlin 959 21,287 32,407 122,466
SQL 260 2,144 7,079 7,763
YAML 10 41 171 244
------------------------------------------------
Total 1,229 23,472 39,657 130,473
------------------------------------------------
of which tests: 60,960 lines (47%)
Measured on 2026-11-13 at commit 158394a20. Tests are counted as written, so a parameterised test counts once however many cases it runs.
Test Growth
How many tests each package had at the end of every day since its suite began, stacked by kind, with the coverage they reached and how their functions' CRAP scores were spread under them, and below both how many pull requests had been merged by then, with the lines of code added and deleted each day, and last the lines of code each package held, its production code and its tests apart. The first four years of the repository had a test or two between them, so the charts start where the suites did. Hover a chart for a day's figures; each one saves as an SVG or PNG picture, or as a CSV of its numbers.
ap-ui tests 8,800
Unitplain functions, no rendering
Componentrendered through Testing Library
End-to-endPlaywright, in a real browser against a mock API
ap-api tests 4,137
Unitno Spring, no database
IntegrationSpring and Postgres, no HTTP
APIthe running app, called over HTTP
Pull requests merged 1,825
Lines of code 305,146
ap-apiproduction code
ap-api testseverything under src/test
ap-uiproduction code
ap-ui testsspecs and the end-to-end suite
Counted by npx nx run ap-ui:test-history from the git history up to 158394a20 (2026-11-13), each day at its last commit on main; the pull requests are those of the whole repository, as GitHub lists them, and the lines changed those of every commit on main in TypeScript, Kotlin, SQL, SCSS, JavaScript and YAML, so lockfiles, fixtures and docs are left out. The lines of code are counted in the same languages, twice a week, at the last commit of each Monday and Thursday, a day between two showing the one before; ap-ui's tests take in the end-to-end suite of ap-ui-e2e. Coverage is measured week by week, by running both suites again at each week's last commit on main: ap-ui's share of statements and ap-api's of instructions, the figures the CI gate holds a run to, and the share of branches of both, which shows the paths left untested.
CRAP (change risk anti-patterns) scores a function by its complexity and how much of it the tests run: complexity² × (1 − coverage)³ + complexity, so a fully tested function scores its complexity and a trivial one 1. The panel draws three points of the spread, on a log scale: the median, the score half the functions stay at or under, the 90th and 99th percentiles, which follow the complex, thinly tested tail, and dashed above them the max, the one worst function. None of them hangs on a threshold, and none grows with the size of the codebase. Measured once a week by scripts/crap_history.py, each Friday at its last commit on main with a full run of the package's suite: ap-api's methods with JaCoCo's complexity and instruction coverage, ap-ui's functions with ESLint's complexity and Jest's statement coverage.