Mandragora is the developer
The Steam store places Mandragora in the Developer field for both the full game and the separate Demo. The Game.Press record repeats that credit, giving independent consistency across the publisher's distribution materials. Use Mandragora when a database, article, video description, or fact box asks who developed ReStory.
Developer means the studio credited with making the game. It does not automatically identify every programmer, artist, designer, writer, producer, composer, tester, contractor, or localization partner who contributed. Individual names require the game credits or a separate official statement.
The developer credit is repeated on Steam and the official press resource, so it does not depend on a search summary or third-party database. Those sources support the studio name but not unsupported additions about ownership, location, size, or internal organization. Keep the public answer limited to the role that the official credits actually state.
tinyBuild is the publisher
Steam and Game.Press identify tinyBuild as publisher. That role appears on the store listing, official announcements, Demo page, and press materials. It should not be swapped with the developer role even though both names appear together frequently.
Publisher activity visible in the approved sources includes the Steam listing, announcements, launch information, press distribution, community links, and optional product pages. These examples do not establish every contractual or operational responsibility between the companies. Private agreements and revenue terms remain outside the evidence.
Support questions can depend on their subject. Store and account issues may begin with Steam, game bugs may use official ReStory community channels, press assets use the press resource, and corporate questions belong with the relevant company. A correct credit helps route the question without assuming one organization handles everything.
Connection to I Am Future
Official ReStory copy describes the game as coming from the creators of I Am Future. That supports mentioning Mandragora's prior work when explaining the studio context. It does not prove that the exact same individuals, tools, budget, or production structure moved unchanged between projects.
The connection is useful because both official descriptions emphasize relaxed systems and management, while ReStory focuses specifically on an electronics shop, nostalgic devices, and customer stories. Comparing high-level themes is reasonable when it is presented as context. Claiming shared code, an engine, universe, or sequel relationship would require additional evidence.
Use the official wording rather than constructing a complete studio history from memory. The reviewed source set is designed around ReStory and does not list every Mandragora release or project. A broader catalogue should come from the studio's current official site.
What the team publicly delivered
Official game material describes detailed device disassembly, cleaning, fault replacement, reassembly, finances, parts sourcing, in-person and online orders, customer choices, and multiple endings. It also highlights a mid-2000s Tokyo setting and officially licensed Atari consoles. Those are verifiable outputs associated with the credited developer and publisher.
The announcement history shows an initial playtest, a June 15 Demo, an August 6 full release, and rapid post-launch patches. The team collected feedback, adjusted performance and gameplay, and publicly documented fixes for saves, achievements, firmware, inventory, ultrawide displays, sonic-bath states, screws, and named devices. This timeline is more concrete than a vague claim that the studio listens to players.
Official August news also says the team was working on a free content update and a longer-term roadmap. It does not publish every planned feature or date in the reviewed text. Specific future gadgets, DLC, platforms, and schedules remain To be confirmed unless named in a newer post.
Credits that remain unconfirmed here
The approved sources do not name a creative director, lead programmer, art director, narrative lead, producer, or full voice cast. They also do not state the studio's headcount, development budget, office location, ownership structure, or funding agreement. This page will not invent those details from company-name associations.
The game's engine is likewise not named in the official pages reviewed for this project. Community use of BepInEx or MelonLoader is not proof of a specific engine because those loaders and frameworks can be adapted across environments. Engine attribution remains To be confirmed.
Outsourced support work should be attributed only when a source identifies it. The August 11 AI-related statement mentions an external artist for separate Steam community backgrounds, but that does not map the full art team or game-production pipeline. Do not generalize one contractor reference into the studio's complete staffing model.
Official links and verification
Use Mandragora's official site for current studio information and the official Steam page for product credits. The Steam announcement feed supplies dated development and patch context, while the press resource supplies structured media fields. Together they support the developer and publisher answer without relying on a competitor guide.
When copying credits, preserve spelling and role. Check whether a future console, mobile, soundtrack, artbook, or regional edition lists additional companies before extending the base-game credit. A partner on one product or territory should not automatically be described as developer of the entire game.
Music has a specific public credit in the August 13 announcement. It says the soundtrack contains tracks composed by M.Harvey Bee exclusively for the game. That named credit can be used for the soundtrack while avoiding assumptions about every sound designer or audio contributor.
Licensed Atari content signals an external rights relationship, but it does not turn Atari into the game's developer or publisher. Credit the license only in the context official copy provides. Other fictional or inspired brands should not be assigned real corporate partners without a source.
Store databases sometimes merge studios with similar names or carry credits forward from another title. Verify ReStory itself rather than relying on a company profile assembled automatically. The product record and in-game credits are stronger evidence than an unsourced biography.
Use past tense carefully when describing launch work and present tense only for current public roles. A credit proves contribution to the released product, not ongoing employment. Dated wording prevents a historical fact from becoming an unsupported staffing claim.
Link the product credit when space permits. Readers can verify the role directly. That is stronger than repeating an uncited studio summary.
The concise verified credit remains Mandragora developed ReStory and tinyBuild published it. Individual contributors and private studio details are To be confirmed from fuller credits or official disclosures. That boundary keeps a simple factual question from becoming an invented company profile.