pgEdge Starfleet Client Workspace Provisioning (Onboarding)

pgEdge Starfleet Client Workspace Provisioning (Onboarding)

1. 01

   Start the 14-day free trial and provision a managed Postgres database from the pgEdge Starfleet console

   Time the provisioning run against the documented under-two-minute claim. If it slips past that window, note the cause before you promise the same turnaround to a client.

2. 02

   Confirm the Postgres version line on the new instance (v16, v17, or v18)

   The Managed plan runs 100% standard Postgres, so match the client's existing version before any schema work begins. Version drift here is the most common source of extension conflicts later.

3. 03

   Enable the curated extensions the client workflow needs: pgvector, PostGIS, pgBackRest, PgBouncer

   pgvector and BM25 hybrid search carry the RAG pipeline. PgBouncer matters once multiple client apps share the instance, and pgBackRest underpins the backup policy you configure next.

4. 04

   Connect Claude Code or Cursor through the built-in MCP server and verify SafeSession read-only enforcement

   Run one read query and one write attempt. The write must fail. If it succeeds, stop onboarding and fix the session scope before any client data lands in the database.

5. 05

   Create a copy-on-write branch for the client's staging environment

   Branching completes in seconds, so treat it as disposable. Every schema change or prompt-tuning experiment runs on the branch first, then promotes to the main instance.

6. 06

   Configure the automated 45-day backup policy on the production instance

   This matches the SMB Launch deliverable. Record the retention window in the client handoff doc so nobody assumes a longer history exists.

7. 07

   Wire the PostgREST server to the client knowledge base and test the FAQ or document search agent end to end

   PostgREST ships included on the Managed plan at $25/month, so there is no separate API layer to bill or maintain. Confirm the agent returns sourced answers, not just plausible text.

8. 08

   Decide the deployment target and document it in the client workspace record: pgEdge cloud, customer VPC (AWS, Google Cloud, Azure), or on-premises

   Data sovereignty requirements drive this choice, and HIPAA compliance sits on enterprise plans only. Locking the target now prevents a mid-project migration that eats your retainer margin.