Marko
Marko is a declarative, HTML-based language for building dynamic and reactive user interfaces that supports streaming, async rendering and custom tags.
According to our data, Marko ranks 28th among the frontend frameworks we track.
It has 0.05% of the frontend framework market share and is detected on 0.006% of all websites.
- π Website
- </> Source code
πΈ Pricing
Marko is available for free.
π Rankings and Market Share
- Frontend Frameworks
- Rank: 28
- Market share: 0.05%
π Marko Awards
- π₯ 11st most popular in Brazil in the Frontend Frameworks category.
β‘ Sites Built With Marko
We have data on 214 websites that use the Marko frontend framework. Here is a list of some of the top ranked ones.
The highest rated site using Marko is ebay.com.
| # | Website | Rank | Country | Language |
|---|---|---|---|---|
| 1 | #92 | United States | American English | |
| 2 | #371 | United Kingdom | English | |
| 3 | #405 | Germany | English | |
| 4 | #558 | Switzerland | Italian | |
| 5 | #1,935 | Switzerland | English | |
| 6 | #2,029 | Australia | Australian English | |
| 7 | #2,065 | Canada | Canadian English | |
| 8 | #7,133 | Spain | European Spanish | |
| 9 | #16,456 | Austria | Austrian German | |
| 10 | #18,230 | Netherlands | English | |
| 11 | #19,109 | Poland | Polish | |
| 12 | #19,875 | Ireland | English | |
| 13 | #39,356 | Malaysia | English | |
| 14 | #50,066 | Hong Kong | Chinese | |
| 15 | #54,105 | Malaysia | English | |
| 16 | #55,067 | Singapore | English | |
| 17 | #56,844 | Switzerland | English | |
| 18 | #152,842 | Japan | Japanese | |
| 19 | #325,630 | Brazil | Brazilian Portuguese | |
| 20 | #328,747 | Brazil | Brazilian Portuguese |
π Usage Statistics
Most of the sites that use Marko:
- are located in Brazil
- have content in Portuguese
- use the .com.br domain extension
- fall into the Auctions/Classifieds category.
Most of the sites using Marko are from Brazil, Indonesia, and Switzerland.
- Brazil 52.5%
- Indonesia 13.5%
- Switzerland 5%
- United States 4%
- France 3.5%
- Australia 2%
- Germany 2%
- Malaysia 2%
- Spain 2%
- Other 13.5%
Most Marko users speak Portuguese, English, or Malay.
- Portuguese 49.5%
- English 26.9%
- Malay 6.1%
- French 4.7%
- Indonesian 2.8%
- German 2.4%
- Italian 1.9%
- Spanish 1.4%
- Polish 1.4%
- Other 2.9%
The Marko frontend framework is especially popular on .com.br and .com top-level domains.
- .com.br 45.8%
- .com 23.4%
- .org 4.2%
- .net 3.3%
- .de 1.9%
- .es 1.9%
- .it 1.9%
- .com.au 1.9%
- .fr 1.4%
- Other 14.3%
The primary market segments for websites utilizing Marko include auctions and classifieds, marketing and merchandising, and business.
- Auctions/Classifieds 60%
- Marketing/Merchandising 20%
- Business 6.7%
- Online Shopping 3.3%
- Entertainment 3.3%
- Blogs/Wiki 3.3%
- Real Estate 3.3%
- Other 0.1%
π΅οΈ Similar Technologies
These are some of the best Marko alternatives.
π Compare Alternatives
Compare Marko toβ¦
- π΅οΈ Similar frameworks
- β Market leaders
- π‘ More alternatives
- π All options
π¬ Frequently Asked Questions
What is the company behind Marko?
Marko is owned by eBay Inc., headquartered in San Jose, California, United States.
Can I use Marko for free?
Yes, it is a free frontend framework.
It is also open source and its code can be found on GitHub.
Which country uses Marko the most?
The majority of Marko users are from Brazil.
Who uses Marko?
According to our data, Marko is used on hundreds of sites, including such established ones as ebay.com,
ebay.co.uk, and
ebay.de.
How does Marko stack up against the competition?
Marko is a moderately popular frontend framework, ranking ahead of 22 other frontend frameworks we track.
π See Also
- β¨ Related technologies
- πΌ All technologies from
eBay
ποΈ About This Data
- We evaluate the popularity of technologies based on the number of websites where we detect their usage.
- Technologies without a detectable web footprint, and those we do not track, are not reflected in the calculated market share.
- This report is based on the analysis of 3,814,833 websites.
- Statistics were last calculated on .
- For more details, see our methodology and disclaimer.

