Game Development Company in Edinburgh

VGEC replaced the older Video Games Tax Relief (VGTR) from 1 January 2024. It is an above-the-line expenditure credit set at 34 percent of qualifying UK and EEA core expenditure, capped at 80 percent of total core spend. To qualify, the game must be certified by the British Film Institute under the cultural test (which scores cultural content, contribution, hubs, and practitioners) and developed by a UK-resident company actively engaged in development. Qualifying expenditure includes design, production, and testing carried out in the UK, but not initial concept or post-release marketing. We log every billable hour and asset to a VGEC-ready ledger from day one, prepare the BFI cultural test submission, and hand your accountant a CT600 attachment package that aligns with HMRC creative industries guidance. Older VGTR transition rules ran until 31 March 2027 for in-flight productions.

The Online Safety Act 2023 brings user-to-user game features (text chat, voice chat, UGC, livestreaming, friend-finding, marketplace listings) under Ofcom’s phased duty regime. Studios must complete an illegal content risk assessment, a children’s access assessment, and (if children are likely users) a separate children’s risk assessment, then put proportionate systems and processes in place against priority illegal content categories and harms to children. We build these obligations into the game backend: scalable text and voice moderation (Hive, Two Hat, or Modulate ToxMod), age assurance gateways, transparent reporting flows, and audit trails ready for Ofcom information notices. The Ofcom duties have phased in through 2024 and 2025, and penalties reach 10 percent of global revenue, so design has to bake compliance in from sprint one.

The ICO Age Appropriate Design Code (Children’s Code) sets fifteen standards for any online service likely to be accessed by under-18s in the UK, including high privacy defaults, data minimisation, no nudge techniques, no profiling for marketing, and transparent terms in age-appropriate language. For games, this means no behavioural advertising to minors, geolocation off by default, no dark patterns in monetisation, and clear parental controls. We design UX flows around the Code from the first wireframe, integrate age assurance providers (Yoti, AgeChecked, or VerifyMy) where the audience demands it, and produce a Children’s Code conformance statement signed off by the studio DPO. The ICO has shown willingness to enforce, and the Online Safety Act now layers additional Ofcom duties on top, so this is no longer optional for any title aimed at under-18s.

We build to the engineering standards Edinburgh demands because of Rockstar North’s presence: persistent-world session management, regional matchmaking at scale, anti-cheat with server-authoritative validation, drop-in and drop-out instancing, and telemetry pipelines built to absorb a launch-day spike. Our stack defaults are AWS GameLift with FleetIQ on eu-west-2 (London) and us-east-1 (N. Virginia), Nakama or AccelByte for session and inventory, Kafka and ClickHouse for telemetry, and Easy Anti-Cheat with custom heuristics on competitive titles. We do not pretend to be Rockstar, but we have shipped multiplayer backends that survive launch-week load, and we know what it takes to plug into a triple-A live-ops org without breaking their existing cadence. References from Edinburgh-area studios available under NDA.

From 1 April 2024 the UK merged the SME R&D scheme and RDEC into a single R&D Expenditure Credit at 20 percent above-the-line, with an enhanced rate for R&D-intensive loss-making SMEs. For games studios, you can stack VGEC at 34 percent on core production expenditure that meets the BFI cultural test with merged RDEC at 20 percent on genuinely novel R&D activity (new rendering techniques, novel AI behaviour, technically uncertain engine extensions, new netcode approaches). The expenditure cannot be double-counted: an engineer hour goes into VGEC or RDEC, not both. We maintain dual-tagged time logs and project ledgers so your accountant can carve the right portion to each scheme, and we document failed-hypothesis cycles in line with HMRC CIRD guidance for the RDEC narrative. Scottish Enterprise EDGE and R&D grants stack separately for SMEs.

Yes. Abertay University in Dundee has been ranked the UK’s top games-development institution for over a decade and runs the UK Games Talent and Finance CIC. Combined with the Edinburgh universities (Edinburgh’s informatics, Heriot-Watt’s graphics, Edinburgh Napier’s games design), this forty-mile Scottish Games Corridor is the densest games-talent pipeline in the UK. We hire and benchmark against Abertay-pipeline engineers, partner with Abertay’s ProtoPlay and Dare Academy alumni networks for prototyping work, and route junior hires through the corridor pipeline. For pure research questions (novel rendering, ML-driven NPC behaviour) we scope collaborations with Abertay’s InGAME centre or Edinburgh’s informatics labs rather than over-claiming in-house research capability.

Concurrency targets set the engineering bar on an Edinburgh multiplayer backend. A scoped multiplayer prototype (matchmaking, sessions, leaderboards, basic inventory, telemetry baseline) is a twelve to eighteen week engagement. A production multiplayer backend adds regional fleets, persistent inventory, anti-cheat, live-ops admin, A/B test infrastructure, VGEC-ready logs, and Online Safety Act controls. Triple-A scale backends add custom netcode, bespoke anti-cheat, MMO-style sharding, and launch-day capacity planning. Edinburgh sits close to London for senior multiplayer engineers because Rockstar, EA Cliffhanger, and Build a Rocket Boy compete for the same pool. We give fixed-fee proposals in GBP and net VGEC against scope where eligibility is clear.

PEGI is the pan-European ratings authority and is the statutory ratings system in the UK under the Video Recordings Act 1984 (administered by the Video Standards Council). Console submission to Sony, Microsoft, and Nintendo all require a valid PEGI rating, and the rating now interacts directly with the Online Safety Act’s child-safety duties under Ofcom: a PEGI 3, 7, or 12 title aimed at children triggers a tighter risk assessment than a PEGI 18 title. We prepare the PEGI submission pack alongside the Children’s Code conformance statement and the Online Safety Act risk assessment so the three artefacts are mutually consistent. For mobile titles, Google Play uses IARC (which feeds PEGI) and Apple uses its own age-rating questionnaire, both of which we handle alongside the underlying PEGI submission.