【Factorio】Space platform design and operation: 3 patterns (translated)

In Factorio: Space Age, the difference in space platforms comes not from the moment they're built, but from whether they keep running properly. This guide breaks down setup into 3 stages—docked minimum config, first voyage, and mass supply—and tackles the auto-request issues, full-load conditions, ammo depletion, and hull width-speed relationships that tend to trip up new players.

For those heading to space for the first time, or who keep launching but run out of supplies mid-flight, this guide focuses on reproducible design steps. Space platforms aren't about making them bigger; they're about breaking down necessary functions into stages and loading them incrementally for stability.

What is a Space Platform in Factorio? Context and target version

Overview of elements added in Space Age

The space platform is a core feature of Space Age that fundamentally changes the "once you launch a rocket, you're done" feeling of vanilla Factorio. Space Age is a paid DLC released October 21, 2024, and alongside space platforms, it introduces four new planets and a restructured tech tree designed around reaching them. As you can see in 'Space Age - Factorio Wiki' and 'Upcoming features - Factorio Wiki', DLC shifts the production and logistics mindset significantly after rocket launch.

A space platform isn't just an orbital outpost. It functions as a factory while also serving as transport to other planets. Your first platform starts by launching a starter pack via rocket, beginning with a hub and minimal floor. From there, you expand the floor and add power, production, defense, and propulsion. Unlike ground factories, floor expansion and removal become operational constraints, and losing the hub means losing the entire platform—a total-loss risk that shapes design significantly. The exact mechanics of floor removal and costs are version-dependent, so it's recommended to confirm current specs in Factoriopedia or the official Wiki.

Even I initially carried the "rocket launch = end credits" mentality from vanilla, delaying my engagement with space mechanics. But in Space Age, that's actually the entry point. An initial platform docked in Nauvis orbit starts collecting asteroids for resources and running as a space science production base. In other words, space is better understood as a new logistics layer and new factory layer before focusing on its visual spectacle.

Space Age

wiki.factorio.com

Target audience and prerequisites for this article

This page is primarily aimed at players with vanilla rocket experience who are touching space platforms for the first time in Space Age. It's beginner-to-intermediate in tone, covering exactly the stage where "I built a platform but operation isn't stable" or "ground supply and orbital demand don't mesh."

The target version is Factorio 2.0 + Space Age DLC. This matters a lot—carrying vanilla rocket and old space science assumptions straight in will create misalignment from the start. For example, in Space Age, space platforms become logistics hubs and production sites simultaneously, with research paths designed around planetary expansion. Beacon efficiency scaling also changed in 2.0, so the old "just stack them" logic is error-prone.

Terminology

Let's nail down a few easy-to-confuse terms before we proceed.

A space platform is a Space Age-exclusive orbital outpost. You expand floor around a hub and outfit it with equipment to create a factory. You can also set a destination and move, making it both a docked production base and an interplanetary transport. The feel is somewhere between a ground base and a train, with destination UI similar to a schedule.

A platform hub is the core building of a space platform. It's the resource exchange point and construction origin; losing it makes the entire platform unusable. It's like a command center and central warehouse combined—a priority defensive target.

Platform floor is the foundation for placing equipment in space. It feels like landfill, but design freedom isn't the same. It's awkward to plan around large cuts later, and rework is common. Exact removal methods and costs vary by version—check Factoriopedia first.

An asteroid collector gathers nearby asteroids. Space has no ore veins; flying objects become resource entry points. Collected items feed into processing equipment, forming the basis of space production.

A crusher converts collected asteroids into resources. Unlike ground ore flowing straight from mining, space requires "collect then crush," a key workflow difference.

A space science pack is crucial for Space Age progression. It shares a name with vanilla's rocket-based version, but in Space Age it's often a production chain on the platform itself—easy to conflate, but important to separate.

Auto-request is the platform asking the ground for supplies via rocket. But ground-side silos need auto-request enabled, the logistics network needs stock, and the origin planet must be specified—several joint conditions that cause hang-ups.

A cargo landing pad is the orbital supply receipt hub. It acts like a request chest but takes only 1 stack per delivery. Uneven delivery pacing is a common bottleneck.

With terminology sorted, we'll next decompose space platforms into "stationary operation" and "traveling delivery" stages.

Setting up initial space platforms: minimum configuration

Launching the starter pack and initial placement

