@buoy-gg/license
Account validation, access state, and feature checks used by Buoy packages. Application integrations normally initialize accounts through Buoy.init or FloatingDevTools from @buoy-gg/core; installing this package alone does not add a tool menu.
Application setup
Follow the Quick Start to sign in and supply a Free or Pro account key. Keep the version compatible with the exact peer requirements of your other Buoy packages. Review peer-dependency warnings when upgrading.
Entry points
| Import | Intended use |
|---|---|
@buoy-gg/license | Application manager, React hooks, account state, and feature access. |
@buoy-gg/license/headless | Node-compatible validation and policy functions for custom hosts. |
The root exports LicenseManager, useAccountAccess, useLicense, and feature/tier hooks. The headless entry point exports validation, tier resolution, account-access resolution, cache-signature helpers, and lifecycle constants. It does not create a complete account manager for your host.
Custom hosts must handle validation, expiry, transient failures, caching, and revalidation. Do not treat a supplied key or a locally selected tier as proof of access. Use the exported policy with validated state, and refresh connected services when admission changes.
Check integration
Initialize through core and confirm that valid account access enables the intended tool. Check the signed-out and failed-validation states too. A temporary network failure and an invalid key are different conditions; preserve that distinction in messages to users.
Account and license validation require network requests. Disabling optional development telemetry does not disable validation. See Telemetry and pricing for data flows and current plan features.
License
Proprietary software. See the package LICENSE and Buoy terms.