In short: yes, but not right now. See this issue: https://github.com/cozodb/cozo/issues/2. Also in this case you are not really using it as an embedded database anymore, which is our original motivation. We currently also provide a "cozoserver", but it is pretty primitive at the moment. "Big data" capabilities, when they arrive in Cozo, will probably go into the server instead of the embedded binaries.
My use of "embedded" means that the whole database runs in the same process as your application. This is how SQLite works. Your application doesn't "connect" to an SQLite database in the usual sense. Your application simply contains SQLite as part of itself. Contrast this with Postgres, where you first need to start a Postgres server and then have your application talk to it.
> Also in this case you are not really using it as an embedded database anymore, which is our original motivation
As by your (and mine) definition, I am indeed using it as an embedded database. It's running inside the process and storing (and persisting) blog-posts.