The goal at first is a platform that runs docked, not a flying ship. A space platform starts with a starter pack launched via rocket, initially just hub and minimal floor—closer to "bare-bones machinery room in orbit" than a ground base extension.

The key is not to carelessly expand the initial floor. As mentioned, you can add platform floor later, but casual rework doesn't work like ground digging and rewiring. Your first dozen tiles set the stage for later layout freedom. I initially spread wide before placing collectors and crushers, causing transport tangles and needing a rebuild. Keep receiving and production close to the hub, then extend collectors outward.

Layout is simple: center the hub and connect power, collection, crushing, and science production in the shortest path. Propulsion and heavy defense are optional for docked platforms. Nauvis orbit is forgiving for startup; the goal is asteroid-to-science-pack there.

地上からの受け取りも、最初から分業しておくと安定します。
カーゴ降着パッドは一度に1スタックずつしか受け取れません。
1台で全部受けようとすると、床材待ちのあとに蓄電池待ち、そのあとインサータ待ちという形で順番待ちが発生します。
自分もこれで初回の立ち上げが止まりましたが、要求品目ごとにパッドを分けたら一気に流れがよくなりました。
停泊型の最小構成では、建材用と消耗品用を分けるだけでも効果が大きいです。

Ground receiving improves with early task division. Per 'Cargo landing pad - Factorio Wiki', pads take only 1 stack at a time. Feeding everything into one pad creates queueing: waiting for floor, then battery, then inserter. Splitting by purpose—construction materials vs. consumables—helps flow significantly. One pad made the difference for my initial setup.

Cargo landing pad - Factorio Wiki

wiki.factorio.com

Power security: solar and accumulator placement

Initial platform power works best as solar and accumulator self-sufficiency. Avoiding fuel power keeps logistics light, suiting docked startup. Solar panels max at 60 kW daytime, averaging 42 kW, with zero at night. Accumulators hold 5 MJ each, charging/discharging at max 300 kW. The day-accumulate, night-discharge logic mirrors ground power.

Numbers clarify placement. For example, to maintain ~500 kW continuously, you'd need roughly 12 solar panels (42 kW average each) as a ballpark. Pair with accumulators in roughly a 25:21 ratio—~10 units works for minimal platform load. One accumulator hits 300 kW momentarily but only holds 5 MJ, so brief and sustained output are separate concerns.

Place solar on perimeter, accumulators hub-side for future expansion. Space platforms don't need power pole density like ground factories; floor usage is design quality. Reserve a power row early, then stretch production lines without replumbing the grid. Scattering accumulators centrally breaks layout on expansion.

Stable power on Nauvis means production unlocks faster than moving or fighting. Collectors and crushers halt when power dips, cutting resource intake instantly. Solar addition here isn't insurance—it's production capacity.

Asteroid collector-to-crusher loop

Once power flows, create a tight collector-to-crusher loop. Space mines asteroids instead of ore veins, so collectors alone or crushers alone won't work. What matters is unbroken flow from collection to crushing to next stage.

Place collectors on outer edges, crushers just inboard—minimizing distance saves initial floor (and rocket payload). The trap is lacking downstream design. Crushers need a destination or they jam, halting collectors immediately. I once saw collectors "working" but resources flat, revealing the backup actually choked production.

Simplicity wins: collector → crusher → buffer or next step in one thread. At startup, one unbroken loop beats perfectly balanced shortfall later.

Minimum space science line

Your initial checkpoint: self-sustaining space science packs, however thin. Space Age lets you produce science docked, making this the natural completion milestone before planetary travel. Chain: collectors → crushers → smelting if needed → assemblers → science packs.

Here, unbroken feed beats high throughput. This isn't a mega-research base; one supplier holding is worth more than parallel assemblers starving. Shortfall materials come via cargo pad, but 1-stack limits mean splitting by product stabilizes startup. I cut pad count with everything mixed; that bottleneck was obvious once I split by category.

Layout: assembler and output near hub, collectors and crushers on perimeter, power mid-range or backing. Incoming supplies stay near hub, orbital resources flow inbound. Avoid chasing exact ratios initially; just get science flowing stably. This independent minimum rig transfers cleanly to supply ships later.

Once science packs flow, your base shifts from "placed foothold" to "running factory." You're ready for auto-supply and ship design.

Design philosophy: hub-centered, tall layout, role division

Hub protection and redundancy

Space platforms' first fixed principle: hub survival beats production elegance. Ground factories lose subsystems; lose an orbital hub and you lose the entire platform—total loss. Design for hub defense before outer-ring beauty.

