When we announced our debut showcase for May and opened submissions, we were surprised by the number of horror and suspense games sent in. In fact, over 30% of the games we received fell into that category. So, we wanted to give those games a chance in the spotlight. That’s why we’re proud to announce: Insider Gaming Presents 28 Games Later: A Horror Showcase.
Unlike our debut event, this show will feature games from teams of all sizes. From small indie games to larger AA and AAA titles, we aim to bring you a look at the best upcoming and recently released horror and suspense games.
The show will air on Thursday, October 1 at 3pm ET/8pm UK and will broadcast on all Insider Gaming platforms, such as YouTube, Twitch, Twitter, Facebook, TikTok, and more. We will also have several co-streaming partners airing the event as well.
Submit Your Game: Submissions are open until July 17
Like May’s Insider Gaming Showcase, 28 Games Later will feature back-to-back trailers and full game write-ups and previews on Insider-Gaming.com and in the free Insider Gaming App on Android and iOS.
Submissions for the showcase begin today and will remain open until July 17. If you have any questions about the showcase, please contact [email protected].
Sponsorship Opportunities
We are actively looking for those interested in sponsoring the event to help make it the best show it can be. Our debut showcase generated over 100,000 views, 1,000,000 social media impressions in the first 24 hours, and thousands of cumulative wishlists.
If you are interested in sponsoring Insider Gaming’s 28 Days Later: A Horror Showcase, please contact Tom Henderson at [email protected].
Co-Stream Opportunities
The Insider Gaming Showcase featured dozens of officially partnered co-streamers, and we want to do it again. If you are interested in co-streaming 28 Games Later – A Horror Showcase, please contact Mike Straw at [email protected].
It’s important to note that the showcase has the potential to include copyrighted music. We will do our best to provide licenses for the event, but there may be instances where we are unable to do so.




Comments