{
  "id": 10463417,
  "title": "pgEdge’s new agent database branches never merge back into the source",
  "url": "https://urgent.news/2026/09/28/pgedges-new-agent-database-branches-never-merge-back-into-the-source",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-28T14:07:38.000Z",
  "source": {
    "name": "The New Stack",
    "slug": "the-new-stack",
    "url": "https://thenewstack.io/pgedge-starfleet-postgres-branching/"
  },
  "original_language": "en",
  "account": "pgEdge has launched Starfleet, a Postgres cloud platform aimed at addressing the challenge of transitioning database setups from development to production environments. The platform utilizes database branching and agent tooling, deploying options from pgEdge's hosted service to air-gapped on-premises environments, all on standard community Postgres. Each coding agent in parallel operates within its own copy-on-write branch, ensuring no integration with the source database's storage layer. Developers work on changes within their isolated environments, which maintain distinct connection details and IP allowlists, preventing accidental access between branches. Linking a project folder through the command line binds the database ID or branch ID to the folder's .env file, allowing agents to connect using the associated credentials without manual intervention. Schema changes are managed using existing tools like Alembic or Flyway, with any migrated files accompanying the code when merged. Test data is retained and deleted alongside the agent's database upon completion. Starfleet operates on a $25 per month pricing model, offering a 14-day free trial. The platform leverages pgEdge's Agentic AI Toolkit for Postgres, which provides MCP server access for coding agents and integrates RAG and PostgREST APIs for content retrieval and direct database access. Additionally, pgEdge SafeSession within the MCP server safeguards read-only agents from making changes to the database.",
  "summary": "AI coding agents can get an application running quickly, but taking that prototype into production is another problem. The database The post pgEdge’s new agent database branches never merge back into the source appeared first on The New Stack .",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}