Relationship structure
Non-hierarchical polyamory
Also called: non-hi-poly, non-hierarchical poly
Polyamory without ranked primary/secondary tiers — relationships are shaped by their own internal terms rather than by an externally-imposed ranking.
Non-hierarchical polyamory deliberately rejects the primary/secondary tiering common in hierarchical polyamory. Each relationship is shaped by its own internal terms — depth, time, commitments — rather than by a pre-assigned tier. The structure does not pretend material asymmetries do not exist (the partner you live with shares dishes; the long-distance partner does not), but it refuses to translate those practical asymmetries into ranked claims on the relationships themselves.
Non-hierarchical practitioners use descriptive language for the practical asymmetries that exist. Nesting partner names the person you live with. Anchor partner names a relationship with deep practical entwinement. Comet partner names a periodic, distance-spread connection. Each term picks out a specific dimension without packaging together a ranking of relationship importance.
The structure is harder to do well than hierarchical polyamory and easier to do well than relationship anarchy. Easier than RA because it retains the partner category and its associated expectations. Harder than hierarchical poly because there is no rule about who gets priority when conflicts arise — those have to be resolved on the merits each time, with all the affected people having genuine voice.
Non-hierarchical polyamory is sometimes the structure couples graduate to after some years of hierarchical practice, when the early need to protect the primary relationship against threat has eased and the secondary relationships have proven sustainable. It is also the starting structure of polyamorous people who never went through a monogamous primary relationship to open — those whose first polyamorous configurations were already multi-partnered.
Where non-hierarchical polyamory tends to slide back into hierarchy is in the unstated defaults. The nesting partner is asked first about holiday plans by default. The shared-finances partner has effective veto over major housing decisions. The partner who lives with you is the one your family invites to events. None of these are explicit hierarchy, all of them function like one. The work of doing non-hierarchical polyamory well is noticing those defaults and addressing them.
Trade-offs
Works well when
- Practitioners can hold practical asymmetries without translating them into relational ranking.
- Decisions that affect multiple relationships are made with all affected people having voice.
- Communication infrastructure is high enough to navigate conflicts case-by-case.
- All partners are oriented toward the same value: no one is hoping to be promoted.
Hard when
- One partner secretly wants to be primary and is performing non-hierarchy.
- Practical infrastructure (shared house, finances) creates default-hierarchies that are not actively addressed.
- External pressures (family, work, legal) require naming a single partner.
- Communication infrastructure is inadequate to handle the case-by-case decision-making the structure asks for.
Common pitfalls
- Unstated defaults that produce hierarchy in practice while denying it in framing.
- Time-allocation that consistently favours the nesting partner under the guise of practicality.
- Treating non-hierarchy as 'no commitments' rather than 'different commitments per relationship'.
How it differs from related structures
- Hierarchical polyamory: uses explicit ranked tiers; non-hierarchical refuses them.
- Relationship anarchy: goes further by rejecting the partner category itself, not just the ranking.
- Solo polyamory: rejects nesting partnership entirely; non-hierarchical polyamory may include nesting partners alongside other relationships.