- Is the core open source? What exactly is paid?
- Yes. The runtime, the scene-graph compiler, and all easing primitives are MIT-licensed on GitHub (38.2K stars). What you pay for in Pro and Studio is the commercial license clarity, the Studio timeline editor, the CI linter plugin, and support — not the engine itself. You can downgrade at any time and keep the core.
- How does seat math work for Studio and Enterprise?
- Studio is billed per seat, with a 3-seat minimum. Seats are assigned to a named user, not a machine — engineers can move between laptops without re-licensing. Enterprise uses a floating-seat model: a pool of seats is allocated to your org and assigned by your admin through SSO.
- What’s in the Enterprise SLA, in writing?
- 99.99% uptime on the Studio cloud surfaces (timeline editor, shared workspaces, asset CDN), measured monthly. Sub-50ms timeline jitter on the published runtime, benchmarked against the agreed reference scene. Misses trigger service credits per the contract schedule.
- Can we self-host and skip the SaaS entirely?
- Yes for the runtime — it’s MIT, you always self-host the engine that ships to your users. Enterprise adds a self-hosted Studio runner so your team can use the visual editor against an internal registry. We sign DPAs and custom indemnities for the runner.
- Do you invoice, and what are the payment terms?
- Pro and Studio are billed annually by default, with NET-30 invoices and credit-card payment. Enterprise contracts are annual with NET-45 by default; we’ll negotiate terms on request. We can issue purchase orders, multi-year commitments, and pro-forma invoices for procurement teams.
- What happens to our work if we cancel?
- Your code keeps running — it’s MIT, it’s already on your CDN. Studio workspaces export to a portable JSON scene-graph format. We retain your account data for 30 days after cancellation in case you change your mind, then it’s purged from production and backups within 90 days.