Ostranauts is easier to approach as a chain of practical decisions than as a list of universal builds. You are trying to keep a ship and its people functional while turning salvage, jobs, and repairs into enough money for the next decision. The official Steam description supports that broad loop: it names derelict salvage, ship upgrades, debt, fuel, air, food, character backgrounds, traits, skills, crew needs, ship construction, Newtonian flight, and docking. This hub turns those facts into a reading route without presenting an untested number as a rule.
What the current scope means
The target of this wiki is the Steam base game, AppID 1022980, rather than the Ostranauts Soundtrack product or a generic space-sim guide. The store page identifies Blue Bottle Games as developer and Kitfox Games as publisher. It also lists single-player, Steam achievements, Steam Cloud, Family Sharing, English interface, and 31 achievements. Those are useful identity checks, but they do not prove that every old guide still matches the 1.0 interface.
The game released into its 1.0 era on August 3, 2026. The official news archive then listed the v1.0.0.9 notice on August 10, 2026. When an article says “current,” it therefore means the checked date in its frontmatter and the branch named in its scope, not a promise that a later patch cannot change the result. Early Access instructions are valuable historical clues, but they must be marked as historical when a menu, achievement, or save behavior may have changed.
A sensible first reading route
Start with the Beginner guide before copying a ship layout. It explains how to inspect the initial situation, distinguish an immediate life-support concern from a longer-term money problem, and write down a recovery point before taking a risky job. Then read Ships for the language of rooms, functional parts, power, pressure, fuel, and docking. These terms make later salvage instructions easier to evaluate because you can ask what a component changes instead of treating every part as an upgrade.
Next, read Salvage to understand why a derelict is an opportunity and a hazard at the same time. A valuable part is only useful if you can reach it, survive the work, move it, and still get home. Systems covers life support and save branches, while Crew explains why food, oxygen, water, intimacy, and security are not flavor text when the official description treats them as AI needs. Modding belongs after a clean baseline save so that a Workshop change does not become indistinguishable from a vanilla bug.
How to use a page safely
Every detailed page should separate what the official store or announcement establishes from what the player must inspect in the current build. A statement such as “the game supports Steam Workshop” is first-party evidence. A statement such as “this part always consumes exactly this amount” needs a current tooltip, data file, or controlled test. If a page cannot provide that evidence, it should state the limit and tell the reader what to check rather than filling the gap with a confident number.
For controls, use the keybinding menu as the final authority because keyboard layouts, remaps, and future patches can change the comfortable answer. For save compatibility, keep a copy of a clean save before switching to a branch or loading a modded state. For platform questions, treat the Windows system requirements on the store page as the documented boundary and do not turn a community report into a native Linux or Steam Deck guarantee.
The decisions that matter early
Your first meaningful choice is usually not “what is the best ship?” but “which failure can I afford to investigate?” A ship with a promising room may still be a poor first target if its route costs more fuel than the likely return. A crew member with a useful skill still needs a workable air, food, water, and security plan. A job that pays well may expose debt, travel, or repair risk that a new save cannot absorb.
Keep a short log of the save date, branch, major purchase, and any mod. This is more valuable than a copied checklist because it tells you which facts belong to your own run. If a guide disagrees with your screen, record the build label and the exact menu or tooltip. That turns a vague “the guide is wrong” report into a useful maintenance signal.
Where this hub should not overpromise
The official pages do not provide a complete component database, full achievement conditions, exact oxygen thresholds, universal docking speeds, guaranteed crew schedules, or a complete Workshop compatibility matrix. Those are good future pages only when their evidence can be dated. They are not safe to invent from the store description. The same restraint applies to prices, debt totals, job payouts, event timing, and the result of every Ceres Affair branch.
An article can still be useful without a hidden database. It can explain what screen to open, what observation to make, what risk to isolate, and how to recover after an unsafe choice. That is the standard used by this site: concrete enough to act on, narrow enough to remain honest when Ostranauts changes.
Official entry points
The canonical product identity is the Steam store page at https://store.steampowered.com/app/1022980/Ostranauts/ . The 1.0 announcement is at https://store.steampowered.com/news/app/1022980/view/507098342507576552 and the v1.0.0.9 announcement is at https://store.steampowered.com/news/app/1022980/view/507098342507576554 . Check those pages for release scope and update language before treating a dated guide as current. The linked articles in this hub add player procedure, not a replacement for the official product record.
Sources
Official Steam Store and Steam News pages above, checked 2026-08-11 UTC. The site is an independent fan guide and is not affiliated with Blue Bottle Games, Kitfox Games, or Valve.
Recommended guides
Choose the guide that matches what you want to do next.
All Guides guides
1 focused guides with steps, checks, and current caveats.