Postgres database
A Postgres database per project, a development branch agents can use safely, and SQL exports.
Serverless Postgres for side projects: one database per project
Provision an isolated serverless Postgres database per project with a development branch and plain DATABASE_URL support across any host.
A development database branch agents cannot break
A development database branch gives your tools and agents an isolated Postgres copy with your production schema, migration ledgers, and zero live rows.
Back up your Postgres database as SQL
Run vibiz export --db to export your entire Postgres database as a compressed SQL snapshot ready for psql or save tables to CSV.
Export Postgres tables to CSV
Export your Postgres database tables to CSV files using the vibiz CLI or API, with automatic table bundling, headers, and environment controls.
Get a Postgres DATABASE_URL in one command
Run vibiz dev to get a working Postgres DATABASE_URL written directly to .env.development.local with your schema ready for migrations.
Inspect tables and run read-only SQL from the CLI
Run read-only SQL queries and inspect Postgres tables directly from the command line using the read view API or a local database branch.
Postgres vs Firebase for a new app
Choose Postgres for relational data, standard SQL queries, and zero lock-in; choose Firebase for quick document storage with built-in client SDKs.
Run database migrations safely with an AI agent
Run safe database migrations with an AI agent by using isolated development branches with schema-only clones and scoped Limited API keys.
Seed data in a development branch, not in production
Seed development databases safely using an isolated branch with empty tables, keeping test fixtures away from production rows.
Use a managed Postgres database from an app hosted anywhere
You can run a managed Postgres database on thelastapi and connect to it from any server, container, or platform using a standard DATABASE_URL.
Use Postgres from Next.js with Drizzle or Prisma
Connect Next.js to Postgres with Drizzle or Prisma using DATABASE_URL from thelastapi, complete with isolated dev branches for safe migrations.
Why agents should never touch production rows
AI agents should never touch production database rows to prevent privacy breaches, accidental data destruction, and unrecoverable user state changes.
No posts match your search. Try fewer words, or pick All topics.