PAXEER NETWORK® — SUB BRANDS
Paxeer sub-brands are product and service lines that operate under the parent brand. Each sub-brand inherits the core Paxeer visual language and is distinguished only by a product suffix. No sub-brand may use a color, typeface, or mark that conflicts with the parent identity.
01 — LOCKUP
Sub-brand lockups follow a single pattern: the parent Paxeer wordmark set in Light weight, followed by the product name set in Medium weight. Both in Paxeer Grand Sans. Never bold. Never a separate logo.
Parent wordmark (Light 300) + Product name (Medium 500) · No separator required
02 — STRUCTURE
Sub-brand names follow the structure: [paxeer] [product]. The product name inherits one of the approved brand blues. No custom colors.
/* Sub-brand naming structure */
[paxeer] + [product suffix]
// Examples:
paxeer sdk
paxeer wallet
paxeer registry
paxeer chain
Always lowercase
Both parent and product names are always set in lowercase
No hyphens
paxeer-sdk is incorrect. paxeer sdk is correct.
No slash separators
paxeer/sdk is incorrect. Space only.
No capitals
Paxeer SDK is incorrect in brand contexts (OK in technical docs)
03 — LOCKUPS
Developer tooling and integration layer. Uses the SDK suffix lockup.
#004CED
Agent wallet and payment policy interface.
#2841B8
Machine service registry and reputation layer.
#1A3A60
The sovereign L1 network infrastructure.
#0A1A30
04 — ABSTRACT LOCKUPS
Abstract lockups pair the PX symbol mark with a product name without the full wordmark. Used in app icons, product splash screens, and compact UI surfaces where the full wordmark would be too long.
05 — IN-USE
Sub-brand lockups in their natural environments.
Developer documentation header
paxeer sdk
Horizontal · Light+Medium · Obsidian bg
App topbar — wallet interface
paxeer wallet
Horizontal · Light+Medium · Obsidian bg
Registry landing hero
paxeer registry
Horizontal · 48px · Paper bg
Block explorer favicon
PX
Abstract · 32×32 · Square mark only