Your complete charting stack, under one license.

No. The core is Apache-2.0, free forever at any company size.

PineTS is AGPL-3.0: free for anyone who open-sources their stack. Closed-source commercial use requires a seat. That’s the entire dual-license deal, from dollar one.

No. A seat’s PineTS rights are a separate commercial grant outside the AGPL, so your use carries no copyleft, source-disclosure or network-use disclosure obligations.

No, because there is no engine-only license. Every seat is the same three things: Vela™ Pro, the PineTS commercial license, and the LuxAlgo Library commercial license. Headless products simply never use the chart.

Vela’s open-source core is the renderer, workspace, drawings, 70+ studies, data providers, the plugin SDK and the scripting port. Vela Pro adds footprint and TPO charts, the orderflow indicator suite, a built-in Pine Script® editor and watermark-free builds. Every seat also carries the PineTS and LuxAlgo Library commercial licenses.

Anyone writing or maintaining code against Pro or PineTS commercial APIs. Your end users never need seats, there is no staging or production split, and a seat can move to another developer once a month.

Yes, when the provider’s terms bar training on your inputs and keep them confidential, as business and enterprise plans do. Assistants are tools, not developers, so they never need seats.

With a seat, yes: every paid seat includes full commercial rights to the LuxAlgo Library, meaning the scripts we publish with source. Closed-source LuxAlgo toolkits are not included. Without a seat, Library scripts remain available only under their published non-commercial terms.

Yes. One license covers web, mobile, desktop, and server-side or headless use, including alerting, royalty-free with no per-end-user fees.

No. Nothing is metered: there are no caps on monthly active users, chart loads or API calls, and no per-end-user fees. Vela runs inside your app on the data feeds you choose. User count only decides eligibility for Business, which is for products with fewer than 100,000 end users.

Resell or sublicense the software itself, share its source outside your team, offer its APIs to other developers as a library or SDK, build a competing charting library or scripting engine on it, or train an AI model on its source. The one exception: Business may ship it as a component inside your own SDK or OEM offering.

Finish your current term, renew on Business. We never claw back mid-term.

Total gross revenue over the trailing twelve months, for your company and its affiliates combined. It is company revenue, not one product’s ARR.

A person who uses your products, counted at your busiest calendar month over the trailing twelve months, across all your products combined. The count matters for Business, which covers fewer than 100,000 end users. End users never need seats.

You certify them at checkout and again at each renewal, and we rely on that in good faith: nothing in the software enforces your tier. A materially false certification is a breach of the agreement.

Yes. Business has no revenue minimum. It has two ceilings, fewer than 100,000 end users and under $25M in revenue, and it isn’t for brokers, exchanges, prop firms or other regulated financial firms, which license on Enterprise at any size. Smaller teams choose it for unlimited developers or white-label and OEM rights, and from 17 developers it costs less than buying seats.

When your platform has 100,000 or more end users, your company does $25M or more in annual revenue, you are a broker, exchange, prop firm or other regulated financial firm (at any size), or procurement needs your own MSA, a DPA, or a written SLA before anyone can pay. Everything else is Business. Talk to us.

Annually, in advance. Every license is a twelve-month term that renews automatically; there is no monthly plan, one-time purchase or per-end-user royalty. Seats are bought at self-serve checkout, and Business can also pay by Stripe invoice (ACH or wire, PO number, net-30). Fees are non-refundable except where the law requires.

Renewal is at the published price, with at least 60 days’ notice of any change. If you stop renewing, deployed products keep running for existing users for a 90-day wind-down. We never claw back mid-term.

Nothing in your deployed product switches off: Vela Pro has no kill switch or license check. What stops is access to the private repository and new releases. If the term ends because either side declines renewal, you may keep operating products already deployed, for your existing end users, for a 90-day wind-down, but not release new versions with the software, add developers or offer it to new customers. When the wind-down ends, you stop using the software and delete your copies, including those in repositories, build caches and on developer machines. After termination for breach there is no wind-down: use stops at once. Either way, your end users’ continued use of products you already distributed is not affected.

The Developer License Agreement is standard and isn’t individually negotiated. Business can add a custom legal review from +$10k at checkout. Enterprise signs on our Enterprise Agreement, and we review your MSA, a DPA or other terms on request.

Not for seats or Business: both are fully self-serve, and the legal hub has the standard terms and procurement documents, right next to the buy button. Enterprise is the one tier that starts with a conversation.

