DOCUMENTATION

Databases

Your Versors machine can connect to external databases to read data, build dashboards, or create apps backed by real data. The AI agent handles the connection setup and queries.

SQLite (Recommended)

If you don't need an external database, we recommend having the AI create a SQLite database directly on your machine. No setup, no credentials, everything stays self-contained. Just ask:

"Build a contacts app with a local SQLite database"

Security note: Database credentials are stored only on your private Versors machine. For safety, we strongly recommend:
  • Use a read-only database user when you only need to read data
  • Create a dedicated database user for Versors (not your admin account)
  • Limit the user's access to only the tables/schemas needed
  • Use connection strings with SSL when available
  • Revoke the credentials when you're done

Supabase

Supabase provides a hosted PostgreSQL database with a REST API. It's the easiest database to connect because the agent can use the JavaScript client library directly.

1

Go to supabase.com, create a project, and find your project URL and anon key in Settings → API.

2

Tell your agent: "Connect to my Supabase database. URL: [project URL], anon key: [key]"

Firebase / Firestore

Firebase uses a service account for server-side access.

1

In the Firebase Console, go to Project Settings → Service Accounts.

2

Click "Generate New Private Key" and download the JSON file.

3

Upload the JSON file to your Versors machine and tell the agent to use it.

PostgreSQL

Connect to any PostgreSQL database using a connection string.

"Connect to my PostgreSQL database: postgres://user:password@host:5432/dbname"

Common hosted PostgreSQL providers: Supabase, Neon, Railway, Render, AWS RDS, DigitalOcean. Most provide a connection string in their dashboard.

MySQL

MySQL connections work similarly with a connection string or individual parameters.

"Connect to my MySQL database at host db.example.com, user readonly, password [password], database myapp"

REST APIs as Data Sources

Many services expose data via REST APIs instead of direct database connections. The agent can connect to any REST API -just provide the endpoint URL and any required API key or auth token.

"Pull my Stripe transactions and build a revenue dashboard"

"Fetch data from the Airtable API and display it in a table"

"Connect to the Notion API and sync my project tasks"

Best Practices

  • Start read-only -Connect with a read-only user first, then upgrade permissions only if needed
  • Test with sample data -Before connecting a production database, test with a staging copy or sample dataset
  • Use environment variables -Ask the agent to store credentials in a .env file rather than hardcoding them
  • Back up before writes -If the agent will modify data, make sure you have a backup or can restore