ActiveState Platform vs FVM

ActiveState Platform hosts custom runtimes assembled from source. Projects specify runtime components, preserve project history and provide deployment instructions; their artifacts may include packages, dependencies, patches and bundles, but not contributors’ first-party code. Create projects in the web interface or with the State Tool CLI, then deploy and activate them locally. Projects can remain personal, be shared with an organization or be public. The platform supports Windows, macOS and Linux deployments, and its GraphQL API can build open-source software for different operating systems and languages without requiring users to manage build infrastructure. It provides immutable SBOMs in SPDX formats and describes build safeguards including reproducible builds, checksum checks and isolated containers. A free organization plan costs nothing and is limited to public projects. Curated Catalog annual pricing is $25,000 for fewer than 100 employees, $50,000 for 100–999 employees and $150,000 for 1,000 or more; those prices do not apply to legacy Platform subscriptions.

FVM manages Flutter SDK versions by project, allowing teams to keep builds consistent while using different versions across projects. A project’s `.fvmrc` file records its selected Flutter version and can include project-specific settings and flavors. FVM switches among installed SDKs without downloading them again. It can identify unreferenced versions, preview cleanup candidates, and remove unused SDKs with `fvm cleanup`. The documentation describes commands suitable for CI/CD automation and support for custom Flutter repositories. FVM provides packages for macOS, Linux, and Windows, with architecture availability varying by system. Installation options include a shell script, Homebrew, Chocolatey, Pub, and standalone packages. FVM detects VS Code and updates `.vscode/settings.json` for the Dart Code extension to use the project’s managed SDK. Android Studio and IntelliJ settings must be configured separately to point to the FVM SDK path. JSON API commands expose installed SDKs, releases, cleanup data, environment context, and project configuration. FVM stores known project roots in a machine-local file and says it does not scan disks for projects. The project is licensed under MIT.