SceneView for companies
The facts a team checks before it adopts an SDK: the license, what the code sends over the network, which platforms are production-grade, how often it ships and where to report a vulnerability.
Last checked: October 28, 2026 · SceneView 4.62.0
For companies shipping SceneView
SceneView runs in commercial products. Sponsor it or buy support.
Commercial products ship SceneView. Almost nobody contributes back, in code or in funding, while the maintainers carry every fix and every release. If SceneView is part of your product, sponsor it or buy support, now.
Sponsor
Funds the fixes, Filament upgrades and releases your product depends on. Open Source Collective issues the invoice and the receipt; your company is listed nowhere unless you ask.
Commercial support
- Incident, $600. One reproducible problem. Within 3 business days: a minimal reproduction, the cause, and a workaround or a costed fix.
- 2.3 LTS, $1,800 for 90 days. One identified integration. Answers within 2 business days and up to 1 day of work a month; more work is quoted. The $600 of an Incident already bought is deducted.
Contracted and invoiced through Open Source Collective, the fiscal host; the money goes to the collective’s budget. Payment comes before any work. Every version stays under Apache 2.0. Write to hello@sceneview.dev.
License in plain words
SceneView is released under the Apache License 2.0. In practice:
- You can use it in commercial and closed-source apps, and modify it, without paying or asking.
- You get a patent grant from every contributor for their contributions.
- When you redistribute it, keep the license text and the NOTICE file, and mark the files you changed.
- No trademark rights: the license does not let you use the SceneView name or logo to brand your product.
The mcp/ directory (the sceneview-mcp server for AI assistants) is under the MIT License. The 3D models used in the samples, docs and this website are third-party works under their own licenses, listed in assets/CREDITS.md; they are not needed to use the SDK.
What the SDK sends over the network
No analytics, no telemetry, no advertising identifiers and no accounts. The SDK opens network connections only for the URLs your app gives it, such as a model to load.
One exception, on the web. sceneview-web fetches its default lighting environment from sceneview.github.io when a viewer starts. To avoid that request, host the environment yourself: with the Kotlin/JS builder, environment(iblUrl, skyboxUrl) or noEnvironment() skip the default; with the JavaScript API, viewer.setEnvironment(url) replaces it once the viewer is running.
Android permissions declared by the libraries and merged into your manifest:
INTERNET(sceneview), to load models from a URL.VIBRATE(sceneview), for optional haptic feedback. Remove it withtools:node="remove"if you do not use it.CAMERA(arsceneviewonly), for augmented reality.
Platform AR services. On Android, AR runs on Google Play Services for AR (ARCore), under Google’s terms. On Apple platforms, AR uses ARKit and RealityKit on the device.
This page is about the SDK. The sceneview.github.io website itself uses Google Analytics, as described in the privacy policy.
Platforms and maturity
Only Android is marked stable today. Alpha platforms ship and are usable, with fewer guarantees: their APIs may still change between 4.x releases.
| Platform | Status | Built on |
|---|---|---|
| Android | Stable | Jetpack Compose, Filament, ARCore. API 24+, OpenGL ES 3.0. |
| Android TV | Alpha | Compose TV, Filament. |
| iOS, macOS, visionOS | Alpha | SwiftUI, RealityKit. iOS 18, macOS 15, visionOS 2. |
| Web | Alpha | Filament.js on WebGL2 / WASM. |
| Compose Multiplatform | Alpha | Viewer subset, no AR. |
| Desktop (JVM) | Alpha | Compose Desktop, Filament. |
| Flutter, React Native | Alpha | Native bridges to the Android and Apple SDKs. |
Source: the platform table in the README.
Release cadence
SceneView ships every week. Android artifacts are published on Maven Central, the web and React Native packages on npm, the Flutter plugin on pub.dev and the Apple package through Swift Package Manager.
Full history: GitHub releases and the changelog.
Versioning and support today
- Semantic versioning. A binary-compatibility check (
apiCheck) runs in CI on pull requests that touch the Android libraries, so their public API cannot change by accident. - Deprecations before removals. Deprecated APIs carry a
ReplaceWithhint your IDE can apply, and upgrades are documented in the migration guide. - Fixes ship in the next 4.x release. Stay on a recent 4.x release to get fixes for free. Guaranteed response times and the 2.3 line are covered only by the paid commercial support.
Where to get help is listed in SUPPORT.md, and how the project is run in GOVERNANCE.md.
Reporting a vulnerability
Report security issues privately, never in a public issue, following the security policy. It lists the supported versions, what to include in a report and the coordinated disclosure process.
Third-party notices
The NOTICE file credits the third-party code SceneView includes or derives from, with its license. Filament, Google’s rendering engine, is used as published by Google. The authors and licenses of every sample 3D model are in assets/CREDITS.md.
Where it shows up
SceneView has more than 1,300 stars on GitHub, and over 500 public repositories declare it as a dependency.
Used in production: SDKs published by commercial vendors on Maven Central and npm declare SceneView as a dependency, and crash reports from apps live on Google Play reach its issue tracker. A company that ships SceneView under its Apache 2.0 license has not endorsed it, so this page names none.
Source: GitHub code search, owners sceneview and ThomasGorisse excluded, checked on October 28, 2026.
Contact
Technical questions happen in the open, on GitHub. For an invoice or a company sponsorship, write to hello@sceneview.dev.
- GitHub Discussions for questions, including an evaluation for your company.
- GitHub Issues for bugs and feature requests.
- Discord for a quick chat with the community.