Account · Your own database

Store your content in your own database

By default Weaver-AI stores your documents, the embeddings built from them and the answers it writes. You can point all of that at a database you own. Your text then rests on your infrastructure and not ours.

Open your account settings Contact support

What moves, and what does not

Weaver-AI still has to run your account. It keeps the records it needs to do that. Everything else goes to your database.

Stored in your databaseYour uploaded documents and the text pulled from them. The embeddings Weaver-AI builds so it can search them. The answers it writes and the passages it cites.

Still stored by Weaver-AIWho your members are and what they may do. What you are billed and what you have used. Your settings, including this one. The audit record of who did what.

What your database has to provide

Weaver-AI supports PostgreSQL and MongoDB. Both are supported on the managed services listed in the console. Self-managed databases are accepted and are not verified, so the connection test is the only thing standing between a wrong setting and a failed upload.

Reachable from the internetWeaver-AI connects from its own network. The hostname has to resolve to a public address. A name that only resolves inside your own network cannot be reached. Add Weaver-AI’s published addresses to your firewall or security group. Leaving the database open to everybody is not a supported setup.

TLS that verifiesWeaver-AI connects with full verification and will not fall back. The certificate has to be valid for the hostname you enter. If you use your own certificate authority, paste its certificate into the form and Weaver-AI will verify against it.

A role Weaver-AI ownsCreate a role for Weaver-AI alone. Give it rights over its own schema and nothing else. Do not give Weaver-AI a superuser, and do not give it an account another application shares. A credential you cannot revoke without breaking something else is a credential you will not revoke.

Vector searchWeaver-AI searches embeddings, so the database has to be able to index them. On PostgreSQL that is the pgvector extension, and several managed services need it allowlisted on the instance before it can be created. On MongoDB that is Atlas Vector Search. Both are checked by the connection test.

What to put in the form

Field	What to put in it
`Engine`	PostgreSQL or MongoDB.
`Service`	Which managed service this is. Weaver-AI uses this to explain failures in that service's own terms.
`Hostname`	The hostname on its own. Not a connection string and not an IP address. Weaver-AI verifies the certificate against this name.
`Port`	Defaults to 5432 for PostgreSQL and 27017 for MongoDB.
`Database name`	A database Weaver-AI uses for itself. Letters, digits, underscore and hyphen.
`Username`	The role you created for Weaver-AI.
`Authentication database`	MongoDB only. The database the user is defined in, which is not the same as the database it has rights over. Leave it blank for admin. Atlas always defines users in admin, whatever database it grants them.
`Password`	Stored encrypted. Weaver-AI never shows it again. Leave it blank on a later save to keep the one you have.
`Certificate authority`	Only if your database uses a private certificate authority.

How to turn it on

Meet the requirements above
Most of this happens in your own cloud console, not in Weaver-AI. Do it first.
Confirm it is you
Weaver-AI asks for your password and a second factor before it will let you change this. A signed-in browser on its own is not enough to move somebody else’s data.
Save the settings
Only an account owner can do this. Saving does not send anything to your database yet.
Run the connection test
Weaver-AI connects and checks nine things separately. Each one says what it found and what to do about it. You get twenty tests an hour.
Turn it on
The switch opens once the test passes. From then on, new content for this account is written to your database.

What to expect once it is on

Content written before you turned this on stays where it was. This is for accounts starting out with their own database, not a migration. Talk to support if you need existing documents moved.

If your database becomes unreachable, Weaver-AI does not quietly start writing your content to its own database instead. A failed connection test does not turn this off either. Where your content goes changes when you change it, and not because something timed out.