Each developer gets read-only access to a private GitHub repository, granted from your LuxAlgo account, so your team builds from source it can read. The open-source cores install from npm (@luxalgo/vela and pinets). Builds have no license key, activation step or entitlement check: the agreement is the enforcement.

No. A license covers software only, and LuxAlgo provides no market data, including the trade feed footprint charts and the orderflow indicators need. Vela ships keyless crypto connections for Binance, Coinbase, and Hyperliquid; stocks, futures, forex and trade feeds plug in through its data-provider interfaces with your own licensed data.

Yes. New versions and fixes ship through the same repository for as long as your license is active. We support the current major version of Vela Pro and PineTS, plus the previous major for twelve months after a new one ships.

Yes. You can use, modify and build on Vela Pro, PineTS and Library scripts for your own products, and ship them compiled or minified inside those products. Support and fixes cover official builds, not builds you have modified.

Email support at partners@luxalgo.com: a first response within two business days on the Developer License, and within one business day with a named escalation contact on Business. Enterprise adds a Slack Connect channel and severity-based targets, from four business hours when a defect takes your product down.

Only through one optional Vela Pro feature, and never as telemetry: neither the open-source cores nor Vela Pro contain analytics or tracking code. The Library menu, on by default, fetches Library scripts from app.luxalgo.com; you can turn it off or route it through your own proxy. Its requests carry the IP address and user-agent any web request does, plus the search. Every other call goes straight to a vendor you configure: the crypto exchanges behind Vela’s built-in adapters, with coin icons from Ledger’s icon service, and the market-data providers in PineTS.

Yes, on request at security@velacharts.dev. The Security & Architecture Overview answers most of it up front: both open-source cores are fully auditable, Vela has seven runtime dependencies and PineTS three, and every npm release carries the registry’s signature and integrity hash.

Yes, without asking anyone: a Business quote PDF on our letterhead, valid for 30 days, and a procurement pack with the Developer License Agreement, the Support & SLA Schedule, the Security & Architecture Overview and our W-9. Both sit next to the Business buy button.

No. The software runs in your infrastructure and your users’ browsers, so uptime is yours to control, and the optional features that call LuxAlgo carry no uptime commitment either. The Support & SLA Schedule commits to response and fix times instead.

Report them to security@velacharts.dev; we honor coordinated disclosure and publish advisories on GitHub. For a confirmed Critical or High vulnerability in a supported version, we target a fixed release within seven calendar days, for every paid tier.

Only billing details (name, email, company), processed by Stripe, and the GitHub usernames you grant source access. Our subprocessors are Stripe (billing), GitHub (source delivery), SendGrid (email), Vercel (hosting), Amazon Web Services (file storage) and Intercom (support). None of them handles your market or end-user data; the optional Library menu is the one feature that calls our servers. Enterprise agreements can add data-processing terms for that billing data.

Delaware law, with venue in Delaware courts. Each side’s liability is capped at the fees paid or payable in the twelve months before a claim, except for IP infringement and breaches of the eligibility or restriction terms. In a merger or sale of the company, the license can be assigned with notice to us, and the new owner’s revenue sets the tier at the next renewal.

No. Trading educators and academies, financial media, fintech apps, research tools and trading communities build on the same tiers. Your tier follows your size, not your industry: the Developer License under $500k in revenue, Business up to 100,000 end users and $25M in revenue, Enterprise beyond either. Brokers, exchanges and prop firms start on Enterprise at any size.

Usually the Developer License: one seat per developer building your platform, and your students and members never need one. The charts, PineTS and Library indicators ship inside your own course site or app, under your own brand. Past $500k in revenue it’s Business; past 100,000 students or members, or $25M in revenue, it’s Enterprise.

Usually your client, as the company whose product ships it: the license covers products developed by or for the company that holds it. Every developer writing code against the APIs needs one of its seats, whoever employs them; Business covers unlimited developers.

Yes. Ship your own indicators, PineTS on your servers, and Library scripts alongside them, as long as your product is the main value. Reselling the charts, the engine, or the Library as a product of their own is not allowed.

Yes: any paid license gives you watermark-free builds and no attribution requirement, so your users see only your brand. Business also lets you remove LuxAlgo names from inside the software and redistribute it in your own SDK or OEM offering. The code is Apache so forks are legal, but the Vela name and branding aren't (TRADEMARK.md). A paid product should carry your logo, not your vendor's.

Yes, as a plain fact, such as “includes indicators from the LuxAlgo Library.” Our logos and names can’t appear in your product’s name or suggest that we endorse it.