Entity Structure
Current and planned entity-structure framing for the ƒxyz Network.
This page explains the legal-entity layer as planning and structure, not as a substitute for the app’s legal-entity route docs.
Multi-Entity by Design
ƒxyz is global infrastructure that started incorporation in Poland. It is not a Polish company expanding outward: the entity layer is part of the architecture, not an administrative afterthought. Different jurisdictions carry different obligations, and the design separates them rather than forcing one company to carry all of them.
- FXYZ Sp. z o.o., Polish registered entity, KRS 0000816477, is the primary node
- the design provides for additional nodes in other jurisdictions as the network grows
Each jurisdiction is one authorization among many rather than the authorization. That is the difference between a company with a licence and a network with a licensing architecture.
Planned Structure
The public planning model also assumes:
- a licensing entity posture per jurisdiction as phases progress
- additional entities for later corridor or jurisdiction expansion
This page describes structure, not status. Which authorizations any entity holds, has applied for, or is pursuing is not stated here or anywhere else public.
Why It Exists
The entity layer exists to support:
- licensing
- regulated operations
- legal accountability
- separation between operational and regulatory obligations
What It Is Not
It is not the same thing as the live app route surface.
For the routed product surface, use:
Entity plans, future structures, and licensing relationships are subject to change and should not be treated as binding commitments.