Connectors
Overview
A connector is how Monospace reaches the system behind a data source: a database, service, or API connected to a workspace. When you add a data source in the Studio, you choose a connector in the connector picker and provide its configuration.
| Connector | Connects | Reference |
|---|---|---|
| Database connectors | PostgreSQL, MySQL, MariaDB, and SQL Server databases | PostgreSQL, MySQL and MariaDB, SQL Server |
| Managed and compatible services | Hosted and compatible PostgreSQL, MySQL, and MariaDB services, including Amazon RDS | Managed and Compatible Services |
| Custom connectors | APIs, SaaS applications, and any other system without a built-in connector | Custom Connectors |
This walkthrough connects an existing MySQL database with a user that can only SELECT, browses it in the Studio, and shows a write the database refuses.
Database Connectors
Each database connector handles connection pooling, schema introspection, SSL/TLS configuration, and query execution. Monospace encrypts credentials at rest and never stores them in plaintext. It then scans the source so you can choose which namespaces and collections to import. To keep Monospace from changing a source's database structure, lock its schema.
| Connector | Tested versions | Authentication | Reference |
|---|---|---|---|
| PostgreSQL | 14 through 18 | Password or AWS IAM | PostgreSQL |
| MySQL | 8.4 minimum | Password or AWS IAM | MySQL and MariaDB |
| MariaDB | 10.7 minimum | Password or AWS IAM | MySQL and MariaDB |
| SQL Server | 2017 and later | Password | SQL Server |
Managed and Compatible Services
The connector picker has a tile for each service below. A tile uses its engine's connector and adapts the form to the service, so the engine's page covers its options. Each engine's page also lists setup notes per service.
| Engine | Services |
|---|---|
| PostgreSQL | Aiven for PostgreSQL, AlloyDB for PostgreSQL, Amazon Aurora PostgreSQL, Amazon RDS for PostgreSQL, Azure Database for PostgreSQL, Crunchy Bridge, DigitalOcean Managed PostgreSQL, EDB Postgres, Google Cloud SQL for PostgreSQL, Heroku Postgres, Neon, PlanetScale PostgreSQL, Railway PostgreSQL, Render PostgreSQL, Supabase, TimescaleDB, YugabyteDB (Alpha) |
| MySQL | Aiven for MySQL, Amazon Aurora MySQL, Amazon RDS for MySQL, Azure Database for MySQL, DigitalOcean Managed MySQL, Google Cloud SQL for MySQL, Oracle MySQL HeatWave, Percona Server for MySQL, PlanetScale Vitess (Beta), Railway MySQL, SingleStore (Beta), TiDB (Beta) |
| MariaDB | Amazon RDS for MariaDB |
A service that runs standard PostgreSQL, MySQL, or MariaDB doesn't need its own tile: choose the engine's connector.
Custom Connectors
For a system that isn't a supported database, such as an internal API or a SaaS application like Stripe, build a custom connector. A custom connector is a data connector extension that runs on your instance and exposes the system's data as collections. Installed custom connectors appear in the connector picker, each marked Extension.
Custom connectors are in preview. See Custom Connectors for the guides and reference to build one.
Request a Connector
If the database or service you need isn't listed, request it on the roadmap.
See Also
- Custom Connectors — build a connector for a system without a built-in one
- Introspection — how Monospace discovers your database schema
- Data Model — collections, fields, and relations
- Configuration — environment variables for the system database and SSL
- Data Types — how field types are represented in the API