Three guard principles: shielding, distance, redundancy. Shielding places replaceable structures and floor around the hub, preventing straight-line targeting. Distance keeps damage-prone zones (collectors, crushers, ammo) off the hub, avoiding splash cascades. Redundancy means no single path to critical functions—hub arrival isn't one-directional.

Floor handling drives this home. Platforms expand but don't easily excavate later. Cramming the center densely limits future adjustments. Protect the hub perimeter by keeping room for future paths, especially supply lines and fuel runs. I once densely packed the center, then found supply and fuel routes forced around the hub awkwardly, defeating defense.

Avoid maxing all four sides early; ample space around the hub is defensive value.

Why tall is superior

Wide layouts seem easier—collectors and power stack horizontally. Operationally, they falter on speed, piping, and defense.

Width kills efficiency and compartmentalization. Ship roles blur when wide: where does the collection zone end and the engine section start? This vagueness spreads fuel and ammo pipes across the frame, making centerlines cramped and fragile.

Critically, thrusters can't build behind themselves, forcing a front-production, rear-engine split—naturally calling for a tall ship. Tall ships naturally section: front (collection + defense + resupply), middle (hub + production), rear (fuel + thrusters). Responsibility zones clarify, damage readability improves. Piping runs cleaner front-to-rear than zigzagging horizontally.

Floor expansion synergizes with tall. Central spine, side branches, rear engine settled early saves adjustments. Adding width later eats routes you'll need. Horizontal expansion consumes future degrees of freedom fast.

Upcoming features

wiki.factorio.com

Design: docked vs. traveling platforms

A crucial separation: docked and traveling platforms aren't the same ship.

Docked platforms skip propulsion (almost), prioritizing safety and production stability. The science base from prior sections is pure docked work—no fuel pipes or thruster zones to waste floor.

Traveling platforms must propel, defend, resupply, and survive mid-flight hits. Thrust-to-speed ratios and continuous ammo flow dominate. A docked design extended for travel often looks compact but performs poorly—weak thrusters, unbalanced defense, stretched fuel lines, thin front armor.

Different platforms have different spare-room values. Docked platforms prize production-growth space; travelers prize ammo flow, fuel routing, and forward protection bands. Cramming both into one frame courts disaster. Splitting the load—docked for raw production, traveling for cargo hauling—stabilizes both designs and makes operation tighter overall.

Thrust and speed: thruster count, hull width, and fuel supply thinking

Hull width and thruster band layout

When a traveling platform underperforms, hull width vs. thruster band is the first check. Easy floor placement tempts wide designs initially, but runtime speed depends on whether you can fit thrusters cleanly. I built wide and expected a single rear row of thrusters to suffice, but speed lagged visibly. Switching to a narrower frame transformed performance.

Broad hulls force sprawling thruster bands, harming efficiency. Practical experience suggests width above ~30 becomes noticeably bad, though exact thresholds vary. Test narrow and tall first, then tune.

"Short and thick" thruster bands beat "long and thin." A compact, high-density rear thruster block is superior to a row strung across the stern. This unifies piping, clarifies the propulsion block, and synergizes with tall layouts—front production, rear thrusters.

Wide layouts feel loadable but underdeliver in flight. Think of propulsion as a constraint, not afterthought. Sufficient thrusters are built first; cargo fills the leftover space, not vice versa.

Fuel and oxidizer supply ratios

Beyond "can we generate fuel," the real question is how do we distribute it to thrusters? I initially assumed feeding one thruster concentratedly was strongest; actually, throughput doesn't scale linearly with fill level.

Thrusters reach 200% at 120/s fuel flow per the space logistics details, with lower-fill regimes more efficient for generating thrust. One full thruster underperforms; two half-full thrusters overproduce total thrust. Example: one chemistry plant yields 37.5/s fuel/oxidizer. Feeding one thruster → ~52% thrust. Split across two → 29% thrust each, totaling ~58%—higher total output.

This efficiency pattern means distributing 37.5/s across four thrusters balances well. Uneven draw still leaves headroom, phased growth stays manageable. Chase efficiency band, not theoretical peaks. Practical experience shows this prevents fuel starvation and acceleration hangs more reliably than maxing one unit.

Speed control: pumps and circuitry for metered output

Bare propulsion isn't stable. Controlled fuel delivery is critical. Open throttle wastes fuel on empty stretches; you risk coasting unpowered to destination.

