Ember app assessment

Every long-lived Ember app accumulates history: pinned addons nobody remembers pinning, a build that only works on one engineer's machine, tests that were green when the original authors left. Before anyone commits to an upgrade budget or a migration roadmap, it's worth knowing exactly what you have.

What we look at

• Version posture — where you sit relative to current LTS, which deprecations are already firing, and what stands between you and the next supported release.
• Addon inventory — every dependency scored for maintenance status, Octane and Embroider compatibility, and replaceability. Abandoned addons are usually the real upgrade blockers, not Ember itself.
• Octane readiness — how much of the codebase is classic components, mixins, and observers versus native classes, Glimmer components, and tracked properties.
• Build and tooling — ember-cli configuration, build times, Embroider viability, CI health.
• Test health — coverage where it matters, flake rate, and whether the suite can actually protect an upgrade.
• Team skills map — who on your team can work confidently in the app today, and what it would take to widen that circle.

What you get

A written report with a keep/upgrade/migrate recommendation and effort ranges for each path — the document an engineering manager can take into a planning cycle. We give the same honest read either way: our revenue doesn't depend on which option you pick, so the recommendation doesn't tilt.

Assessments are hourly time and materials like all our work; the scope conversation before we start settles how deep to go. Start that conversation here.