The application encrypts the data, you save in the database the data encrypted. When you retrieve the info, the app decrypt it.

SQLCipher fits that bill. I had some issues with language integration but depending on what you're using it might work for you.

Turso: https://docs.turso.tech/libsql#encryption-at-rest

Also, DuckDB devs said it was planned: https://github.com/duckdb/duckdb/discussions/4512

Well, sqlite

Depending on the application could you just mount a filesystem that supports encryption? Even if it’s just mounting a .tar file.

Use an encryption library to decrypt the database in memory and encrypt it prior to writing it to disk. Assuming that you are not afraid of data loss due to power loss; that would be the most secure option and it works with the standard SQLite library

Or if you need more fault tolerance. The SQLite Encryption Extension (SEE) will read and write database files encrypted using 128-bit or 256-bit AES.

Firebird: 13.8. Database Encryption https://www.firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref30/fblangref30-security-dbcrypt.html

https://github.com/utelle/SQLite3MultipleCiphers/

Encryption is usually implemented in the server or client code. Why do you want the database to handle encryption?