Get carvercat

Free. In development.
Preparing for Alpha.

Public downloads are not open. The first reviewed release is planned as Alpha, with its supported systems, setup and known limitations listed alongside the package.

Development and distribution are different.

StageAvailabilityMeaning
Pre-alpha 0.0.1Internal development identityWindows and macOS Dev builds exist; these are not supported public installers
AlphaPlanned reviewed releaseFriends/public trials follow package, workflow and delivery checks; no release date or numeric Alpha version is announced

A source build or internal installer does not certify clean-machine installation, hardware compatibility or Resolve behaviour. Only the scope listed with a reviewed public package will be advertised as supported.

The local app is free.

  • Motion-graphics design and animation in the editor.
  • Local MCP integration for compatible clients.
  • Local editable Fusion generation/delivery within supported scope.
  • No Carvercat account required for local use.

Source remains private. Your optional AI client or model provider may require its own account, internet access or payment. No paid tier or hosted compiler is required for these local workflows.

What a reviewed download will include.

InformationWhy it matters
Stage, version and release dateIdentifies the exact package and its evolving stage
OS, architecture and requirementsLets you choose the package that was actually checked
Integrity and signing detailsLets you verify what you downloaded without bypassing security warnings
Installation, update and removalExplains the supported lifecycle and project preservation
Resolve/client compatibilityNames editions, versions and routes rather than broad logos
Known issues and guidesExplains limitations before your first project

There are no package links on this page because a reviewed public package has not been selected. Internal build locations are not distribution instructions.

Prepare for a useful Alpha trial.

  1. Choose a small, disposable composition and preserve your real work.
  2. Record the app version/stage, OS and relevant Resolve or client setup.
  3. Make a graphic, revise it, then save and reopen.
  4. Use only the delivery routes documented for that package.
  5. Report exact steps, expected/actual result and a cleared minimal example.

Stay close to the actual progress.