CodeMorph API VS Flight Ledger

Flight Ledger's answer:

Flight Ledger combines flight history, ticket economics, and loyalty accounting in one private local ledger. It does not just show where you flew. It reconciles each flight with receipts, reissues, refunds, reimbursements, miles flown, aircraft and tail numbers, and what MileagePlus actually credited. This makes cost per mile and missing-credit checks possible. The public app requires no account, stores its SQLite database in the browser, supports optional private Google Drive sync, and is free and open source.

Flight Ledger's answer:

Choose Flight Ledger if you care about ownership and auditability more than live travel alerts. Unlike flight-status trackers, it focuses on your completed flight history and the money and loyalty credit behind it. It imports records you already have, works without sign-up, keeps data locally, and can be self-hosted. Its strongest fit is frequent United travelers who want to reconcile ticket costs, reimbursements, PQP, PQF, award miles, and lifetime miles. A live flight tracker can complement Flight Ledger rather than replace it.

Flight Ledger's answer:

Flight Ledger is for frequent flyers who want a durable personal flight ledger rather than only live flight tracking. It is especially useful for United and MileagePlus members because its loyalty analysis covers PQP, PQF, award miles, lifetime miles, and Premier progress. Flight and cost tracking work across airlines. It also suits work travelers who need to separate reimbursed business trips from personal spending, aviation enthusiasts interested in routes and airframes, and privacy-conscious users who prefer local data or self-hosting.

Flight Ledger's answer:

I fly frequently and wanted a clean way to understand my own flying: where and how often I had flown, how many miles I had accumulated, what the trips cost, which aircraft I had used, and how my MileagePlus totals developed over time.

That information was scattered across my United account, MileagePlus activity, email receipts, and flight tracking apps. I wanted one private place to see it together without creating another account, repeatedly logging in to different services, or digging through receipts.

Flight Ledger grew from that personal need. It imports the records I already have, connects the flight, cost, and loyalty sides, and makes the numbers easy to inspect and reconcile.

Flight Ledger's answer:

• Next.js 15 with the App Router, React 19, and TypeScript
• Tailwind CSS v4 for the interface
• SQLite, using the official SQLite WebAssembly build in the browser and Node's built-in node:sqlite when self-hosted
• Recharts for charts and d3-geo for the route map
• A fully static browser build with bundled fonts, airport data, and map geometry

There is no ORM and no application account backend. Optional sync uses the user's own Google Drive.