Pump + circuit network ON/OFF control works well. Use fuel tank level or waypoint flags to gate fuel flow. Example: cut cruising thrust if fuel drops below threshold; shift to decel-heavy thrusters near destination. Stage output modes—full, cruise, economy, idle—rather than continuous speed ramping. Each mode opens different pump branches.

Pumps max at 1200 units/second flow, so bottleneck is logic condition, not pump power. Adding control stretches range without boosting production.

Efficiency design sidesteps the non-linear thrust curve. Spread supply, meter output, and build margins into fuel systems. Early interplanetary trips value "complete round trip without crash" over top speed.

Logistics: auto-request and launching without stalling

Enabling auto-request and full-load conditions

The most frequent stall: requests exist but rockets never launch. Root cause: ground-side network lacks full-load-condition inventory despite platform requests. Auto-request isn't like request chests; it demands accumulated supply meeting launch volume before the logistics network moves anything.

Critical mindset shift: requests alone don't trigger shipments. Ground-side buffers must hold surplus stock. Predictable items like ore and belt refill smoothly, but building materials, ammo, and sundries scatter, under-filling shipments. You need persistent ground-side buffers to accumulate launch-ready quantities.

Per 'Space network' and its detailed spec, requests and ground supply both matter—neither alone works. When rockets stay silent, check ground network inventory before launch settings.

Splitting small-quantity materials and minimum shipment sizes

Another trap: low-quantity items don't auto-ship. Platforms needing only a handful of construction parts or backup gear sit requesting while ground inventory falls short of minimum shipment volume. Auto-request struggles with small orders.

This hurdle is insidious: main flow looks fine while small items silently starve. At expansion or repair windows, you suddenly notice. The cure: split small goods into manual launch or circuit-gated micro-batches. Let bulk items go auto; manage small supplies separately. Packaging large and small identically fails—auto thrives on scale, falters on scarcity.

Specifying supply planet and orbital drop slots

Auto-requests also need origin planet designation. Requesting without specifying source creates ambiguity; multiple planets confuse which network supplies where.

Organize supplies by source. A single "iron" request mixing Planet A and B sources jumbles responsibility. Split by supply endpoint—one request per origin planet. Orbital drop slots consolidate ground logistics but don't replace this clarity. Buffer capacity and split paths work together for clean multi-planet supply chains.

Using cargo landing pads strategically

Ground reception hits a snag: pads accept 1 stack at a time. Mixed shipments queue badly. A fast-rotating ammo supply and rarely-needed building parts in the same lane create wait lines, where the buildings actually stall (not ammo).

Split pad placement by category: construction, ammo, bulk material each get zones. Rushing multiple goods into one location looks tidy but kills delivery speed for items that matter. Segregation lets quick items flow without small-item delays. I initially thought central receiving was elegant; operation proved otherwise. Item-clearing speed beats layout tidiness.

Space resupply works when requests, ground supply, source designation, and pad scheduling align. Bottlenecks hide in spec boundaries: full-load conditions, minimums, source designation, 1-stack limits. Separate these concerns and debugging becomes simple.

Defence and upkeep: asteroid hazards, ammo, repair reality

Nauvis orbit vs. inter-planetary threat levels

Orbital defense intensity shifts with location and travel zone. Nauvis orbit is relatively safe; minimal platforms with light defenses operate there. Other orbits and inter-planetary routes expose platforms to continuous asteroid pressure, eating hull, transport, power randomly, chain-failing production. Docked platforms stay whole; traveling platforms bleed externals immediately.

Underestimating this gap courts disaster. Tightly-specced traveling platforms fail spectacularly: one severed ammo belt stops turrets, exposing the hull to cascading damage. Repair-wise, structural survival during combat matters more than hitting hard. I learned when a few minutes of defenselessness cratered my front hull. Strategy flipped: keep ammo flowing and patch the holes trumps raw firepower.

Scaling a docked design to travel is risky. Traveling ships need built-in defense equipment and repair stockpile. Nauvis "minimum" isn't minimal elsewhere.

Ammunition and turret selection

Early defense leans gun turret-heavy. Community wisdom holds asteroids resist lasers, flame, and electricity—energy weapons seem potent but cost more than they return. Charring one asteroid while absorbing hits wastes time and power.

