Download websites that use Gravitec

About Gravitec

Web push is the channel a publisher reaches for when email is not working and an app is out of the question. Gravitec is a tool for that channel. A site asks the visitor for notification permission, and once permission is granted the publisher can deliver messages to the browser afterwards, whether or not the visitor ever returns on their own. Sold by Gravitec since 2015 on a Freemium model, the product sits in our Widgets category alongside tools with very different economics.

The licensing detail is worth pausing on, because it shapes the population. A free tier that becomes paid at a subscriber threshold pulls in operators who would not buy retention software at all. So the install base leans toward independent publishers, regional news sites, niche content networks and small shops rather than the media groups that build the same capability in house. Anyone reading the list as a customer roster for a mature enterprise product will misread it. Taken instead as a map of sites that decided repeat traffic was worth interrupting a visitor for, the same list is far more useful.

What does presence actually imply? A site running push has a traffic problem it is trying to solve on the demand side. The business depends on return visits, the content refreshes often enough for a notification to have something to say, and somebody decided a permission prompt on arrival was an acceptable cost. For advertising vendors, content recommendation networks, hosting providers and anyone selling audience tooling, sites in that state are close to the definition of a qualified prospect, because the operator has already admitted the problem by installing something to fix it.

As of September 2026 we see Gravitec on 1,462 sites. The total is a starting point rather than the product. The file lets a researcher segment by country and top level domain, cross the population against advertising networks, publishing platforms and analytics to see which publisher profiles adopt push, and re run the same query later to watch churn, which is unusually informative in a category where tools get swapped often. A per domain check produces none of that, because each of those answers is a property of the whole population.

Detection has a specific weakness here. Push integrations register a service worker and often load their script conditionally, after a consent decision, after a delay, or only for visitors who have not already answered the prompt. A crawler that fetches a page once and accepts nothing misses a share of live deployments, and an abandoned service worker file can sit on a server long after the publisher moved on. The count records observed presence at fetch time rather than active accounts.