Compatome

Private beta · Ionic / Capacitor

Know what breaks before you upgrade.

Compatome analyzes an existing Ionic and Capacitor project before a major upgrade — dependencies, plugins, native requirements and known breaking changes — and turns them into an actionable upgrade plan.

Request beta access See what Compatome checks

Runs locally. Your source code stays on your machine.

Example scanFieldNotes · Vue

compatome scan

Detected
Ionic
8.4.3
Capacitor
6.2.0
Vue
3.4.38
Target
Ionic
9
Capacitor
8
Upgrade readiness

HIGH RISK

Findings
38
Manual review flags
6

Static analysis · no build executed

Adapted from the legacy FieldNotes benchmark. Results depend on your project; a scan does not run a build.

Before the migration

Major upgrades shouldn't start with guesswork.

An Ionic upgrade spans several systems: Ionic breaking changes, Capacitor migration requirements, plugin compatibility and npm peer dependencies. Then there’s the native side: Android SDK, Gradle and Java; iOS, Xcode and CocoaPods.

Deprecated APIs, configuration changes and your own native customizations add another layer. These often surface one by one during an upgrade. Compatome attempts to identify them before the migration begins, so you can investigate and plan. It cannot guarantee a successful upgrade.

What gets checked

One project.
Several moving parts.

Compatome prefers “unknown” over pretending to know.

Framework & dependencies
Current stack, proposed targets, package relationships and documented migration requirements.
Plugins
Official, third-party and legacy plugin compatibility where reliable evidence exists. Unsupported combinations stay visible for review.
Android
Relevant SDK, Gradle, AGP, Java/Kotlin and native configuration requirements.
iOS
Deployment targets, Capacitor iOS, CocoaPods and relevant native requirements.
Source & configuration
Selected known removed APIs, renamed configuration and high-confidence migration patterns. This is not exhaustive source analysis.
Evidence & confidence
Verified and documented findings separated from inference and unknown compatibility.

How it works

From a scan to a plan.

  1. Scan

    Run Compatome from your project directory.

    compatome scan

  2. Assess

    Build a compatibility profile of the current project and proposed target.

  3. Understand

    See what was detected, why it matters, confidence, evidence and required action.

  4. Plan

    Get an ordered migration plan and an optional offline HTML report.

Validation, with boundaries

Tested against real Ionic upgrade scenarios.

Three different projects. 72 benchmark predictions. 136 automated tests passing.

Historical misses have been converted into regression coverage. These are scoped observations, not an accuracy percentage.

Benchmark scope

Vue / Ionic / Capacitor
FieldNotes · upgrade and build validation
Legacy Angular / SQLite
Static-only checks · no build or runtime test
React / mixed plugins
Static-only checks · no build or runtime test

FieldNotes validated workflows

  • Dependency installationVerified
  • Web buildBuild verified
  • Capacitor Android / iOS syncSync verified
  • Android debug buildBuild verified
  • Unsigned iOS simulator buildBuild verified
  • Device / runtime behaviorNot verified

Build execution covers FieldNotes only. The other two benchmarks are static-only. Not all 72 predictions are build- or runtime-verified; benchmark results are not compatibility certification.

Evidence over reassurance

A finding should tell you why it exists.

A finding can include the detected state, target state, severity, confidence, affected project area, evidence and recommended action.

Evidence may come from official migration documentation, package metadata, peer dependencies, release notes, native configuration, selected static source checks and separately recorded build validation.

Compatome distinguishes between verified, documented, inferred and unknown conclusions.

Local by default

Your project stays your project.

A normal scan reads project metadata, configuration and selected source patterns on your machine and produces local results. Your source files and generated reports are not uploaded to a Compatome server.

Optional external validation, enabled explicitly with --online, may send dependency package names, versions and related package metadata to the public npm registry. When external validation is unavailable, local analysis continues with reduced evidence.

Normal scans are read-only. They do not rewrite project source code, install dependencies or execute builds.

A small, free private beta

Have an Ionic project that's due for an upgrade?

We're looking for a small number of developers maintaining real Ionic/Capacitor applications. The private beta is free.

Request beta access

Please don't upload or paste proprietary source code when applying. We only need basic information about your project.

Bring the project you’ve been putting off.

Older Ionic or Capacitor versions. Third-party plugins. Cordova integrations. Native Android or iOS customization. An upgrade whose scope is still unclear.

Help us check the work.

Tell us which findings are accurate, what we missed, which warnings are unnecessary, and whether the report reduced your investigation time.