Pricing
The launch scope is narrow on purpose, so the pricing story is narrow too. The site should make it obvious how to start an evaluation, when to move to a team license, and when an enterprise rollout conversation is justified.
Commercial Access
Use this when you need to validate chart-family fit, wrapper shape, and rollout constraints before committing to a license.
Commercial Access
Commercial access for product teams shipping against the supported wrapper surface and documented launch families.
Commercial Access
For larger programs that need rollout planning, support expectations, and alignment around long-lived product ownership.
What To Send
The fastest path is a short message that states the chart families you care about, which wrapper you need first, and what makes the rollout commercially meaningful.
List the chart families, data shape, and wrapper surface you need to validate first.
Explain whether this is a prototype, a team rollout, or an enterprise delivery program.
Call out the interaction, performance, or support questions that have to be answered before you proceed.
Include when you need an answer so the conversation can match the urgency of the project.
Current Commercial Policy
JavaScript and Svelte support are the public entry points today, so pricing and support center on those paths.
The contract is easier to trust when each supported family has explicit boundaries instead of a vague platform promise.
Commercial discussions should not get ahead of the examples and docs that engineers will actually use during evaluation.
That tier is for rollout planning and execution, not just a renamed email inbox.