Yellow ammo self-sufficiency works. Reddit ship-building threads repeatedly emphasize never running dry over raw power. Onboard ammo production—even modest—keeps turrets firing indefinitely. Continuous supply beats burst damage. Double ammo-belt routing, with redundant buffers, means losing one line doesn't halt fire.

Turret placement: front density is standard, but important systems (ammo, power, collectors) need flanking coverage. Breakthrough prevention matters more than totals interception.

Repair kits, spare parts, and baseline supplies

Repair complacency is dangerous. Latenight repair isn't guaranteed during combat. Community consensus: repairs lag real-world pressure—you can't out-heal incoming fire. Assume breaches will happen.

Pack spares: decking, equipment, belts, power supplies, wiring, ample repair kits. Decking especially—a missing floor section halts rebuilding (you can't place equipment mid-air). Carrying spares isn't comfort; it's structural restore capability.

Self-experienced: cutting repair stock to fit cargo backfired. Far expeditions should prioritize stop-gap repair materials—patch the hole, restore power, resume supply. Minor fixes under fire beat perfect repairs after power loss.

Design pattern comparison by purpose

Docked: space science production

Non-traveling docked platforms focus purely on asteroid processing and science output. No moving means minimal propulsion, light defense, easier design. Failure factors collapse to shortages of building material and power.

Docked simplicity wins here. Power alone is decipherable: 24 solar panels (~42 kW average) feed ~1 MW draw. Accumulators: 5 MJ storage, 300 kW max flow, 1 MW runtime = ~5 units. Collection, crushing, assembly, export—all straightforward. This is where I benchmarked space-platform thinking before expanding to ships. Design difficulty stays low, letting you focus on production ratios and flow stability first.

Layout: docked designs tolerate width. Horizontal spreading of collection, crushing, science, power is feasible here. Yet future ship conversion favors rear-extensible tall designs—early habit-forming pays dividends.

Generalist transport: early 3-planet routes

Balanced ammo, fuel, and light cargo in one ship—the first real travel-platform. It pursues survival over optimal role specialization, avoiding role-fragmentation complexity while maintaining core viability.

Critical for this class: survivability precedes payload. Padding cargo space tempts; the real bottleneck is fuel, ammo, and repair margin. Early transport losses stem from ammo starvation and fuel shortage, not load capacity. Skimp there and you fail before arriving.

Tall design becomes strongly advantageous here. Clean sectioning (front defense + collection, middle logistics + assembly, rear fuel + thrusters) aligns naturally. Horizontal spreading creates speed and piping headaches fast.

Resupply integration is forgiving: auto-request + manual launch covers most needs without circuit logic. Few supply types make simple splits work. Reference planetary-shipping guides for deeper logistics tuning.

Specialist fleets: mid-game division of labor

Multiple ships by role becomes viable once you've done several round trips. Ammo carriers, fuel tankers, material ships—each handling one job steadily beats one ship juggling everything. Separation clarifies operation. Ammo shortage doesn't drag down fuel delivery; material delay doesn't starve defense.

Advantage: accident scope narrows. A single-ship failure cascades; multi-ship failure isolates to one task. Coordination gains stability. I switched mid-game and immediately felt accident rates drop—single-point failures vanished.

Downsides: build cost and complexity rise. Design deteriorates faster with scale. Overambitious specialist designs fail worse than generalist overload.

Tall compartmentalization sharpens here: front (defense + collection) remains independent, rear (fuel + engines) stays specialized, middle (hub + production) flexibly repurposed. Cost realism demands realistic role division rather than monolithic ships.

Common failures and fixes

Auto-request stalls

Before troubleshooting launch equipment, verify ground-side full-load inventory actually exists. Requests alone don't trigger anything. Ground buffers must accumulate launch-minimum quantities.

Check minimum shipment size. Tight constraints on small goods prevent micro-shipments. Use separate manual launch or circuit-gated batches for consumables.

Verify origin planet designated and sourced from the intended network. Ambiguous supply confuses multi-planet ops.

Prioritize: inventory check, then minimum-size review, then origin inspection.

Ammunition and fuel shortage

Supply stalls manifest as ammo drought or fuel depletion. Both show as mid-journey collapses, so redundant ammo lines and continuous supply matter.

Mix current production + ground stockpile. Pure imports fail when resupply lags. Onboard generation—even minimal—plugs gaps.

Fuel shortages follow similar logic. Continuous tank draw needs dual supply paths and circuit-gated alerts. Alert thresholds catch problems before total loss.

Throttle control (limiting cruise draw) extends operational range significantly, often more than adding fuel capacity.

Slow speed and width

Slow ships usually reflect hull width, not thruster underdeal. Horizontal sprawl looks spacious but kills acceleration. Pare hull width, condense rear thrusters, and speed improves noticeably.

Change focus from "more engines" to tighter layout. Vertical expansion over horizontal expands utility more predictably.

Over-supply and hoarding

Abundant supplies suggest minimum-shipment or upper-inventory misalignment. Auto-dispatch flooding buffers wastes logistics.

Lower minimum quantities for small goods. Lean upper-inventory caps tighter.

Combine auto-request with circuit-gated cap logic. Requests flow only when under threshold. This prevents surplus accumulation while allowing urgency-responsive top-ups.

Missing return capacity

A silent killer: forgetting return-trip supplies. Reaching destination with empty tanks, no repair stock, no floor material leaves you stranded.

Pack standing return kits: fuel, oxidizer, spare decking, repair supplies, thruster blocks. Normalize via blueprint—never renegotiate.

Traveling platforms must account for round-trip autonomy, not just outbound arrival.

Next steps: per-planet optimization and quality/beacon leverage

Asteroid distribution per planet and harvest efficiency

Mid-game stability demands planet-specific gathering configs. Each world's asteroid profile differs; optimal collector angle, density, defense cover, and crusher placement vary by location.

Verify current-planet asteroid trends in Factoriopedia before finalizing ship specs. Dense asteroid zones benefit from narrow, focused collection. Sparse zones tolerate generalist layouts but demand higher ammo consumption and defense margin.

Defense planning mirrors this. High-density routes require careful front sizing—spreading wide loses manageability while boosting asteroid exposure. Narrow defenses with concentrated firepower stabilize better.

Quality synergy with space platforms

Quality (rarity) shines in space more than ground. Orbital space, supply throughput, and defense margin are perpetually stretched. Per-unit performance gains compress ship designs visibly.

Value rises in critical equipment: thrusters, defense, energy. High-quality specialized components let you shrink overall hull, reducing resupply burden and maintenance. Space doesn't reward "solve by scaling up"—it rewards density.

Tier quality spending: propulsion + defense + supply core first, spreadsheet luxury items later. Quality is a logistics-compression tool, not indulgence.

Beacon efficiency post-2.0 and Space Age

Beacons changed radically. Efficiency scales as sqrt(count), plateauing at 8 units. Vanilla "stack as many as possible" strategy now wastes space on diminishing returns.

Orbit's high real-estate cost favors 8-beacon clusters or fewer. Beyond 8, adding beacons eats floor and power without proportional gain. Modules, power wiring, and defense perimeter all scale with beacon proliferation.

Target 8-beacon pairs around assemblers, then grow assembler count if needed. Compute throughput + space + resupply holistically before reflexively adding beacons.

Specialist supply ships and role distribution

Once transport volume climbs, single-ship generalism breaks. Splitting by function (ammo vessel, fuel tanker, materiel ship) clarifies bottlenecks and stabilizes rotation.

Each material's urgency differs: ammo failure is instant catastrophe, building materials allow slight delays, fuel determines endurance. Mixed shipping muddies priorities; segregated channels let fast items avoid slow-item queueing.

Specialist ships needn't be massive—tweak balanced templates into fixed-function variants. Multi-planet operation increasingly benefits from role-dedicated small fleets versus a jack-of-all-trades flagship.

As you expand to 4+ planets, role division compresses dock logistics and clarifies resupply accountability. Purpose-built routing outweighs generalist flexibility.

Summary and next moves

Space platform design evolves through tiers. Begin with docked Nauvis production—learn flow, power, and collection stability there. Graduate to balanced travel platforms once production steadies. Finally, split into specialist fleets once multi-planet rotation sustains itself.

Each tier teaches distinct lessons. Docked teaches fundamentals without propulsion noise. Balanced travel reveals thrust, ammo, and fuel depth. Specialists demand logistics finesse.

The single meta insight: stability beats optimization. A slightly inefficient platform that completes cycles beats a maxed-spec wreck. Over-specced designs fail under stress; conservative designs flex under load.

From here: try the Nauvis docked platform first. Build science output reliably, then attempt your first 3-planet route in a balanced transport. Once confident, tackle specialist ship coordination. Each milestone is a platform's steady improvement—a game-spanning project that rewards iterative refinement over theoretical perfection.