Start trial

SQLite migration

AthenaDB provides a native SQL engine plus a SQLite-compatible C API and an athenadb-sqlite3 drop-in CLI, so existing SQLite applications can run on AthenaDB unchanged — and gain encryption at rest and AI-native retrieval. See the SQLite compatibility page.

The drop-in shell

athenadb-sqlite3 ./app.db ".tables"
athenadb-sqlite3 ./app.db "SELECT count(*) FROM events;"

Everything you use from the sqlite3 shell works the same way.

Applications linked against libsqlite3

AthenaDB ships a libsqlite3 shim exposing the sqlite3 C API. An application built against -lsqlite3 can load AthenaDB's implementation and run without code changes. SQLite compatibility is available in supported builds.

Why migrate

  • Encryption at rest with AthenaDB's own crypto stack.
  • Hybrid AI-native retrieval — keyword + vector + timeline + entity — on the same data, alongside your existing SQL.
  • A path, not a rewrite — keep your SQL surface and application code.

Notes

SQLite compatibility targets application-level drop-in use. As with any migration, test your workload against AthenaDB before switching a production system.