Lohika Games is the studio name associated with Machineers, yet the public Lohika company profile on LinkedIn describes a software development business, not a games studio. Use the app store developer listing as the final check on any credit.
This profile sits beside the main machineers game page and covers the company behind the name: what is publicly stated about it, how to read it, and what to check before treating any company page as a games credit.
How the Lohika name works
A developer name is only useful if it points to a company you can verify. The Lohika page on LinkedIn lists the company’s industry as software development and places it in San Mateo, California. It does not present Lohika as a games studio. A reader who searches for Lohika games should therefore expect the public information to describe a software services firm first and a game developer second, if at all.
That distinction shapes the rest of this profile in three stages:
- Identify the company. Start with what Lohika says about itself, including its headquarters, size, specialties and website.
- Read the business model. Look at what kind of work the company describes publicly, because a services firm and a game publisher are credited differently.
- Confirm the credit. Use the store listing for the game itself, not a company page, to settle who is responsible for a specific release.
Following those stages avoids a common mistake: assuming that a company page and a game’s developer line describe the same legal or creative entity just because the names look alike.
The Lohika company profile at a glance
The table below collects the attributes that Lohika publishes on its own LinkedIn page. They describe the company as a whole, so use them to identify the firm rather than to judge any single game.
| Attribute | Stated value | Planning use |
|---|---|---|
| Headquarters | San Mateo, CA, US (1825 S Grant St #400) | Match this against any registered address you find for a developer before assuming two names refer to the same company. |
| Company size | 501-1,000 employees band; 381 employees shown on the page | Indicates a company much larger than a typical small indie team, so do not read it as a handful of designers. |
| Industry | Software Development | Shows the primary business is software services, not game publishing. |
| Specialties | Software Development, Mobile Application Development, QA, R&D | Mobile and QA skills are relevant to mobile games, but the list names no game titles. |
| Type | Privately held | Private ownership means public financial detail is limited, so lean on the company’s own statements. |
| Ownership note | Lohika is now part of Capgemini | Check whether a developer credit predates or postdates this change when comparing older and newer material. |
| Website | https://www.lohika.com/ | Use it as the starting point for any official statement about the firm’s work. |
These figures come from Lohika’s own LinkedIn company page, which is the company’s self-description rather than a third-party assessment.
What the size band tells you
A band of 501-1,000 employees is a range, and the page also shows 381 employees. The practical conclusion is simpler: this is an organisation with hundreds of staff, which fits a services business serving several clients better than a small studio shipping its own puzzle game.
What the headquarters tells you
The listed headquarters is in San Mateo, California. Anyone searching for a Nordic or other European studio should keep that in mind. A company page can list a headquarters while teams work elsewhere, and a listed headquarters does not by itself say where a particular game was built. For a location claim about a game, rely on the game’s own developer page.
What Lohika says it does
Lohika presents itself as a software engineering partner. In a client post on LinkedIn, the company describes how Petuum needed to ramp up its software engineering team quickly to develop two prototypes within two weeks. That is an extended-team model: the firm supplies engineers who work as part of a client’s project.
This matters for anyone researching games. In an extended-team arrangement the client usually owns the product and its brand, so the services firm and the product’s publisher can be different entities. The Petuum example is not a games project, and it should not be read as evidence about any game. It shows how the company describes its core service, and that service is the lens through which its name should be read.
Events and startup links
A case study from the web agency BRINK describes Lohika as a premier startup technology service provider that hosts events for startup minds in Silicon Valley and beyond. The same BRINK client story mentions 6-7 Lohika events per month. This is a secondary account written by an agency about its client, so treat it as background colour on the company’s community activity rather than a precise record. It also points away from games: the activity described is aimed at startups and technology teams.
The Capgemini change
Both the LinkedIn page and the BRINK case study state that Lohika is part of Capgemini, the case study describing it as acquired. If you are comparing older articles about Lohika with newer ones, expect the ownership description to differ. A credit that reads Lohika on an older release and one that reads Capgemini on later material may refer to the same organisation at different points in its history, but only the developer listing can confirm which applies to a given game.
Mobile skills and what they imply
Lohika lists Mobile Application Development, QA and R&D among its specialties. For a mobile puzzle title, those are the disciplines that matter most after design: building the app for phones and tablets, testing it across devices, and researching how the mechanics behave. Machineers is a physics-based puzzle game, and these skills are relevant to that kind of project.
Relevance is not attribution, though. A shared skill set shows that a company could plausibly contribute to a mobile game. It does not show that it did. Keep the two ideas apart when you write or share anything about who built a game.
Confirming who made a game
The most reliable way to answer who made Machineers, or any mobile game, is to read the developer line on the store listing and then follow it to the developer’s own page. The company profile you find through a search is the second step, not the first. This order protects you from joining two similarly named entities that are not the same.
- Start at the store listing. The App Store and Google Play pages show the name the publisher registered for that release, which is the name that matters for credit.
- Follow the developer link. From the listing you can open the developer’s other titles and any website they provide.
- Compare with the company profile. Check headquarters, industry and website against what the listing shows. A mismatch means the names may belong to different organisations.
- Prefer the company’s own words. Official sites and company pages outrank third-party summaries when the two disagree.
For the game side of the story, the page on what is machineers game explains the puzzle itself, and the article on how was machineers made covers its development.
A caution about the registry route
Company registries are a good way to confirm a legal entity, but only if the record you open belongs to the right company. A registry page for a similarly named games business is not evidence about Lohika. Always check the company number, name and registered address on the record against the developer you are researching, and discard the record if any of them differ.
How to use this profile
If you are a player, the useful takeaway is modest: the Lohika name connects to a software development company with a San Mateo headquarters, a mobile engineering focus and Capgemini ownership. If you are a writer or researcher, the lesson is to separate three things that often get blended: the company, the studio credit and the individual game. Each needs its own evidence.
If you are choosing what to read next, go to the game pages for how Machineers plays and the development story. Come back to the company profile only when you need to verify a name or an ownership statement.
Frequently asked questions
Is Lohika a games studio?
Its LinkedIn page describes it as a software development company, with specialties in mobile development, QA and R&D, not as a games studio.
Where is Lohika headquartered?
LinkedIn lists San Mateo, California, at 1825 S Grant St #400. That is the company’s listed headquarters, not necessarily where each project is built.
Who owns Lohika now?
The company’s own page says it is now part of Capgemini, and an agency case study describes it as acquired by Capgemini.
How do I check who published a specific game?
Open the game’s store listing, read the developer name, and follow it to the developer’s own page before comparing it with any company profile.