Employer plan registry
Plan archetypes, graded by source
Large cloud platform
Cloud / infrastructure
- mechanic
- In-plan Roth conversion
- contrib
- Per pay period
- source
- Illustrative archetype
Social platform
Consumer internet
- mechanic
- In-plan Roth conversion
- contrib
- Per pay period
- source
- Illustrative archetype
Marketplace retailer
E-commerce
- mechanic
- No conversion path
- contrib
- Not applicable
- source
- Illustrative archetype
Productivity software co.
Enterprise software
- mechanic
- In-plan Roth conversion
- contrib
- Per pay period
- source
- Illustrative archetype
Device hardware maker
Consumer hardware
- mechanic
- In-service distribution
- contrib
- Per pay period
- source
- Illustrative archetype
Payments infrastructure
Fintech
- mechanic
- In-plan Roth conversion
- contrib
- Per pay period
- source
- Illustrative archetype
Streaming media co.
Media / streaming
- mechanic
- No conversion path
- contrib
- Not applicable
- source
- Illustrative archetype
Accelerated computing co.
Semiconductors
- mechanic
- In-plan Roth conversion
- contrib
- Per pay period
- source
- Illustrative archetype
Enterprise CRM platform
Enterprise software
- mechanic
- In-service distribution
- contrib
- Annual / lump-sum
- source
- Illustrative archetype
Ride-hailing platform
Mobility
- mechanic
- In-plan Roth conversion
- contrib
- Per pay period
- source
- Illustrative archetype
Why archetypes, not brands
Plan features change, and asserting “Company X allows the Mega Backdoor Roth” without a current primary-source citation is exactly the trust failure this category is prone to. So this registry ships as illustrative archetypes you can pattern-match against. When the operator verifies a real plan against a primary source — official benefits page > Form 5500 filing > Levels.fyi > Carry — an archetype is replaced with a real, dated, cited entry. See the methodology for the source-of-truth hierarchy and verification cadence.