Create one, link it to the services that should reach it, and the credentials arrive as environment variables on the next deploy. Nothing listens on the public internet, nothing is injected behind your back, and the server is our problem rather than yours.
Every project can have databases, and each one is a libsql instance we run: the SQLite dialect you already know, spoken over HTTP so there is no connection pool to exhaust and nothing to keep warm between requests. It is the one to reach for when your service sleeps between visitors.
Postgres when your schema wants Postgres: extensions, window functions, types that libsql does not have, and every tool you already own. You create the database, link it to the services that should reach it, and the connection string arrives as an environment variable. We run the server.
The cache, the queue and the rate limiter that every app eventually wants. Valkey is the open fork of Redis, so it speaks the same protocol and works with the client you already import: the change is one URL. You create it, link it to a service, and we run it.
Go beyond what seems possible.