Companies that develop and publish video games, including game engines, digital storefronts, and related gaming software. It has no schema of its own: companies here are mapped on the Software & SaaS schema, and what it does not cover is recorded as gaps.
© 2026 System Atlas · Built by MIOSA
Free to map your own company · Members $300 a yearCounts of what public research has found and sourced, each part with its source on the organization’s profile. They say what is known, not how much of the industry exists.
Focused research on the organizations with the fewest mapped parts in video game developers and publishers; what it finds is public for everyone.
How automatable each primitive is, estimated from the 440 organizations mapped in public on the Software & SaaS schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.
| Primitive | Layer | Automation | Peers on software | Software parts named most |
|---|---|---|---|---|
Ideal customer and positioning Demand: winning customers | Decisions | LowEstimate | 0 of 31 on software | — |
Pipeline generation Demand: winning customers | Process | LowEstimate | 0 of 15 on software | — |
Sales Demand: winning customers | People | LowEstimate | 0 of 12 on software | — |
Packaging and pricing Demand: winning customers | Decisions | LowEstimate | 0 of 13 on software | — |
Quotes and order forms Demand: winning customers | Process | MediumLayer only | 0 of 440 mapped; too few to read | — |
Subscription agreements Demand: winning customers | Decisions | LowEstimate | 0 of 6 on software | — |
Product management Supply: making or delivering the offer | Process | LowEstimate | 21 of 430 on software | AI-Powered (11), Social Media Monitoring (3), Facial Recognition (2) |
Sprint and capacity planning Supply: making or delivering the offer | Process | MediumLayer only | 0 of 440 mapped; too few to read | — |
Procurement Supply: making or delivering the offer | Process | MediumLayer only | 1 of 440 mapped; too few to read | — |
Suppliers and partners Supply: making or delivering the offer | People | LowEstimate | 0 of 14 on software | — |
Running the service Supply: making or delivering the offer | Process | LowEstimate | 1 of 10 on software | Compute (agent sandboxes) (1) |
Testing and QA Supply: making or delivering the offer | Process | MediumLayer only | 4 of 440 mapped; too few to read | — |
Code, infrastructure and licences Supply: making or delivering the offer | Data | LowEstimate | 0 of 6 on software | — |
Provisioning Supply: making or delivering the offer | Process | MediumLayer only | 3 of 440 mapped; too few to read | — |
Product roadmap Supply: making or delivering the offer | Decisions | LowEstimate | 0 of 5 on software | — |
Engineering delivery Supply: making or delivering the offer | Process | MediumLayer only | 1 of 440 mapped; too few to read | — |
Releases and change communication Supply: making or delivering the offer | Process | LowEstimate | 0 of 8 on software | — |
Uptime and incidents Supply: making or delivering the offer | Process | MediumLayer only | 2 of 440 mapped; too few to read | — |
Implementation Customers: keeping them | Process | MediumLayer only | 3 of 440 mapped; too few to read | — |
Customer support Customers: keeping them | People | LowEstimate | 0 of 7 on software | — |
Customer success Customers: keeping them | People | LowLayer only | 1 of 440 mapped; too few to read | — |
Customer data Customers: keeping them | Data | LowEstimate | 0 of 6 on software | — |
Renewals Customers: keeping them | Process | MediumLayer only | 4 of 440 mapped; too few to read | Your Turn and We Met (1) |
Onboarding and activation Customers: keeping them | Process | MediumLayer only | 2 of 440 mapped; too few to read | — |
Churn and expansion Customers: keeping them | Data | MediumLayer only | 4 of 440 mapped; too few to read | — |
Invoicing Money: getting paid and paying | Process | MediumLayer only | 0 of 440 mapped; too few to read | — |
Collections and receivables Money: getting paid and paying | Process | MediumLayer only | 0 of 440 mapped; too few to read | — |
Payments and payables Money: getting paid and paying | Process | MediumLayer only | 1 of 440 mapped; too few to read | — |
Payroll Money: getting paid and paying | Process | MediumLayer only | 1 of 440 mapped; too few to read | — |
Revenue recognition and close Money: getting paid and paying | Software | HighLayer only | 0 of 440 mapped; too few to read | — |
Plan and burn Money: getting paid and paying | Decisions | LowLayer only | 0 of 440 mapped; too few to read | — |
Cash and treasury Money: getting paid and paying | Data | MediumLayer only | 0 of 440 mapped; too few to read | — |
Subscription billing Money: getting paid and paying | Software | HighEstimate | 5 of 5 on software | Credit-based plan billing with per-second compute metering (1), Membership charges at the then-current price (1), Metered actions and storage billing (1) |
Unit economics Money: getting paid and paying | Data | MediumLayer only | 0 of 440 mapped; too few to read | — |
Cloud and hosting costs Money: getting paid and paying | Data | MediumLayer only | 1 of 440 mapped; too few to read | — |
Org structure People: who does the work | People | LowEstimate | 0 of 22 on software | — |
Hiring People: who does the work | Process | LowEstimate | 0 of 7 on software | — |
Onboarding and training People: who does the work | Process | MediumLayer only | 2 of 440 mapped; too few to read | — |
Performance and pay People: who does the work | Decisions | LowLayer only | 2 of 440 mapped; too few to read | — |
Scheduling and capacity People: who does the work | Process | MediumLayer only | 0 of 440 mapped; too few to read | — |
Policies and culture People: who does the work | Decisions | LowEstimate | 0 of 7 on software | — |
Core system of record Systems: tools and data | Software | HighEstimate | 9 of 9 on software | Buffer app (scheduling and publishing) (1), Bumble app (1), Grindr app (1) |
Communication tools Systems: tools and data | Software | HighLayer only | 4 of 440 mapped; too few to read | IG Auto Reply, Audience Manager, short links and QR codes (1), In-app voice and video calls (1), QQ (1) |
Integrations Systems: tools and data | Software | HighLayer only | 4 of 440 mapped; too few to read | AI framework and observability integrations (1), Integrations (1), Link Apps marketplace (1) |
Metrics and board reporting Systems: tools and data | Data | LowEstimate | 0 of 9 on software | — |
Data management Systems: tools and data | Data | MediumLayer only | 2 of 440 mapped; too few to read | — |
Security and access Systems: tools and data | Decisions | LowEstimate | 1 of 7 on software | Private Detector and Deception Detector (AI safety) (1) |
Product analytics Systems: tools and data | Data | MediumLayer only | 4 of 440 mapped; too few to read | Reporting and Analytics (incl. Premium Analytics) (1) |
Licences and registrations Control: rules the company runs under | Decisions | LowLayer only | 1 of 440 mapped; too few to read | — |
Regulatory compliance Control: rules the company runs under | Decisions | LowEstimate | 0 of 6 on software | — |
Insurance and risk Control: rules the company runs under | Decisions | LowLayer only | 0 of 440 mapped; too few to read | — |
Legal and contracts administration Control: rules the company runs under | Data | MediumLayer only | 1 of 440 mapped; too few to read | — |
Health, safety and environment Control: rules the company runs under | Decisions | LowLayer only | 1 of 440 mapped; too few to read | — |
Data protection and security assurance Control: rules the company runs under | Decisions | LowEstimate | 0 of 9 on software | — |
Strategy and goals Direction: deciding where it goes | Decisions | LowEstimate | 0 of 20 on software | — |
Governance and decision rights Direction: deciding where it goes | Decisions | LowEstimate | 0 of 24 on software | — |
Management cadence Direction: deciding where it goes | Process | MediumLayer only | 0 of 440 mapped; too few to read | — |
Learning and improvement Direction: deciding where it goes | Process | MediumLayer only | 4 of 440 mapped; too few to read | — |
The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.