database-manager

You can manage PostgreSQL CRUD operations across multiple providers using a unified, provider-agnostic interface that supports Supabase, PlanetScale, and Turso with typed configurations. This allows seamless cross-provider database integration directly within agent workflows.

You can configure RLS policies and run schema migrations for Supabase through an extensible schema management interface. This provider-agnostic API enforces typed configurations to securely manage row-level security and apply migrations within your agent workflows.

Yes, transactional support for PostgreSQL works alongside other databases like Turso and PlanetScale. The unified interface manages connections across all providers, allowing you to execute PostgreSQL transactions while maintaining multi-database CRUD operations.

The best way to perform health checks and connection pooling for multi-database setups is through a provider-agnostic interface with typed configurations. It monitors connection health across Supabase, PlanetScale, Turso, and PostgreSQL within your agent workflows.

A provider-agnostic database API works with Supabase and PlanetScale for agent workflows by providing a unified interface for CRUD, migrations, and RLS. It enforces typed configurations to ensure secure and consistent cross-provider database operations.

Limitations of a unified interface for multi-database management include relying on provider-agnostic abstractions, meaning provider-specific features outside standard CRUD, migrations, RLS, and health checks may require direct database access. Transactional support is limited to PostgreSQL.