The case for a single platform identity is simple to state and hard to retrofit: one account, signed in once, working across every tool in the family — versus a drawer of point solutions, each with its own login, its own user list, and its own idea of who you are. The first is a platform. The second is integration work that never ends.
The cost of stitching point tools together
Most software stacks grow by accretion. A team adds a tool for documentation, another for analytics, another for learning, another for billing. Each arrives with its own account system. Soon there are six user directories that disagree about who works here, six places to revoke a departing employee's access, six logins a new hire must be provisioned into by hand, and six brand experiences that look nothing like each other.
The cost is not only friction. It is risk. Access that must be revoked in six places is access that gets revoked in five. An identity that lives in six systems is an identity nobody fully controls.
HQ FS takes the opposite shape. One account spans the whole family — HQ Wealth for crypto portfolio accounting, HQ Docs for documentation, HQ Auth for identity, HQ Admin for control, HQ LMS for learning, HQ KPI for analytics. Sign in once, and you are in all of them.
Spine, control plane, and surfaces
A platform identity works because the pieces play distinct roles rather than overlapping.
- HQ Auth is the spine. It owns identity. One login, one session shared across every subdomain, one signing authority that every other product trusts. Nothing else mints an identity; everything else verifies one.
- HQ Admin is the control plane. From a single branded dashboard it manages users, feature flags, A/B testing, connected apps, VIP tiers, and whitelabel branding. Access, rollout, and experiments are governed in one place rather than six.
- The surfaces are where work happens. HQ Wealth, HQ Docs, HQ LMS and HQ KPI are the tools a user actually opens. Each is a surface over the same identity and the same control plane, so they share a session and a source of truth about who you are.
The separation is the point. When identity lives in the spine and governance lives in the control plane, the surfaces stay focused on doing their job, and adding a seventh surface does not mean adding a seventh user directory.
Modular adoption, not a monolith
A single identity does not require buying everything. The platform is modular by design.
- A free-forever base provides a universal account, a basic dashboard, HQ Docs, and a starter allowance — enough to be genuinely useful on day one.
- Add-on modules layer the heavier tools on top — wealth accounting, analytics, learning — adopted only as a team needs them.
The result is that an organisation picks the tools it needs rather than buying a monolith and growing into it. What does not change with each addition is the identity: every new module joins the same account, the same session, and the same control plane.
AI woven through, not bolted on
Because the products share a spine, the intelligence layer can run through all of them rather than being rebuilt per tool. Claude powers Ask AI in HQ Docs, evaluation in HQ LMS, insights in HQ KPI, and the autonomous documentation agents that keep docs current. The AI is a property of the platform, not a feature flag in one corner of it.
Built for tenants, too
For businesses that resell or rebrand the stack, the same architecture pays off again. HQ Auth and HQ Admin are whitelabel-ready: branded login pages — logo, colours, fonts — with no fork of the codebase, and a control plane a tenant administers themselves. One identity model, applied to many brands, without maintaining many codebases.
That is the whole case. A single account is not a convenience feature; it is the architecture that lets a suite of tools behave like one product — one place to sign in, one place to govern access, one consistent brand, and one intelligence layer — while still letting each team adopt only what it needs.
Takeaway: Point tools each bring their own login, user list and brand; a platform identity gives you one of each — Auth as the spine, Admin as the control plane, the surfaces on top — so adding the next tool is adoption, not integration.