Understanding Gateways

Tuesday, March 3, 2026

Understanding Gateway Mechanics

The AGC’s open nature encourages active discussion and many ideas. However, gateway mechanics are complex, and it’s easy for conversations to drift away from the reality of those mechanics. When evaluating gateway placement, keep the following principles in mind.

Traffic Volume Is Critical

It’s natural to want a gateway that serves your niche system. It may benefit you directly, and you may even know several players there.

However, a pair of gates costs 300k per week in upkeep. To justify that cost, you need roughly 100 trips per week through that gate. Even a large co-op of 20 players — which is substantial — only gets you about one-third of the way to viability.

Instead of anecdotal demand, examine workforce population data. As a rough benchmark, a planet with 100k population may represent a reasonable starting point for sustained traffic.

The Value of a Gate: Parsecs Saved

A gateway must significantly reduce effective travel distance.

Consider Roshar to EW-238.

  • Via FTL: 46.6 parsecs over 7 jumps
  • Via Gate: 16.91 parsecs

Your speed through a gate is 3 pc/hr. Your typical FTL speed will be higher, perhaps 3.5 to 4.5 pc/hr. Here we’ve got solid gate, but a modest distance reduction can still result in a slower trip overall.

64% distance saved is a solid improvement. A gate saving only 14% will probably always be worse than avoiding the gate.

As a rule of thumb:

Less than ~25% distance savings is not worth considering.

The OOG map now calculates distance saved.

The STL Flight Time Penalty

Additionally, if you are not starting directly on the planet with the gate, you must account for STL travel time to reach it.

A gateway makes sense only if:

$$d_{\text{FTL}} \cdot v_{\text{FTL}} > d_{\text{gateway}} \cdot v_{\text{gateway}} + t_{\text{STL}}$$

Where:

Place Gates to avoid STL Flight Segments

Avoid Large STL Segments

If your route requires:

you may introduce a long STL segment. Due to ship flight computer behavior and default SF allocation, these STL legs can be longer than expected. This is why some gate routes are slower than pure FTL routes.

We are now suggesting:

Place gates in adjacent systems so ships FTL directly to them.

Don’t Compromise the Network for Aesthetic Connectivity

When people see a gateway map, there is a strong impulse to connect everything like a subway diagram. This often leads to inefficient placements made purely for visual or conceptual symmetry.

Gateways are not subways.

Instead, think of them as links in a multi-modal transportation system.

It’s okay that your UPS package flies on an airplane to your city, then takes a truck to your house. Demanding that every package stays on an airplane network reduces the effectiveness of the system. Our PRUN ships struggle with STL flight, in just the same way airplanes would struggle navigating to your house. Allowing for your “last mile” to happen via your ship’s FTL drive reduces the role of the weak link of STL flight in the system.

STL Ship Support

Designing around STL support might sound attractive. It expands theoretical use cases. I know I’m a people-pleaser and a compromiser, so it’s easy for me to capitulate to watered-down ideas to reach a consensus. I’m working on myself.

However:

De-prioritizing STL support allows for stronger long-term placement decisions.

Prioritize distance to CX

Choosing the innermost planet gives you better travel times to the CX. This is more important than prioritizing base-to-base traffic. Prioritize the common good over your personal bases or use cases.

Design Tradeoffs, Volume vs. Distance

We can only choose 5 upgrades.

Supporting 5k ships reduces maximum gateway range from 25pc to 20pc. The loss of range has an outsized effect:

When Planet-to-Planet Gates Work

Planet-to-planet gates can be very strong under the right conditions.

Remember these facts:

For a planet to planet gate to succeed:

Without both conditions, the gate will struggle to justify its upkeep.