Gamescom 2026 Grew Again and Exposed a Security Risk for Studios
Gamescom 2026 welcomed 368,000 visitors, but reported equipment thefts highlighted why studios need secure, recoverable event builds and demo infrastructure.
Gamescom 2026 confirmed the event's position at the centre of the international games industry.
Official figures from the organisers show that 368,000 people from 131 countries attended the Cologne event, up from 357,000 in 2025. The number of visitors arriving from outside Germany increased by 6%.
More than 36,000 trade visitors attended, while 1,743 companies from 66 countries exhibited - 11% more than the previous year. The 233,000-square-metre exhibition floor was fully booked for the first time, and 72% of exhibitors came from outside Germany.
Those numbers are a strong sign for the industry's global reach. They also describe an event operating at enormous physical and technical scale.
Unfortunately, another Gamescom story showed what that scale can mean for the smaller teams bringing valuable equipment and unfinished work onto the show floor.
Reported thefts affected multiple exhibitors
During the event, developers and publishers reported laptops and handheld hardware stolen from booths in both the Indie Area and business area.
GosuGamers reported that Tessera Studios found a locked cabinet forced open and two laptops and a Steam Deck missing. Solo developer Ryan Laley reported losing equipment used to demonstrate Mimic, cutting his event short. Publisher iam8bit said two laptops used for appointments had been taken from its business-area station.
The concern extended beyond the replacement cost of the devices. Some of the stolen hardware reportedly contained unfinished builds as well as personal, company or other sensitive information.
Gamescom said uniformed guards provide general venue security, that exhibitors can book individual stand security and that equipment insurance is advised. The organisers confirmed that the cases had been reported to police and investigations were underway.
Developers and industry figures criticised that response, particularly given the effect on small exhibitors and reports that equipment had been taken from locked storage or controlled areas.
The incidents should not overshadow the wider event, nor should the lesson be that affected teams simply failed to prepare. They do show that event planning must treat demo hardware as both a physical asset and a potential route into company systems.
A stolen laptop is more than lost hardware
For a studio, an event machine may contain much more than a playable build.
It can hold source-control credentials, API tokens, saved browser sessions, personal data, internal documents, crash dumps, unreleased assets and access to production services. Even if the laptop is replaceable, the uncertainty around what someone can reach from it creates a second incident.
That risk is especially difficult for indie teams. The same person may be responsible for the hardware, build, booth, meetings and incident response. Losing one machine can remove the demo and the tools required to recover it.
Studios therefore need to design event setups around two assumptions: a device may leave their control, and a device may fail immediately before an important meeting.
Build a clean event environment
An exhibition laptop should not be a developer's everyday workstation.
Use a dedicated event image containing only the demo and software required to run it. Encrypt the drive, apply operating-system updates and remove stored credentials, source repositories, unrelated builds and internal documents.
The demo should use separate accounts and an isolated backend environment. Avoid production secrets, broad cloud credentials and shared administrator logins. Tokens should be scoped to the smallest possible set of actions and given a clear expiry or revocation path.
If the device disappears, the first question should be “Which event credentials do we revoke?” rather than “What might have been saved on it?”
Make the demo recoverable
The event build should exist somewhere other than the device displaying it.
Keep a versioned, verified copy in a secure remote location and document the steps needed to provision a replacement machine. A spare device is helpful, but reproducibility matters more: the team should be able to move from clean hardware to a working demo without reconstructing the build from memory.
For multiplayer demonstrations, keep the backend and dedicated servers away from the booth. The exhibition laptop should be a replaceable client connecting to a remote test environment, not the only machine running the complete experience.
Monitor that environment from a second device and prepare a fallback mode for unreliable venue connectivity. Depending on the game, that might be a local offline path, a recorded walkthrough or a reduced demo that does not depend on every external service.
Treat event networks as untrusted
Busy event networks can be unpredictable even when nobody is attacking them.
Do not expose remote administration, RCON, databases or monitoring endpoints simply to make setup more convenient. Use secured management access and multi-factor authentication. Keep public game ports separate from administrative services and test the exact network path before the show opens.
The team should know what happens if venue Wi-Fi becomes congested, an external API is blocked or latency increases. A technically impressive demo is still fragile if one undocumented network dependency can stop it.
Physical controls still matter
Technical preparation does not replace basic booth security.
Record device serial numbers, use appropriate locks, understand venue storage rules and confirm what insurance covers. Decide whether equipment will remain overnight and whether individual stand security is appropriate. Avoid leaving small devices, removable storage or access badges unattended during setup and breakdown periods.
Most importantly, assign responsibility. “The team” cannot secure a booth unless one person knows who is checking the equipment, when it moves and where it is stored.
Prepare a short incident runbook
If equipment is missing, the first hour matters.
A practical event runbook should identify who will:
Contact venue security and local police.
Revoke credentials and invalidate active sessions.
Trigger device tracking or remote management controls.
Preserve account and audit logs.
Assess whether a build or company data could be exposed.
Notify partners, press appointments or affected users.
Restore the demo on replacement hardware.
Rehearsing that sequence once before travel can prevent several people from making the same calls while more urgent security actions wait.
Scale creates opportunity and responsibility
Gamescom 2026 was a major success by almost every attendance and participation measure. Its growth gives studios more opportunities to meet players, publishers, press and partners in one place.
The thefts are a reminder that the value concentrated inside the venue has grown too. For developers, event readiness now includes infrastructure recovery, credential control and data protection alongside travel, marketing and the demo itself.
PingCore helps studios keep multiplayer environments centrally managed rather than tied to a booth machine. Separate branches, scoped API access, remote monitoring and globally deployed game servers can make the event client easier to replace without putting the wider platform at risk.
