Skip to content
Account

Billing

How ForestVPN billing works for developers — project plans, consumer entitlements, and where end users manage their own subscription.

Billing on ForestVPN runs at two levels. Your project is billed for its platform plan and any usage-based charges. Your project's consumers are billed against the plans you define, and their entitlements (device limits, locations, mesh capacity, feature flags) are what the SDK enforces at runtime.

Managing your own ForestVPN subscription?

If you want to change your personal plan, read an invoice, or cancel, use the app and the consumer help center at forestvpn.com/help.

Billing in the API

  • Infrastructure API guides — projects, consumers, and the webhooks that keep your systems in sync with subscription state.
  • API reference — the consumer and platform billing endpoints, generated from the committed OpenAPI specifications.

Prices and entitlements are always served live from the billing catalog — the SDK and API read whatever your project's plans currently define.

Devices

How ForestVPN models devices in the SDK and Infrastructure API, and where end users manage their own devices.

Mesh (vspaces)

How ForestVPN's private mesh works for developers — device-to-device connectivity, MagicDNS names under mesh.fvpn.net, and where end users manage their own mesh.

On this page

Billing in the API