Does Neon branching work with Gateco?

Yes. Each Neon branch gets its own connection string. Register each branch as a separate Gateco connector with a distinct name (e.g. "knowledge-base-staging"). Policies apply per connector via selectors, so you can have different policies on your staging branch during development.

Will Neon scale-to-zero affect Gateco latency?

Only on the first query after an idle period — cold-start adds 200–500ms on reconnect. For production Gateco workloads with latency SLAs, use Neon's fixed-compute option or connect via the Neon connection pooler, which maintains a warm connection.

Can I use sql_view metadata resolution with Neon?

Yes — sql_view is available for all Postgres-family connectors including Neon. Create a view in your Neon database exposing the classification and ownership fields, then reference the view name in your connector's search_config.

Vector DBTier 1

Neon

Policy-enforced vector search on Neon serverless Postgres — with branch-per-environment isolation for policy development.

Search capabilities

Vector (ANN)	Keyword (ranked)	Keyword (filter)	Hybrid (native)	Grep (substring)	Grep (regex)

Cold-start on autoscaled branches adds 200–500ms on first query after scale-to-zero. Use Neon connection pooler for production SLA workloads.

Ingestion (Tier 1)Retroactive registrationsidecar metadatainline metadatasql_view metadataauto metadata

Neon is a serverless Postgres platform with database branching, autoscaling, and pgvector support. Gateco connects to Neon as a Tier 1 Postgres-family connector, supporting ingestion, retrieval, and sql_view metadata resolution.

Neon's branching model makes it well-suited for isolated development and staging environments: create a branch with test vector data, connect it as a separate Gateco connector, and run your policy tests without touching production data.

Neon autoscaling means connections can scale to zero when idle. Gateco's connection handling tolerates reconnects transparently. For production workloads with sub-50ms SLAs, configure a fixed connection string pointing at Neon's connection pooler endpoint rather than a branch endpoint.

All four search modes are supported. Retroactive registration scans the configured table and enrolls existing vectors. sql_view metadata resolution lets you keep policy-relevant fields in your Postgres schema rather than syncing a separate sidecar store.

Sample search config

{
  "table": "knowledge_chunks",
  "embedding_column": "embedding",
  "content_column": "chunk_text",
  "metadata_columns": ["classification", "source_doc_id", "department"],
  "text_search_config": "english"
}

Sample policy

{
  "name": "Department knowledge access",
  "effect": "allow",
  "rules": [{
    "conditions": [
      {"field": "principal.department", "operator": "eq", "value": "{{resource.department}}"},
      {"field": "resource.classification", "operator": "in", "value": ["internal", "public"]}
    ]
  }],
  "selectors": [{"connector_type": "neon"}]
}

Policy conditions reference resource.* and principal.* fields. Policy reference →

Frequently asked questions

Does Neon branching work with Gateco?: Yes. Each Neon branch gets its own connection string. Register each branch as a separate Gateco connector with a distinct name (e.g. "knowledge-base-staging"). Policies apply per connector via selectors, so you can have different policies on your staging branch during development.
Will Neon scale-to-zero affect Gateco latency?: Only on the first query after an idle period — cold-start adds 200–500ms on reconnect. For production Gateco workloads with latency SLAs, use Neon's fixed-compute option or connect via the Neon connection pooler, which maintains a warm connection.
Can I use sql_view metadata resolution with Neon?: Yes — sql_view is available for all Postgres-family connectors including Neon. Create a view in your Neon database exposing the classification and ownership fields, then reference the view name in your connector's search_config.

Ready to connect Neon?

Follow the step-by-step setup guide or talk to the team for help with your specific configuration.

Setup guide →Talk to the team All integrations