Mobile Development · head to head
Codemagic vs Turso

Codemagic
Mobile Development
CI/CD built for Flutter and mobile apps
- From
- Free
- Free plan
- Yes

Turso
Databases
SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.
- From
- Free
- Free plan
- Yes
The short version
- Free plans on both; paid from $1/mo and $4.99/mo.
- Where Codemagic falls short: minute-based pricing opacity: exact costs for concurrent builds become difficult to predict at scale without calculator.
- Prices and features on this page were last checked on 20 November 2026.
How do Codemagic and Turso differ?
Codemagic and Turso differ on pricing model and category (Mobile Development against Databases). Only the attributes on which Codemagic and Turso actually diverge.
Identical on both: starting price (Free), free tier (Yes), platforms (Web).
Which features does each one have?
They share no listed features; 10 only for Turso. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Codemagic
Nothing recorded that Turso does not also cover.
Only in Turso
- Per-tenant databases
- MIT licence
- Embedded replicas
- SQLite compatibility
- HTTP access
- Branching
- Point-in-time restore
- In-process engine
What is each one used for?
Codemagic is most often brought in for mobile CI/CD pipelines for iOS and Android. The jobs each tool is most often brought in to do.
Codemagic
- Mobile CI/CD pipelines for iOS and Androidnot Turso
- React Native CodePush over-the-air update distributionnot Turso
- Enterprise multi-team CI/CD at scalenot Turso
Turso
- Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Codemagic
- Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Codemagic
- Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Codemagic
- Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Codemagic
Where do Codemagic and Turso fall short?
Codemagic's most cited limit: minute-based pricing opacity: exact costs for concurrent builds become difficult to predict at scale without calculator. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Codemagic
- Minute-based pricing opacity: exact costs for concurrent builds become difficult to predict at scale without calculator
- Free tier severely limited to 500 minutes/month with single parallel build vs. competitors offering more generous free allocations
- M1/M2/M4 pricing variance creates complexity; customers must right-size machine type upfront without clear performance guidance
- Additional concurrency is expensive at $49/month per concurrent build, potentially costing $588/year per extra slot
Turso
- SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option
- Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated
- There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate
- Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on
- Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only
How much do Codemagic and Turso cost?
Codemagic has a free plan, with paid plans from $1/mo; Turso has a free plan, with paid plans from $4.99/mo. Plan by plan below, from each vendor's own pricing page.
Codemagic
Free- Pay as You GoOn request
- M2 Fixed Plan$3,990/yr
- 3 concurrent builds
- unlimited build minutes on M2
- M4 Fixed Plan$5,400/yr
- 3 concurrent builds
- unlimited build minutes on M4
- M4 Max Fixed Plan$9,000/yr
- 3 concurrent builds
- unlimited build minutes on M4 Max
Turso
Free- FreeFree
- 100 databases
- 5 GB storage
- 500M monthly rows read
- Developer$4.99/mo
- Unlimited databases
- 9 GB storage
- 2.5B monthly rows read
- Scaler$24.92/mo
- Unlimited databases
- 24 GB storage
- 100B monthly rows read
- Pro$416.58/mo
- Unlimited databases
- 50 GB storage
- 250B monthly rows read
Which should you pick?
Choose Turso if
- You need per-tenant databases.
- You want to start without paying.
- You also want mit licence.
Questions people ask
- Is Codemagic or Turso better?
- Neither clearly leads. Codemagic starts at Free and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Codemagic or Turso?
- Codemagic starts at Free and Turso at Free.
- Does Codemagic or Turso run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Codemagic for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Codemagic best used for?
- Codemagic is most often used for mobile ci/cd pipelines for ios and android, react native codepush over-the-air update distribution, enterprise multi-team ci/cd at scale. Of those, mobile ci/cd pipelines for ios and android and react native codepush over-the-air update distribution are not what Turso is typically brought in for.
- What can Codemagic do that Turso cannot?
- Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.
Answered from the vendors’ own pages
Codemagic: How much does it cost to add more parallel builds?
Each additional concurrent build costs $49/month ($588/year). Fixed-plan customers can purchase additional concurrency at $1,500–$3,000/year depending on tier.
SourceTurso: Is Turso just hosted SQLite?
Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.
Codemagic: Does Codemagic offer a free tier?
Yes. The free tier includes 500 free M2 build minutes monthly with 1 parallel build maximum, then paid usage kicks in.
SourceTurso: Can I really run a million databases?
That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.
Codemagic: What is the difference between monthly billing and annual fixed plans?
Pay-as-you-go charges per minute of build time. Fixed annual plans provide unlimited minutes on a specific machine type (M2, M4, or M4 Max) for one upfront yearly payment plus the option to purchase additional concurrency.
SourceTurso: How do embedded replicas handle read-after-write?
Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.
Codemagic: Is there a limit to monthly users on React Native CodePush?
Yes. On the fixed-price CodePush plan, users are billed per 100,000 Monthly Active Users (MAU). Overage pricing is $1 per 2,500 installs on pay-as-you-go or a higher per-instance fee on fixed plans.
SourceTurso: What licence is it under?
libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.
Turso: Is Turso still an edge database?
No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.
Related pages
Other head to heads
- Codemagic vs Bitrise
- Codemagic vs EAS Build
- Codemagic vs Appcircle
- Codemagic vs Maestro
- Codemagic vs Fastlane
- Codemagic vs Emerge Tools
- Codemagic vs Flutter
- Codemagic vs React Native
- Codemagic vs Adapty
- Codemagic vs AWS Amplify
- Codemagic vs .NET MAUI
- Codemagic vs NativeScript
- Codemagic vs Capacitor
- Codemagic vs RevenueCat
- Codemagic vs Superwall
- Codemagic vs Expo
- Codemagic vs Firebase
- Codemagic vs Android Studio
- Codemagic vs SQLite
- Codemagic vs SurrealDB
- Codemagic vs Supabase
- Codemagic vs PlanetScale
- Codemagic vs MotherDuck
- Codemagic vs EMQX
- Codemagic vs Trino
- Codemagic vs DuckDB
- Codemagic vs Teradata
- Codemagic vs Nile
- Codemagic vs Apache Kafka
- Codemagic vs Apache Spark
- Codemagic vs Firebolt
- Codemagic vs LanceDB
- Codemagic vs Timeplus
- Codemagic vs Vitess
- Codemagic vs YugabyteDB
- Codemagic vs Canary Labs
- Turso vs Bitrise
- Turso vs EAS Build
- Turso vs Appcircle
- Turso vs Maestro
- Turso vs Fastlane
- Turso vs Emerge Tools
- Turso vs Flutter
- Turso vs React Native
- Turso vs Adapty
- Turso vs AWS Amplify
- Turso vs .NET MAUI
- Turso vs NativeScript
- Turso vs Capacitor
- Turso vs RevenueCat
- Turso vs Superwall
- Turso vs Expo
- Turso vs Firebase
- Turso vs Android Studio
- Turso vs SQLite
- Turso vs SurrealDB
- Turso vs Supabase
- Turso vs PlanetScale
- Turso vs MotherDuck
- Turso vs EMQX
- Turso vs Trino
- Turso vs DuckDB
- Turso vs Teradata
- Turso vs Nile
- Turso vs Apache Kafka
- Turso vs Apache Spark
- Turso vs Firebolt
- Turso vs LanceDB
- Turso vs Timeplus
- Turso vs Vitess
- Turso vs YugabyteDB
- Turso vs Canary Labs
